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-8466: cdcwatch not starting a new adclient process

Authentication Service ,  

31 March,17 at 04:16 PM

Applies to:
DirectControl 5.3.1 on CentOS platform

Problem:
When adclient process was killed with the “kill” command, both cdcwatch and adclient processes were stopped and a new adclient process was not restarted 

Resolution:
When Linux "kill" command is issued without signum parameter, by default, it uses SIGTERM(terminate the process), upon which both adclient and the cdcwatch will be killed. This is by design.

To kill the adclient without killing cdcwatch, use  "kill -9 <process_id>" or "kill -SIGKILL <process_id>" or "kill -KILL <process_id>"

Related Articles

 articleKB-2211: ERROR cdcwatch detected adclient is not running properly articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS 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-1831: runmappers (defunct perl processes) for GPs time out. articleKB-8461: Can the CDCWatch process be configured to use the same port each time it launches? articleKB-4621-How-to-configure-RHEL-abrt-to-exclude-Centrify-adclient articleKB-4291: What files are modified by Centrify DirectControl or DirectAudit during install & adjoin process articleKB-2313: Enabling "Do not require Kerberos Preauthentication Kerberos Preauthentication" causes adclient to crash