11.31 lockmgr/rpc.statd...nfs setup

[Coburn Watson]

Hello,

We are running 11.31 on an rx2620. I am attempting to create an NFS share and following the instructions in the online 11.31 sysadmin docs for setting up NFS.

1. When I attempt to start the nfs server via:

/sbin/init.d/nfs.server start

I get the following:

ERROR: rpc.statd not running. Run "/sbin/init.d/lockmgr start" to start rpc.statd, exiting

2. Stop then start lockmgr:

# /sbin/init.d/lockmgr stop
killing rpc.lockd

# /sbin/init.d/lockmgr start
Starting up the Status Monitor daemon
/usr/sbin/rpc.statd
Starting up the lock manager daemon
/usr/sbin/rpc.lockd

3. Try to start nfs server again:

# /sbin/init.d/nfs.server start
ERROR: rpc.statd not running. Run "/sbin/init.d/lockmgr start" to start rpc.statd, exiting

Same message, anyone have any recommendations or come across this.


Thanks,
Coburn

[Steven E. Protter]

Shalom Coburn,

The options in /etc/exports could be causing trouble, so please post that.

Add a set -x to the startup script of both nfs.server and lockmanager.

Lets look and see if we can find out which line of code is failing, that might be helpful in diagnosis.

I've seen this message before from a variety of causes, most of which had to do with configuration files, permissions or lack of patching. Since the OS is new, I doubt there are a lot of helpful NFS patches, but do install the bi-annual update when it comes out in a few months.

SEP

[Coburn Watson]

Hello Steven,

My /etc/exports is empty and I am using /etc/dfs/dfstab as the documentation indicates that /etc/exports has been deprecated; let me know if that is not the case.

When I execute the lockmgr start command I get the following output:

# /sbin/init.d/lockmgr start
+ unset UNIX95
+ PATH=/sbin:/usr/sbin:/usr/bin:/usr/lib/netsvc:/usr/lib/netsvc/yp
+ export PATH
+ rval=0
+ [ -f /etc/rc.config.d/nfsconf ]
+ . /etc/rc.config.d/nfsconf
+ NFS_CORE=1
+ RPCBIND_OPTIONS=
+ LOCKMGR=1
+ LOCKD_OPTIONS=
+ STATD_OPTIONS=
+ NFS_CLIENT=1
+ NFS_SERVER=1
+ PCNFS_SERVER=0
+ START_NFSLOGD=0
+ START_MOUNTD=1
+ MOUNTD_OPTIONS=
+ AUTOFS=1
+ AUTOMOUNT_OPTIONS=
+ AUTOMOUNTD_OPTIONS=
+ AUTO_MASTER=/etc/auto_master
+ [ 1 -a 1 -ne 1 ]
+ [ 1 -a 1 -ne 1 ]
+ + findproc rpcbind
pid=1275
+ [ -z 1275 ]
+ [ -eq 0 ]
+ echo Starting up the Status Monitor daemon
Starting up the Status Monitor daemon
+ + findproc rpc.statd
pid=
+ [ -z ]
+ [ -x /usr/sbin/rpc.statd ]
+ echo \t/usr/sbin/rpc.statd
/usr/sbin/rpc.statd
+ /usr/sbin/rpc.statd
+ set_return
+ echo Starting up the lock manager daemon
Starting up the lock manager daemon
+ + findproc rpc.lockd
pid=
+ [ -z ]
+ [ -x /usr/sbin/rpc.lockd ]
+ echo \t/usr/sbin/rpc.lockd
/usr/sbin/rpc.lockd
+ /usr/sbin/rpc.lockd
+ set_return


It looks like the rpc.statd daemon isn't starting:

# ps -ef|grep rpc
root 31 0 0 Aug 7 ? 0:00 krpckd
root 21004 17545 0 11:33:41 pts/0 0:00 grep rpc
root 1275 1 0 Aug 7 ? 0:00 /usr/sbin/rpcbind
root 1948 1 0 Aug 7 ? 0:00 /opt/dce/sbin/rpcd
root 20979 1 0 11:30:38 ? 0:00 /usr/sbin/rpc.lockd


I do see this process however:
# ps -ef|grep stat
root 3 0 0 Aug 7 ? 0:13 statdaemon

Is that the statd daemon?

