nlockmgr and the 11.31 NFS stack

[Francis Noël]

Hello forum people !

I am setting up NFS on some new-to-me 11.31 boxes and there is some trouble on the client side.

All configuration has been kept at the default settings, save from enabling PCNFSD.

The problem I have is that some hummingbird maestro enabled windows hosts (ugh!) cannot find their lock manager on the 11.31 servers.

I compared the rpcinfo output with some functional 11.11 hosts and the only difference I can spot is that the 11.11's run llockmgr and nlockmgr in the rpc stack. The windows admin has kind-of-confirmed taht the maestro client relies on nlockmgr.

So, how do I configure the rpc server to get nlockmgr and llockmgr fired up ? Only metion of it I found is in /etc/rpc.

Thank you !

[Dave Olker]

Hello Francis,

Are you saying the nlockmgr is not running on the 11.31 system? If you issue this command on the 11.31 system:

# rpcinfo -p | grep nlockmgr

you should see this:

# rpcinfo -p | grep nlockmgr
100021 1 udp 4045 nlockmgr
100021 2 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 2 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 4 tcp 4045 nlockmgr

Please let me know if you get output similar to this. If not, make sure LOCKMGR is enabled in your nfsconf file:

# grep ^LOCKMGR /etc/rc.config.d/nfsconf
LOCKMGR=1

Thanks,

Dave

[Francis Noël]

Hello Dave and thak you for your interest.

This issue has been resolved with some help from Eric Wilford at Hp Software Support.

I'll post the outcome here in case someone else runs into this.

First some important background :
This host was booted over four months ago and at the time it was not setup for NFS.
The NFS services were brought up very recently, following a user request.



rpcinfo looked like this :
rpcinfo
program version netid address service owner
100000 4 ticots lhbd03pd.rpc rpcbind superuser
100000 3 ticots lhbd03pd.rpc rpcbind superuser
100000 4 ticotsord lhbd03pd.rpc rpcbind superuser
100000 3 ticotsord lhbd03pd.rpc rpcbind superuser
100000 4 ticlts lhbd03pd.rpc rpcbind superuser
100000 3 ticlts lhbd03pd.rpc rpcbind superuser
100000 4 tcp 0.0.0.0.0.111 rpcbind superuser
100000 3 tcp 0.0.0.0.0.111 rpcbind superuser
100000 2 tcp 0.0.0.0.0.111 rpcbind superuser
100000 4 udp 0.0.0.0.0.111 rpcbind superuser
100000 3 udp 0.0.0.0.0.111 rpcbind superuser
100000 2 udp 0.0.0.0.0.111 rpcbind superuser
100231 1 ticlts lhbd03pd.nfsauth - superuser
100231 1 ticotsord lhbd03pd.nfsauth - superuser
100231 1 ticots lhbd03pd.nfsauth - superuser
100005 1 udp 0.0.0.0.237.63 mountd superuser
100005 1 ticlts \000\000\020\255 mountd superuser
100005 1 tcp 0.0.0.0.219.30 mountd superuser
100005 1 ticotsord \000\000\020\262 mountd superuser
100005 1 ticots \000\000\020\265 mountd superuser
100005 2 udp 0.0.0.0.237.63 mountd superuser
100005 2 ticlts \000\000\020\255 mountd superuser
100005 2 tcp 0.0.0.0.219.30 mountd superuser
100005 2 ticotsord \000\000\020\262 mountd superuser
100005 2 ticots \000\000\020\265 mountd superuser
100005 3 udp 0.0.0.0.237.63 mountd superuser
100005 3 ticlts \000\000\020\255 mountd superuser
100005 3 tcp 0.0.0.0.219.30 mountd superuser
100005 3 ticotsord \000\000\020\262 mountd superuser
100005 3 ticots \000\000\020\265 mountd superuser
100003 2 udp 0.0.0.0.8.1 nfs superuser
100003 3 udp 0.0.0.0.8.1 nfs superuser
100227 2 udp 0.0.0.0.8.1 - superuser
100227 3 udp 0.0.0.0.8.1 - superuser
100003 2 tcp 0.0.0.0.8.1 nfs superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
100227 2 tcp 0.0.0.0.8.1 - superuser
100227 3 tcp 0.0.0.0.8.1 - superuser
100166 1 ticotsord lhbd03pd.nfsmapid - superuser
150001 1 udp 0.0.0.0.3.190 pcnfsd superuser
150001 2 udp 0.0.0.0.3.190 pcnfsd superuser
150001 1 tcp 0.0.0.0.3.190 pcnfsd superuser
150001 2 tcp 0.0.0.0.3.190 pcnfsd superuser
1073741824 1 tcp 0.0.0.0.223.253 - superuser


Notice that the lock managers were absent from the registered RPC programs. They should have been there since they are in /etc/rpc.


Software Support spotted the clue in this ps output :
# ps -ef | grep rpc
root 27 0 0 Feb 14 ? 0:00 krpckd
daemon 1043 1 0 Feb 14 ? 0:00 /usr/sbin/rpc.statd
root 1049 1 0 Feb 14 ? 0:00 /usr/sbin/rpc.lockd
root 1457 1 0 Feb 14 ? 0:36 /opt/dce/sbin/rpcd
root 4548 1 0 11:08:22 ? 0:00 /usr/sbin/rpcbind
root 4580 1 0 11:08:28 ? 0:00 /usr/sbin/rpc.mountd
root 17291 16832 1 10:29:47 pts/1 0:00 grep rpc
root 4598 1 0 11:08:28 ? 0:00 /usr/sbin/rpc.pcnfsd

