Product/Component Concerned : eDirectory / LDAP
Target Audience : Beginners
Platform : All (Demonstrated on Linux)
Using (N)DSTRACE is one of the usual debugging techniques in eDirectory. And you have a lot of options that can be used to get the debug trace messages. One of the options is LDAP that can be used to log the messages specific to any ldap operation.
By default, the LDAP option will log on only the error (critical and non-critical) messages. This article will help you to get the more debugging LDAP messages in the ndstrace by setting the LDAP screen options.
- Log in to your tree with iManager.
- Go to the Directory Administration Tab.
- Select the LDAP Server object concerned with your server.
- Go to the 'Tracing' tab.
And now you can see the 'Error Messages'(critical and non-critical) being selected by default.
- Log in to your eDirectory server. Start NDSTRACE and enable the LDAP option.
- Run a simple ldapsearch and see no messages been logged in to your NDSTRACE screen, as there are no errors in the ldapsearch.
- Go back to the iManager 'LDAP Server' page and enable all the LDAP screen option and click 'Apply'.
- We are now done with setting the LDAP screen options. We can now run the same ldapsearch query again against the eDirectory server.
- Now we can see more details on the search being logged in to the NDSTRACE including the search parameters, search result etc.
Through ldapconfig utility:
Setting the LDAP screen options can be done through the 'ldapconfig' utility (that gets installed with eDirectory) as follows:
- Run 'ldapconfig' to get the options.
- Run 'ldapconfig get' with the following parameters to get all the options that can be set through ldapconfig.
- Use 'ldapconfig get 'LDAP Screen Level'' to get the LDAP Screen Level option alone. And by default it shows only 'Error | Critical'.
- The option can be changed to set the screen level option to ALL using the 'ldapconfig set 'LDAP Screen Level=all'' as follows.
- Run 'ldapconfig get' to see if the option LDAP Screen Level has been set to ALL.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.