You are not logged in.

#1 2015-09-24 15:09:01

Watnuss
Member
Registered: 2013-03-04
Posts: 53

nfs4-server not starting

Hi, I cannot help myself any more. I have no idea what is going wrong. Maybe someone may help me get to the cause of my problem.

I was running a nfs4 only share like the wiki page suggested for several months and now it broke. I couldn'f fix it so I tried to reinstall/configure the whole setup. So I basicly followed each step at https://wiki.archlinux.org/index.php/NFS#Server

My setup looks like:

/etc/exports

/srv/nfs4 192.168.0.0/24(rw,fsid=root,no_subtree_check)
/srv/nfs4/files 192.168.0.0/24(rw,no_subtree_check,nohide)

/etc/conf.d/nfs-server.conf

NFSD_OPTS="-N 2 -N 3"

/etc/fstab

/home/watnuss/files /srv/nfs4/files none bind 0 0

With this setup my server reboots into an emergency shell as it failes the mount --bind (manually doing so works) and because of the failing nfs-server daemon:
jounal log for failing nfs-server:

Sep 24 16:45:11 odroid systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Sep 24 16:45:11 odroid systemd[1]: Starting NFS Mount Daemon...
Sep 24 16:45:11 odroid rpc.statd[352]: Version 1.3.2 starting
Sep 24 16:45:11 odroid rpc.statd[352]: Flags: TI-RPC
Sep 24 16:45:11 odroid systemd[1]: Starting NFSv4 ID-name mapping service...
Sep 24 16:45:11 odroid rpc.statd[352]: Failed to read /var/lib/nfs/state: Success
Sep 24 16:45:11 odroid rpc.statd[352]: Initializing NSM state
Sep 24 16:45:11 odroid rpc.statd[352]: Running as root.  chown /var/lib/nfs to choose different user
Sep 24 16:45:11 odroid rpc.statd[352]: failed to create RPC listeners, exiting
Sep 24 16:45:11 odroid rpc.mountd[351]: Could not bind socket: (98) Address already in use
Sep 24 16:45:11 odroid rpc.mountd[351]: Could not bind socket: (98) Address already in use
Sep 24 16:45:11 odroid systemd[1]: rpc-statd.service: Control process exited, code=exited status=1
Sep 24 16:45:11 odroid rpc.idmapd[353]: rpc.idmapd: Skipping configuration file "/etc/idmapd.conf": No such file or directory
Sep 24 16:45:11 odroid rpc.idmapd[355]: Unable to open '/proc/sys/fs/nfs/idmap_cache_timeout' to set client cache expiration time to
Sep 24 16:45:11 odroid rpc.mountd[351]: Could not bind socket: (98) Address already in use
Sep 24 16:45:11 odroid rpc.mountd[351]: Could not bind socket: (98) Address already in use
Sep 24 16:45:11 odroid rpc.mountd[351]: mountd: No V2 or V3 listeners created!
Sep 24 16:45:11 odroid rpc.mountd[356]: Version 1.3.2 starting
Sep 24 16:45:11 odroid systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Sep 24 16:45:11 odroid systemd[1]: rpc-statd.service: Unit entered failed state.
Sep 24 16:45:11 odroid systemd[1]: rpc-statd.service: Failed with result 'exit-code'.
Sep 24 16:45:11 odroid systemd[1]: Started NFS Mount Daemon.
Sep 24 16:45:11 odroid systemd[1]: Started NFSv4 ID-name mapping service.
Sep 24 16:45:11 odroid systemd[1]: Starting NFS server and services...
Sep 24 16:45:11 odroid rpc.nfsd[360]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
Sep 24 16:45:11 odroid kernel: svc: failed to register nfsdv4 RPC service (errno 111).
Sep 24 16:45:11 odroid rpc.nfsd[360]: rpc.nfsd: unable to set any sockets for nfsd
Sep 24 16:45:11 odroid systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE
Sep 24 16:45:11 odroid kernel: svc: failed to register nfsdv4 RPC service (errno 97).
Sep 24 16:45:11 odroid systemd[1]: Failed to start NFS server and services.
Sep 24 16:45:11 odroid systemd[1]: nfs-server.service: Unit entered failed state.
Sep 24 16:45:11 odroid systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Sep 24 16:45:11 odroid systemd[1]: Stopping NFS Mount Daemon...
Sep 24 16:45:11 odroid rpc.mountd[356]: Caught signal 15, un-registering and exiting.
Sep 24 16:45:11 odroid systemd[1]: Stopping NFSv4 ID-name mapping service...
Sep 24 16:45:11 odroid polkitd[316]: Unregistered Authentication Agent for unix-process:312:41515 (system bus name :1.10, object pat
Sep 24 16:45:11 odroid systemd[1]: Starting Notify NFS peers of a restart...
Sep 24 16:45:11 odroid sm-notify[365]: Version 1.3.2 starting
Sep 24 16:45:11 odroid systemd[1]: Stopped NFSv4 ID-name mapping service.
Sep 24 16:45:11 odroid systemd[1]: Stopped NFS Mount Daemon.
Sep 24 16:45:11 odroid systemd[1]: Started Notify NFS peers of a restart.

Maybe it has something to do with the avahi-daemon which also fails:

avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2015-09-24 17:06:00 CEST; 12s ago
  Process: 238 ExecStart=/usr/bin/avahi-daemon -s (code=exited, status=255)
 Main PID: 238 (code=exited, status=255)
   Status: "avahi-daemon 0.6.31 starting up."

Sep 24 17:06:00 odroid avahi-daemon[238]: avahi-daemon 0.6.31 starting up.
Sep 24 17:06:00 odroid systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Sep 24 17:06:00 odroid avahi-daemon[238]: Successfully called chroot().
Sep 24 17:06:00 odroid avahi-daemon[238]: Successfully dropped remaining capabilities.
Sep 24 17:06:00 odroid avahi-daemon[238]: Loading service file /services/sftp-ssh.service.
Sep 24 17:06:00 odroid avahi-daemon[238]: Loading service file /services/ssh.service.
Sep 24 17:06:00 odroid avahi-daemon[238]: SO_REUSEPORT failed: Protocol not available
Sep 24 17:06:00 odroid systemd[1]: avahi-daemon.service: Main process exited, code=exited, status=255/n/a
Sep 24 17:06:00 odroid systemd[1]: avahi-daemon.service: Unit entered failed state.
Sep 24 17:06:00 odroid systemd[1]: avahi-daemon.service: Failed with result 'exit-code'.

I hope someone sees what I am missing. I would be really glad to get some hints where to look at next.

Best regards,

watnuss

Last edited by Watnuss (2015-09-24 15:09:23)

Offline

#2 2015-09-24 17:00:20

pekka
Member
Registered: 2011-07-21
Posts: 104

Re: nfs4-server not starting

192.168.0.0 is strange ip address.

192.168.0.0 it is reserved for network address.

Offline

#3 2015-09-24 19:17:57

Watnuss
Member
Registered: 2013-03-04
Posts: 53

Re: nfs4-server not starting

That's because it's not an ip address which I wanna export to but my whole LAN subnet. My home network is setup to be in a 192.168.0.0/24 subnet. This is intentional and should not be a problem as it is also suggested in man exports.

Last edited by Watnuss (2015-09-24 19:18:19)

Offline

#4 2015-09-24 19:28:09

dcdriving
Member
From: United Kingdom
Registered: 2015-01-20
Posts: 70

Re: nfs4-server not starting

I have meant to do this but never got round to it as I just accepted I needed rpcbind (it worked with it so hey!) but have a read as this may be your problem
edit: wiki has been updated with this link since.  sorry if you have already read it.

Last edited by dcdriving (2015-09-24 19:36:53)

Offline

Board footer

Powered by FluxBB