Notice that some daemons have a start date back in feb. and that others had been started recently. Software Support suggested that I use the lockd startup script /sbin/lockmgr to restart those daemons.

# cd /sbin
# cd init.d
# ./lockmgr stop
killing rpc.lockd
killing rpc.statd
# ./lockmgr start
Starting up the Status Monitor daemon
/usr/sbin/rpc.statd
Starting up the lock manager daemon
/usr/sbin/rpc.lockd
# rpcinfo
program version netid address service owner
100000 4 ticots lhbd03pd.rpc rpcbind superuser
100000 3 ticots lhbd03pd.rpc rpcbind superuser
100000 4 ticotsord lhbd03pd.rpc rpcbind superuser
100000 3 ticotsord lhbd03pd.rpc rpcbind superuser
100000 4 ticlts lhbd03pd.rpc rpcbind superuser
100000 3 ticlts lhbd03pd.rpc rpcbind superuser
100000 4 tcp 0.0.0.0.0.111 rpcbind superuser
100000 3 tcp 0.0.0.0.0.111 rpcbind superuser
100000 2 tcp 0.0.0.0.0.111 rpcbind superuser
100000 4 udp 0.0.0.0.0.111 rpcbind superuser
100000 3 udp 0.0.0.0.0.111 rpcbind superuser
100000 2 udp 0.0.0.0.0.111 rpcbind superuser
100231 1 ticlts lhbd03pd.nfsauth - superuser
100003 2 udp 0.0.0.0.8.1 nfs superuser
100003 3 udp 0.0.0.0.8.1 nfs superuser
100227 2 udp 0.0.0.0.8.1 - superuser
100227 3 udp 0.0.0.0.8.1 - superuser
100003 2 tcp 0.0.0.0.8.1 nfs superuser
100231 1 ticotsord lhbd03pd.nfsauth - superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
100227 2 tcp 0.0.0.0.8.1 - superuser
100227 3 tcp 0.0.0.0.8.1 - superuser
100231 1 ticots lhbd03pd.nfsauth - superuser
100005 1 udp 0.0.0.0.248.65 mountd superuser
100005 1 ticlts \000\000\021* mountd superuser
100005 1 tcp 0.0.0.0.200.225 mountd superuser
100005 1 ticotsord \000\000\021/ mountd superuser
100005 1 ticots \000\000\0212 mountd superuser
100005 2 udp 0.0.0.0.248.65 mountd superuser
100005 2 ticlts \000\000\021* mountd superuser
100005 2 tcp 0.0.0.0.200.225 mountd superuser
100005 2 ticotsord \000\000\021/ mountd superuser
100005 2 ticots \000\000\0212 mountd superuser
100005 3 udp 0.0.0.0.248.65 mountd superuser
100005 3 ticlts \000\000\021* mountd superuser
100005 3 tcp 0.0.0.0.200.225 mountd superuser
100005 3 ticotsord \000\000\021/ mountd superuser
100005 3 ticots \000\000\0212 mountd superuser
100166 1 ticotsord lhbd03pd.nfsmapid - superuser
150001 1 udp 0.0.0.0.3.204 pcnfsd superuser
150001 2 udp 0.0.0.0.3.204 pcnfsd superuser
150001 1 tcp 0.0.0.0.3.204 pcnfsd superuser
150001 2 tcp 0.0.0.0.3.204 pcnfsd superuser
100024 1 udp 0.0.0.0.242.83 status superuser
100024 1 tcp 0.0.0.0.200.116 status superuser
100024 1 ticlts \000\000\021W status superuser
100024 1 ticotsord \000\000\021Z status superuser
100024 1 ticots \000\000\021] status superuser
100133 1 udp 0.0.0.0.242.83 - superuser
100133 1 tcp 0.0.0.0.200.116 - superuser
100133 1 ticlts \000\000\021W - superuser
100133 1 ticotsord \000\000\021Z - superuser
100133 1 ticots \000\000\021] - superuser
100021 1 udp 0.0.0.0.15.205 nlockmgr superuser
100021 2 udp 0.0.0.0.15.205 nlockmgr superuser
100021 3 udp 0.0.0.0.15.205 nlockmgr superuser
100021 4 udp 0.0.0.0.15.205 nlockmgr superuser
100021 1 tcp 0.0.0.0.15.205 nlockmgr superuser
100021 2 tcp 0.0.0.0.15.205 nlockmgr superuser
100021 3 tcp 0.0.0.0.15.205 nlockmgr superuser
100021 4 tcp 0.0.0.0.15.205 nlockmgr superuser


A test was conducted with the Windows clients that previously had trouble connecting and all is well.


So there you are : the lock managers have their own startup script under 11.31. If you activate the NFS Server in nfsconf and then start it up with /sbin/init.d/nfs.server you might need to bounce the lockmgr startup script to have the required RPC programs register.

Hope this helps!

[Francis Noël]

Bounced the lock managers after starting nfs.server, see details in the previous post.