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-3015: adquery user does not return anything on HPUX requiring leave and join

Centrify DirectControl ,  

12 April,16 at 11:09 AM

Applies to: All versions of Centrify DirectControl on HPUX
 
Question:
 
After joining a HPUX server running Centrify DirectControl and after provisioning users, adquery user -A does not show anything. Neither running adflush nor restarting Centrify DirectControl helped. 
 
The HPUX caching daemon daemon pwgrd is running fine and has also been restarted. 
 
When Centrify debug is enabled, the /var/adm/centrifydc.log is 0 bytes (does not log anything), however /var/adm/syslog is growing in size with DirectAudit messages. 
 
Leaving and joining the server fixes the issue temporarily. 
 
Is there any reason for this?

 
Answer:
 
When HP's /var/adm/syslog file grows too big, or when there is too much logging to syslogd (not necessarily by Centrify, but possible with any application) syslogd will hang and in turn cause adclient to hang when trying to log messages.  
 
Re-configure Centrify DirectAudit correctly to stop the logging of warning messages. Restarting syslogd and restarting centrifydc (the adclient) afterwards will resolve the issue. There is no need to do an adleave and an adjoin.

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

Related Articles

No related Articles