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-9314: Background job agebinding was never run to recover from disconnected mode

Authentication Service ,  

9 October,17 at 05:18 PM

problem:
adclient stayed in disconnected mode for a long period of time and never got back to connected mode even if there are valid and working domain controllers in the domain.

Cause:
There are times when adclient fails to recover from disconnected mode because the background recovery thread is busy.

If a single task takes too much time could cause agebinding never gets a chance to recover.  The cause of long running task observed could be
<bg:MemberRefresh>
<bg:krb5.conf>
<bg:netstate>


Workaround:
Currently the only workaround is restart centrifydc agent to free the stucked background thread.

Resolution:
In release Suite 2017.2, we introduced two background threads responsible for performing different background tasks.  This should prevent agebinding from not able to bring adclient back to connected mode.