Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-1384: Why are debug messages getting logged into /var/log/centrifydc_client.log even though adclient debugging is turned off.

Centrify DirectAudit ,   Centrify DirectControl ,   Centrify Identity Service, Mac Edition ,  

12 April,16 at 11:02 AM

Applies to: Centrify DirectControl 4.x & above on all OS's

Problem:
Why are debug messages getting logged into /var/log/centrifydc_client.log even though adclient debugging is turned off.

Sample messages in the log:
Oct 05 17:14:03 oninit[688248] DEBUG: -> centrifydc2_getpwnam user="rx"
Oct 05 17:14:03 oninit[688248] DEBUG: getpwnam: User 'rx' is in 'pam.ignore.users' list
Oct 05 17:14:03 oninit[688248] DEBUG: <- centrifydc2_getpwnam, result=NSS_NOTFOUND(2)
Oct 05 17:14:03 oninit[688248] DEBUG: -> centrifydc2_getpwnam user="rx"
Oct 05 17:14:03 oninit[688248] DEBUG: getpwnam: User 'rx' is in 'pam.ignore.users' list
Oct 05 17:14:03 oninit[688248] DEBUG: <- centrifydc2_getpwnam, result=NSS_NOTFOUND(2)
Oct 05 17:14:03 oninit[688248] DEBUG: -> centrifydc2_getpwnam user="rx"

Cause:
The issue is debug messages that are emitted out of applications such as Informix or Oracle or other similar applications. That is because when Informix/Oracle/other apps got started, it loaded and called Centrify libraries for user and group name resolution. At the time, debug option was turned on, so the debug messages were generated, and will continue to be generated. There is no way to tell these libraries, which had already been initialized in application process space, that debug has been turned off - short of restarting it. This is primarily due to there is no known mechanism to safely deliver a signal to Informix/Oracle/other apps for the Centrify library only.

Workaround:
Please restart the application after turning off debugging. If this is not an option, please run "addebug clear" periodically to make sure centrify_client.log does not grow too big.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.