[Gluster-users] NFS mount

Thu Aug 20 10:03:49 UTC 2015

----- Original Message -----
> From: "shacky" <shacky83 at gmail.com>
> To: "Rajesh Joseph" <rjoseph at redhat.com>
> Cc: "Soumya Koduri" <skoduri at redhat.com>, "gluster-users" <gluster-users at gluster.org>
> Sent: Thursday, August 20, 2015 2:36:58 PM
> Subject: Re: [Gluster-users] NFS mount
> 
> Hi all.
> I'm trying to do some tests on node1 too, and I'm having the same problems.
> 
> root at node1 ~ # rpcinfo -p
>    program vers proto   port  service
>     100000    4   tcp    111  portmapper
>     100000    3   tcp    111  portmapper
>     100000    2   tcp    111  portmapper
>     100000    4   udp    111  portmapper
>     100000    3   udp    111  portmapper
>     100000    2   udp    111  portmapper
>     100021    3   udp  37308  nlockmgr
>     100021    4   udp  37308  nlockmgr
>     100021    3   tcp  56406  nlockmgr
>     100021    4   tcp  56406  nlockmgr
>     100005    3   tcp  38465  mountd
>     100005    1   tcp  38466  mountd
>     100003    3   tcp   2049  nfs
>     100024    1   udp  37592  status
>     100024    1   tcp  52430  status
>     100021    1   udp    756  nlockmgr
> 
> Gluster is not running:
> 
> root at node1 ~ # ps ax|grep gluster
>  987904 pts/1    S+     0:00 grep gluster
> 
> I don't have nfs-kernel-server installed on this system, only
> nfs-common (which I also restarted):
> 
> root at node1 ~ # service nfs-common restart
> Stopping NFS common utilities: idmapd statd.
> Starting NFS common utilities: statd idmapd.
> 
> I restarted rpcbind:
> 
> root at node1 ~ # service rpcbind restart
> Stopping rpcbind daemon....
> Starting rpcbind daemon....
> 
> Then I started Gluster:
> 
> root at node1 ~ # service glusterfs-server start
> Starting glusterd service: glusterd.
> 
> But the NFS server is not started on Gluster:
> 
> [2015-08-20 09:04:26.886555] I [glusterfsd.c:1959:main]
> 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version
> 3.5.2 (/usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p
> /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log -S
> /var/run/4a953fc123a9286e647595c25ecaee31.socket)
> [2015-08-20 09:04:26.887553] I [socket.c:3561:socket_init]
> 0-socket.glusterfsd: SSL support is NOT enabled
> [2015-08-20 09:04:26.887580] I [socket.c:3576:socket_init]
> 0-socket.glusterfsd: using system polling thread
> [2015-08-20 09:04:26.887652] I [socket.c:3561:socket_init]
> 0-glusterfs: SSL support is NOT enabled
> [2015-08-20 09:04:26.887663] I [socket.c:3576:socket_init]
> 0-glusterfs: using system polling thread
> [2015-08-20 09:04:26.889610] I [glusterfsd.c:1959:main]
> 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version
> 3.5.2 (/usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p
> /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log -S
> /var/run/4a953fc123a9286e647595c25ecaee31.socket)
> [2015-08-20 09:04:26.889688] E
> [glusterfsd.c:1531:glusterfs_pidfile_setup] 0-glusterfsd: pidfile
> /var/lib/glusterd/nfs/run/nfs.pid lock error (Resource temporarily
> unavailable)
> [2015-08-20 09:04:26.895180] I
> [rpcsvc.c:2127:rpcsvc_set_outstanding_rpc_limit] 0-rpc-service:
> Configured rpc.outstanding-rpc-limit with value 16
> [2015-08-20 09:04:26.901656] I [socket.c:3561:socket_init]
> 0-socket.nfs-server: SSL support is NOT enabled
> [2015-08-20 09:04:26.901677] I [socket.c:3576:socket_init]
> 0-socket.nfs-server: using system polling thread
> [2015-08-20 09:04:26.902352] I [socket.c:3561:socket_init]
> 0-socket.nfs-server: SSL support is NOT enabled
> [2015-08-20 09:04:26.902372] I [socket.c:3576:socket_init]
> 0-socket.nfs-server: using system polling thread
> [2015-08-20 09:04:26.903054] I [socket.c:3561:socket_init]
> 0-socket.nfs-server: SSL support is NOT enabled
> [2015-08-20 09:04:26.903078] I [socket.c:3576:socket_init]
> 0-socket.nfs-server: using system polling thread
> [2015-08-20 09:04:26.903507] I [socket.c:3561:socket_init]
> 0-socket.NLM: SSL support is NOT enabled
> [2015-08-20 09:04:26.903517] I [socket.c:3576:socket_init]
> 0-socket.NLM: using system polling thread
> [2015-08-20 09:04:26.910430] E
> [rpcsvc.c:1314:rpcsvc_program_register_portmap] 0-rpc-service: Could
> not register with portmap
> [2015-08-20 09:04:26.910471] E [nfs.c:332:nfs_init_versions] 0-nfs:
> Program  NLM4 registration failed
> [2015-08-20 09:04:26.910484] E [nfs.c:1312:init] 0-nfs: Failed to
> initialize protocols
> [2015-08-20 09:04:26.910495] E [xlator.c:403:xlator_init]
> 0-nfs-server: Initialization of volume 'nfs-server' failed, review
> your volfile again
> [2015-08-20 09:04:26.910509] E [graph.c:307:glusterfs_graph_init]
> 0-nfs-server: initializing translator failed
> [2015-08-20 09:04:26.910519] E [graph.c:502:glusterfs_graph_activate]
> 0-graph: init failed
> [2015-08-20 09:04:26.910740] W [glusterfsd.c:1095:cleanup_and_exit]
> (-->/usr/lib/x86_64-linux-gnu/libgfrpc.so.0(rpc_clnt_handle_reply+0xa4)
> [0x7f6cefb7dae4] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x307)
> [0x40c557] (-->/usr/sbin/glusterfs(glusterfs_process_volfp+0x106)
> [0x408306]))) 0-: received signum (0), shutting down
> pending frames:
> 
> I'm still having the "Could not register with portmap" error.
> 
> Please note that I have one NFS share mounted on this node, could this
> cause the problem?
> 

AFAIK, you are not suppose to do NFS mount on the same node where
gluster NFS server is running due to NLM locking.