Hi,
When I restart NFS with=20
/etc/init.d/nfs-kernel-server restart
I see these messages in syslog:
May=A0 3 13:57:15 server mountd[928]: Caught signal 15, un-registering =
and exiting.
May=A0 3 13:57:15 serverkernel: [82562.372930] nfsd: last server has ex=
ited, flushing export cache
May=A0 3 13:57:16 serverkernel: [82563.499249] svc: failed to register =
lockdv1 RPC service (errno 97).
May=A0 3 13:57:16 serverkernel: [82563.501211] NFSD: Using /var/lib/nfs=
/v4recovery as the NFSv4 state recovery directory
May=A0 3 13:57:16 serverkernel: [82563.501246] NFSD: starting 90-second=
grace period
=A0
How can I fix that failure?
// Naderan *Mahmood;
On May 3, 2011, at 5:30 AM, Mahmood Naderan wrote:
> Hi,
> When I restart NFS with
>
>
> /etc/init.d/nfs-kernel-server restart
>
>
> I see these messages in syslog:
>
> May 3 13:57:15 server mountd[928]: Caught signal 15, un-registering and exiting.
> May 3 13:57:15 serverkernel: [82562.372930] nfsd: last server has exited, flushing export cache
> May 3 13:57:16 serverkernel: [82563.499249] svc: failed to register lockdv1 RPC service (errno 97).
> May 3 13:57:16 serverkernel: [82563.501211] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
> May 3 13:57:16 serverkernel: [82563.501246] NFSD: starting 90-second grace period
>
>
> How can I fix that failure?
IIRC, that usually means the kernel has attempted to register an IPv6 listener with the local portmapper, which doesn't support IPv6. The message was removed in a later kernel.
To be sure it's harmless, after NFSD is running, verify that lockd is registered by running "rpcinfo -p" on your server.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com