ITEM: AB8013L

lockd and statd error messages.

Question:

I am using NFS on the diskless client and every one or two 
minutes get these messages:

Cannot Register Service RPC: 1832-008 Timed out                                 
rpc.lockd:  1831-057 unable to register(NCM_PROG, NLM_VERS,tcp)                 
rpc.statd:  1831-119 unable to register                                         
 (SM_PROG, SM_VERS,udp)                                              

Answer:

We tried the following:

 1) Verify that the portmap, rpc.lockd, and rpc.statd subsystems
    are all active; run the command 'lssrc -a', and look at the 
    status of these subsystems.

 2) If the subsystems are active, stop each of them with the
    command 'stopsrc -s \'.

 3) Run the command 'rm -rf /etc/sm /etc/sm.bak' to get rid
    of any files that may be in these directories.

 4) Uncomment the line in /etc/rc.tcpip that starts the 
    portmap daemon.

The portmap wasn't starting by the script

mount | grep ' /usr *nfs' 2>&1 > /dev/null
if [ "$?" -ne 0 ]
then
REMOTE_USR="N"
start /usr/etc/portmap "$src_running"
fi

and the same was happening with lockd and statd.

After a long time we realized that the /usr file system gets 
mounted twice in the /etc/filesystems file. There was an old 
entry for /usr file system along with the new one. The old 
entry was commented out with asteriks, but evidently, the entry 
was still read and mounted. After we've completely removed this 
entry from the /etc/filesystems , the user directory was only
mounted once. 

With the /usr directory being started twice, the script in 
/etc/rc.tcpip was getting the '*nfs' entries from the grep 
command which was resulting in incorrect output. Thus portmap
wasn't started.



Support Line: lockd and statd error messages. ITEM: AB8013L

Dated: December 1994 Category: N/A

This HTML file was generated 99/06/24~13:30:31

Comments or suggestions?
Contact us