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-2021: Centrify debug does not work with syslog-ng and syslog server

Centrify DirectControl ,  

12 April,16 at 11:02 AM

Applies to: All versions of Centrify DirectControl

Question:
In a situation where a customized syslog-ng (instead of /etc/syslog.conf) and a dedicated syslog server is used, Centrify debug does not work when /usr/share/centrifydc/bin/addebug is executed. The following error message is seen:

ERROR: /etc/syslog.conf not found. Operation cancelled.

Answer:
1. Edit /etc/centrifydc/centrifydc.conf and change the log: parameter to DEBUG so that Debug is turned ON. 

2. Run adreload to make adclient pick up the new setting. 

3. If adnisd is being used, please run 'service adnisd reload' to make adnisd pick up the new setting. 

4. Configure /etc/syslog to send auth.* traffic to /var/log/centrifydc.log 

5. Reload syslog configuration by restarting or HUPing the same. 

6. Reproduce the issue in question. 

7. Reverse configuration modified in steps 1-5. 

8. Email Centrify support the file /var/log/centrifydc.log.

Note:  This is a unique setup. It would be next to impossible for Centrify to make addebug (a shell script) smart enough to work with all the combinations of customer's configuration.

 

 

 

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