Clearing startup problems
A potential problem can occur if the name of the machine is changed with
the uname command.
When the system hostname is changed with the uname command, the
hostname entries in the /etc/net/*/hosts and
/etc/inet/hosts files are not updated.
This causes the rpcbind daemon to fail.
To clear startup problems, do the following:
-
Check if the NFS daemons and the rpcbind daemon are running,
using nfsping -a.
-
Check if the system hostname matches the entry in the
/etc/net/*/hosts files. For example, if the machine's hostname
was hulk (as returned by uname -n), the entry in each
of the /etc/net/*/hosts files should look like:
hulk hulk
-
Check the /etc/inet/hosts if it has an entry for hulk.
-
If the first entry in each of the /etc/net/*/hosts files does not
match the machine's hostname, then do the following in order:
-
Stop NFS.
-
Update the first entry in the /etc/net/*/hosts files.
-
Restart the rpcbind daemon:
/usr/sbin/rpcbind
-
Restart NFS.
For information on starting and stopping NFS, see
``Starting and stopping NFS''.
Next topic:
Clearing server problems
Previous topic:
Checking the biod daemon
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 - 01 June 2005