On Mon, Oct 27, 2014 at 3:38 PM, walt <w41...@gmail.com> wrote:
>
> Last night when I powered off my machines NFS was working perfectly. Today
> it's broken again for the nth time:
>
> #systemctl status nfs-server
> ● nfs-server.service - NFS server and services
> Loaded: loaded (/usr/lib64/systemd/system/nfs-server.service; enabled)
> Active: failed (Result: exit-code) since Mon 2014-10-27 11:50:38 PDT;
> 25min ago
> Process: 896 ExecStopPost=/usr/sbin/exportfs -f (code=exited,
> status=0/SUCCESS)
> Process: 893 ExecStopPost=/usr/sbin/exportfs -au (code=exited,
> status=0/SUCCESS)
> Process: 939 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited,
> status=1/FAILURE)
> Process: 936 ExecStartPre=/usr/sbin/exportfs -r (code=exited,
> status=0/SUCCESS)
> Main PID: 939 (code=exited, status=1/FAILURE)
>
> Oct 27 11:50:38 a6 rpc.nfsd[939]: rpc.nfsd: writing fd to kernel failed:
> errno 111 (Connection refused)
> Oct 27 11:50:38 a6 rpc.nfsd[939]: rpc.nfsd: unable to set any sockets for nfsd
> Oct 27 11:50:38 a6 systemd[1]: nfs-server.service: main process exited,
> code=exited, status=1/FAILURE
> Oct 27 11:50:38 a6 systemd[1]: Failed to start NFS server and services.
> Oct 27 11:50:38 a6 systemd[1]: Unit nfs-server.service entered failed state.
>
> #rpc.nfsd -d
> rpc.nfsd: Checking netconfig for visible protocols.
> rpc.nfsd: Enabling inet udp.
> rpc.nfsd: Enabling inet tcp.
> rpc.nfsd: Enabling inet6 udp.
> rpc.nfsd: Enabling inet6 tcp.
> rpc.nfsd: knfsd is currently down
> rpc.nfsd: Writing version string to kernel: -2 +3 +4
> rpc.nfsd: Creating inet TCP socket.
> rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
> rpc.nfsd: Creating inet6 TCP socket.
> rpc.nfsd: writing fd to kernel failed: errno 97 (Address family not supported
> by protocol)
> rpc.nfsd: unable to set any sockets for nfsd
Is rpcbind.service running?
Does "rpcbind -p" output the usual programs/ports/...?
Are the nfs-api-filesystems mounted? ("/var/lib/nfs/rpc_pipefs" and
"/proc/fs/nfsd")
