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-2504: adclient takes a very long time to start the first time during adjoin.

Centrify DirectControl ,  

12 April,16 at 11:09 AM

Applies to: Centrify DirectControl 5.x and above
 
Question:
 
The first time adclient starts up as part of running adjoin, it seems to take an inordinate amount of time to start. 
While it is reporting that it is initializing caches, dots are repeatedly echoed to stdout and several minutes later it gives the error:
 
Exception during cache load RecvWait out
 
..and the adjoin command returns. An alternate session on the host being used to check what is happening with adinfo, etc. indicates all is fine. 
This test was repeated several times with several different systems and it seems to happen consistently. Subsequent startups of adclient seem to work. 
 
Is there any reason for this?
 
Answer:
 
Starting from Centrify DirectControl 5.x, the agent pre-populates the cache (including all the roles and rights) and this can take time depending on how many zones, users, groups there are. Customers can quicken the adjoin process by using the 'i' flag (-i, --noinit Do not preload the cache) which will skip the pre-load of the cache.
 
This will not affect normal functionality in any way apart from after adclient starts up - any kind of query is going to be very slow as there is no initial cache present - particularly in large environments. 

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