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-7783: Adnisd is Failing to Start When the Machine is Rebooted

Centrify DirectControl ,   Centrify DirectControl Plugins ,  

21 December,16 at 08:59 PM

Applies to:  
All versions of Centrify NIS on all supported platforms.

Problem:
On Centrify enabled *nix machines 'adnisd' is not starting successfully when the machine is rebooted.

Cause:
'adclient' must be running and in a "Connected" state before 'adnisd' can complete startup. In this case, the system took an extended amount of time to move into a "Connected" state and 'adnisd' attempted to start before this occurred, causing the service startup to fail. ​

Workaround:
If the startup of adnisd is delayed, adclient will complete its startup and then adnisd will start without issue. Below are the steps for delaying the adnisd startup:

1)  Edit and change the line in 'adinsd.service' to
 
ExecStartPre=/etc/centrifydc/scripts/systemd/adnisd.sh ; /usr/bin/sleep 30

And then save and close.
 
2) Edit adnisd.sh and change the count to "COUNT=40" (The 40 can be adjusted higher if more time is needed)
 
3) While in the adnisd.sh file, change "sleep 1" to "sleep 5" 

And then save and close adnisd.sh.
 

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

Related Articles

 articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6041: How to show current license type in use by adclient? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-3925: How to add Centrify parameter to a group policy articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-4744: adnisd doesn't start up on zone reboots on Solaris 10 articleKB-5616: Cached logins may fail for the first few minutes when connected to external (non-domain) networks