I made an entry in my /etc/dfs/dfstab file but the same error was occurring with or without this entry. I've also pasted the debug output from the nfs.server start command below:


# /sbin/init.d/nfs.server start
+ unset UNIX95
+ PATH=/sbin:/usr/sbin:/usr/bin:/usr/lib/netsvc:/usr/lib/netsvc/yp
+ export PATH
+ rval=0
+ [ -f /etc/rc.config.d/nfsconf ]
+ . /etc/rc.config.d/nfsconf
+ NFS_CORE=1
+ RPCBIND_OPTIONS=
+ LOCKMGR=1
+ LOCKD_OPTIONS=
+ STATD_OPTIONS=
+ NFS_CLIENT=1
+ NFS_SERVER=1
+ PCNFS_SERVER=0
+ START_NFSLOGD=0
+ START_MOUNTD=1
+ MOUNTD_OPTIONS=
+ AUTOFS=1
+ AUTOMOUNT_OPTIONS=
+ AUTOMOUNTD_OPTIONS=
+ AUTO_MASTER=/etc/auto_master
+ [ 1 -a 1 -ne 1 ]
+ [ 1 -ne 1 ]
+ + findproc rpcbind
pid=1275
+ [ -z 1275 ]
+ [ -eq 0 ]
+ + findproc rpc.statd
pid=
+ [ -z ]
+ echo ERROR: rpc.statd not running. Run "/sbin/init.d/lockmgr start" to start rpc.statd, exiting
ERROR: rpc.statd not running. Run "/sbin/init.d/lockmgr start" to start rpc.statd, exiting
+ exit 1
#

[Dave Olker]

Hi Coburn,

Are there any messages in the /var/adm/syslog/syslog.log file pertaining to RPC?

Dave

[Coburn Watson]

I don't see any messages when I execute the nfs.server start (beyond what is on stdout) but I do see the following when I execute "lockmgr start":

Aug 14 11:23:08 labmvitg23 statd[5473]: svc_tp_create: Could not register prog 100024 vers 1 on udp
Aug 14 11:22:18 labmvitg23 vmunix: NOTICE: USB device detached. Identification String:
Aug 14 11:23:08 labmvitg23 statd[5473]: svc_tp_create: Could not register prog 100024 vers 1 on tcp
Aug 14 11:23:08 labmvitg23 vmunix: tunopen(): CLONEOPEN not allowed
Aug 14 11:23:08 labmvitg23 statd[5473]: svc_tp_create: Could not register prog 100024 vers 1 on ticlts
Aug 14 11:23:08 labmvitg23 statd[5473]: svc_tli_create: could not open connection for ticotsord
Aug 14 11:23:08 labmvitg23 statd[5473]: svc_tp_create: Could not register prog 100024 vers 1 on ticots
Aug 14 11:23:08 labmvitg23 vmunix: tunopen(): CLONEOPEN not allowed
Aug 14 11:23:08 labmvitg23 statd[5473]: statd: unable to create (SM_PROG, SM_VERS) for netpath.
Aug 14 11:23:19 labmvitg23 vmunix: tunopen(): CLONEOPEN not allowed

- Coburn

[Dave Olker]

Ok, that's what I was looking for. Yours is the second report of this problem I've seen. Let me do some investigation and get back to you.

Dave

[Dave Olker]

I think this is a known problem that was supposed to be fixed prior to 11i v3 shipping but it may have reappeared somehow. It may be a corrupted /stand/ioconfig file.

Try this:

# /sbin/init.d/nfs.server stop
# /sbin/init.d/autofs stop
# /sbin/init.d/nfs.client stop
# /sbin/init.d/lockmgr stop
# /sbin/init.d/nfs.core stop

Then rebuild your /stand/ioconfig file by issuing the command:

# insf -e

Then see if you can get all the RPC daemons to start normally:

# /sbin/init.d/nfs.core start
# /sbin/init.d/lockmgr start
# /sbin/init.d/nfs.client start
# /sbin/init.d/autofs start
# /sbin/init.d/nfs.server start

Let me know if this works.

Regards,

Dave

[Coburn Watson]

That did it. Thanks!

[Coburn Watson]

Dave indicated that a known fix which was supposed to go out with 11v3 might not have. After running the commands it was resolved.