Centrify

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-1909: Why running "addebug on" produced an error?

Authentication Service ,  

12 April,16 at 11:47 AM

Applies to: 
 
Centrify DirectControl on Linux, Unix system running syslog-ng
 
Question:
 
Why I am getting the following error when I run 'addebug on'? ERROR: /etc/syslog.conf not found. Operation cancelled.
 
Answer:
 
Addebug script checks for the existence of a syslog pid file in /var/run directory.  For system that is running syslog-ng, syslog config file is written as /etc/syslog-ng/syslog-ng.conf but not /etc/syslog.conf and pid file as /var/run/syslogd.pid.  Addebug failed because it could not find config is /etc/syslog.conf.
 
Workaround:
 
Rename /var/run/syslogd.pid to /var/run/syslog-ng.pid.  This way your script finds syslog-ng.pid and able to correctly update syslog-ng.config file.
 
In addition, please take a back up of your existing syslog-ng.conf file and add the following lines and restart syslog (service syslog-ng restart)
 
====================================================================
filter f_centrify_re {
    ( program("adnisd") or program("adclient") )
    and priority(debug..emerg);
};
 
######
destination d_centrify_re {file("/var/log/centrifydc.log");};
# destinations
 
log {
    source(s_local);
    source(s_kernel);
    filter(f_centrify_re);
    destination(d_centrify_re);
};
 
==============================================================================
A sample file is attached at the end of this KB article. Pl. use it as reference only.

Resolution: 
 
None
 
 

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

Related Articles

 articleKB-6041: How to show current license type in use by adclient articleKB-9281: Running a dzdo Command and Entering a Good Password Can Produce an Error: dzdo: pam_open_session: Permission denied articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-2462: Running the CLI version of adjoin with a valid computer name produces an error about illegal characters. articleKB-2000: "addebug on" command fails with syslog ng installed articleKB-2936: Unable to initialize the tcl environment when running addebug