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-2211: ERROR cdcwatch detected adclient is not running properly

Centrify DirectControl ,  

2 February,17 at 04:58 PM

Applies to:
 
All versions of Centrify DirectControl.
 
Question:
 
What does the below message mean?. 
 
ERROR cdcwatch detected adclient is not running properly
 
Answer:
 
Cdcwatch is the watch dog spawned by adclient (Centrify's main daemon) on starting up to watch itself. Should adclient go down for some reason, cdcwatch will attempt to restart it.
 
cdcwatch will make a connection to adclient every 20 seconds and wait for reply. If it does not hear a reply after 30 seconds, it issues SIGABRT 9 (On Posix-compliant platforms, SIGABRT is the signal sent to a process to tell it to abort) i.e. to terminate adclient, and then tries to start a new adclient process. 
 
Enabling the watchdog is governed by a couple of parameters
 
Frequency: adclient.watch.check.frequency (20 sec) 
 
Timeout: adclient.watch.check.timeout (30 sec) 
 
There are 2 other parameters: 
 
adclient.watch.startup.delay (5 min) - cdcwatching starts pinging cycle. 
 
adclient.watch.death.timeout (10 min)  - this is how long cdcwatch will keep trying. After this time, it also gives up. At this point manual intervention would be required. 
 
Note: adinfo will report Centrify mode: down if adclient is completely down.
 
 

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