This discussion is archived
1 Reply Latest reply: Apr 26, 2013 12:13 AM by DeanyDean RSS

Explanation of SGD logging severity

Currently Being Moderated

I have checked the SGD docs but it's not very clear. I need to troubleshoot problem that the SGD server throws error below in login.log after less than a day of run.

The password for user was incorrect or has expired.
Exception was: javax.naming.NamingException: Failed to get an LDAP connection
at com.sco.tta.common.jndi.provider.ldap.LdapScopeState.getLdapContext(
at com.sco.tta.common.jndi.provider.ldap.LdapMultiCtx.getLdapContext(
at com.sco.tta.common.jndi.provider.ldap.LdapMultiCtx.lookupLink(
at com.sco.jndi.toolkit.provider.BaseContext.lookup(
at com.sco.jndi.toolkit.provider.ToolkitContext.nns_lookup(

I'd like to find out which KDC it has trouble getting an LDAP connection from since i have two KDC specified in my krb5.conf file. I was hoping by enabling more verbose logging, it will tell me.

The SGD docs say:
"Selecting a severity level is not cumulative. For example, selecting info does not mean you also see warningerror or fatalerror log messages.

To log more than one level of severity, use a wild card."

So assuming "moreinfo" severity has more info but I don't want to miss errors either, does severity "*" show logs for ALL levels? Since I don't know what to expect for each level, I can't confirm this.

Alternatively, is there a way to see which KDC server it binds to?

Thank you!
  • 1. Re: Explanation of SGD logging severity
    DeanyDean Newbie
    Currently Being Moderated
    If you set the severity to "*" it will show all log levels.

    To get more log info for LDAP/AD you can use the following filters:

    In SGD 4.60 and newer:


    In SGD 4.50 and before:


    Hope this helps

    Edited by: DeanyDean on 26-Apr-2013 08:13


  • Correct Answers - 10 points
  • Helpful Answers - 5 points