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-5876: How to supress agent SYSLOG warnings

Authentication Service ,  

12 April,16 at 11:46 AM

Applies to:

All versions of Centrify DirectControl on all platforms


Question:

Is there a way to suppress the following Centrify warnings in SYSLOG?

Apr 16 13:14:11 myserver Message forwarded from myserver: adclient[6619148]: WARN <bg:dzRefresh> sam.loader Fail to insert local passwd 'localuser:XXX' into DZ DB (error: Failed to step: SQL logic error or missing database ), continue.Please ensure there is no duplicated uid in the local passwd file. 

Apr 16 09:42:37 myserver auth|security:warn|warning adclient[6619148]: WARN <fd:26 sshd(3604684)> 'myusername' has a unix name of 'myusername' which is longer than the recommended maximum of 8 characters 


Answer:

In general a Centrify warning can be suppressed by identifying the component and adjusting it's log level.  


In the first example observe the component name "sam.loader" is mentioned.  To suppress the first event add the following parameter in /etc/centrifydc.conf:

log.sam.loader: ERROR 


In the second example it is slightly more challenging as there is no component mentioned.  To suppress this event specifically add the following parameter in /etc/centrifydc.conf:

log.lam: ERROR


Finally if the event you wish to suppress is not specified here you can either contact Centrify support to help determine that or suppress all warnings by modifying the following parameter in /etc/centrifydc.conf:

log: ERROR 

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

Related Articles

 articleKB-0062: How to Collect Debug Logs from a DirectControl Agent articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS 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? articleSIEM Integration - Understanding Centrify's Audit Events articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0)