This section describes issues that involve the Service Management Facility of Solaris 10 OS. For more information about this new feature in the Solaris OS, see Solaris Service Manager in Solaris 10 What’s New.
When the system first boots after a Solaris 10 OS installation, an error with dependent services might occur. The svccfg import subcommand might fail to activate dependent services that have been declared in a service's manifest file. Consequently, the dependent services might not start in order and generate error messages that refer to those services.
Workaround: Issue the command svcadm refresh for the dependent service. For example:
svcadm refresh dependent FMRI
Software developers can avoid this problem with the following workarounds:
Declare dependent services at the instance level instead of the service level.
For live installations, enable a package's postinstall script to run the svcadm refresh dependent FMRI command.
For installations that use an alternate boot environment, append the svcadm refresh dependent FMRI command to the /var/svc/profile/upgrade file.
When a host has no local printers configured, two print services, ipp-listener and rfc1179, are set to offline by default. These services are automatically moved to online after local printers are configured on the host. The default offline settings of these services do not indicate an error. Therefore, no user intervention is required.
On systems that do not use Network Information Service (NIS) or NIS+ name service, the NFS and autofs services are disabled. The failure is due to these services' dependency on the keyserv daemon. The keyserv daemon relies on the RPC domain name, which is not set on systems that do not use NIS or NIS+. Consequently, the failure of the keyserv daemon causes the NFS and autofs services to become disabled.
Workaround: To enable the services, perform the following steps:
Issue the following commands:
# svcadm disable network/rpc/keyserv # svcadm disable -t network/nfs/client:default # svcadm enable network/nfs/client:default # svcadm disable -t network/nfs/server:default # svcadm enable network/nfs/server:default # svcadm disable -t network/rpc/gss:ticotsord # svcadm enable network/rpc/gss:ticotsord
During system startups, sometimes the login services such as console or ssh logins start before remote file systems and naming services become available. Consequently, the user name might not be recognized or the user's home directory might not be available.
Workaround: If the error occurs, wait for a few seconds and then log in again. Alternatively, log in from a local account to view the system state.