Problem:
On Solaris 10, a problem was found that adnisd did not start up on zone reboot if either passwd or group was excluded, e.g. "nisd.exclude.maps: passwd group".
Snippet of logs:
svc:/network/nis/centrifydc-server:default (Centrify DirectControl NIS server)
State: maintenance since Mon Dec 09 08:17:59 2013
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/network-nis-centrifydc-server:default.log
Impact: This service is not running.
Error in the service log:
[ Dec 9 08:17:30 Enabled. ]
[ Dec 9 08:17:42 Rereading configuration. ]
[ Dec 9 08:17:44 Executing start method ("/lib/svc/method/centrifydc-nis start") ]
/lib/svc/method/centrifydc-nis failed: Adclient not running and no cache files.
[ Dec 9 08:17:59 Method "start" exited with status 96
Looking at the dependencies of the service centrifydc-server, there doesn't appear to be a dependency on adclient due to which SMF tries to bring up adnisd in parallel/before adclient leading to the issue.
# svcs -l centrifydc-server
fmri svc:/network/nis/centrifydc-server:default
name Centrify DirectControl NIS server
enabled true
state maintenance
next_state none
state_time Mon Dec 09 08:17:59 2013
logfile /var/svc/log/network-nis-centrifydc-server:default.log
restarter svc:/system/svc/restarter:default
contract_id
dependency require_all/none svc:/system/filesystem/minimal (online)
dependency require_all/restart svc:/network/rpc/bind (online)
dependency exclude_all/none svc:/network/nis/server (disabled)
Cause:
This was because in this case adnisd startup script checked for passwd and group maps and did not start up if they were not there.
Resolution:
This error is fixed in the 2014.1 release. Customers running into this issue should upgrade to this release to address
this issue.