yeah this is cause the stock log4j config might be missing some loggers
try with this http://d.pr/f/J486


On Mon, Apr 8, 2013 at 10:41 PM, Wu, James C. <James.C.Wu@disney.com> wrote:
Hi,

I tried to debug the kinit error by setting Log4j level to DEBUG. But the apacheds simply can't start. I tried using both java 7 JVMs from OpenJDK and Oracle.

The last log records I got are like the follows:

ATTRIBUTE_TYPE[2.5.4.37] : {OBJECT_CLASS[2.5.4.37], OBJECT_CLASS[2.5.4.37]}
OBJECT_CLASS[2.5.6.7] : {OBJECT_CLASS[2.5.6.7]}
ATTRIBUTE_TYPE[2.5.4.30] : {OBJECT_CLASS[2.5.4.30]}
ATTRIBUTE_TYPE[2.5.4.31] : {OBJECT_CLASS[2.5.4.31]}
ATTRIBUTE_TYPE[2.5.4.32] : {OBJECT_CLASS[2.5.4.32], OBJECT_CLASS[2.5.4.32], OBJECT_CLASS[2.5.4.32]}
ATTRIBUTE_TYPE[2.5.4.33] : {OBJECT_CLASS[2.5.4.33]}
LDAP_SYNTAX[1.3.6.1.1.16.1] : {ATTRIBUTE_TYPE[1.3.6.1.1.16.1], MATCHING_RULE[1.3.6.1.1.16.1], MATCHING_RULE[1.3.6.1.1.16.1], ATTRIBUTE_TYPE[1.3.6.1.1.16.1], ATTRIBUTE_TYPE[1.3.6.1.1.16.1]}
ATTRIBUTE_TYPE[2.5.4.38] : {OBJECT_CLASS[2.5.4.38], OBJECT_CLASS[2.5.4.38], OBJECT_CLASS[2.5.4.38]}
ATTRIBUTE_TYPE[2.5.4.39] : {OBJECT_CLASS[2.5.4.39], OBJECT_CLASS[2.5.4.39], OBJECT_CLASS[2.5.4.39]}

Regards,

james



--
Kiran Ayyagari
http://keydap.com