Nfs server did not start

I have a fedora 31 server with nfs server installed. Suddenly the nfs-server service wont start again. It is in the status activating (start-pre). All other services rpcbind, rpc-gssd, nfs-mountd etc. are running. Has anyone a hint for me why the nfs-server is not starting?

1 Like

   Hi @markusroth.  Did you’d tried the updates and reboot (just to see if this service can work at all for now)?

First run:

systemctl restart nfs-server.service
journalctl -xe -u nfs-server.service

and then give us the output of the last restart attempt.

2 Likes

Hi Alph4Num3ric here is the output of the last restart attempt:

Mär 23 07:59:20 my-nfs-server systemd[1]: nfs-server.service: Control process exited, code=killed, status=15/TERM
– Subject: Unit process exited
– Defined-By: systemd


– An n/a= process belonging to unit nfs-server.service has exited.

– The process’ exit code is ‘killed’ and its exit status is 15.

Mär 23 08:00:50 my-nfs-server systemd[1]: nfs-server.service: Control process exited, code=killed, status=15/TERM
– Subject: Unit process exited
– Defined-By: systemd


– An ExecStopPost= process belonging to unit nfs-server.service has exited.

– The process’ exit code is ‘killed’ and its exit status is 15.
Mär 23 08:00:50 my-nfs-server systemd[1]: nfs-server.service: Failed with result ‘signal’.
– Subject: Unit failed
– Defined-By: systemd


– The unit nfs-server.service has entered the ‘failed’ state with result ‘signal’.
Mär 23 08:00:50 my-nfs-server systemd[1]: Stopped NFS server and services.
– Subject: A stop job for unit nfs-server.service has finished
– Defined-By: systemd


– A stop job for unit nfs-server.service has finished.

– The job identifier is 3947 and the job result is done.
Mär 23 08:03:52 my-nfs-server systemd[1]: nfs-server.service: Found left-over process 928 (rpc.nfsd) in control group while starting unit. Ignoring.
Mär 23 08:03:52 my-nfs-server systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mär 23 08:03:52my-nfs-server systemd[1]: nfs-server.service: Found left-over process 1793 (exportfs) in control group while starting unit. Ignoring.
Mär 23 08:03:52 my-nfs-server systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mär 23 08:03:52 my-nfs-server systemd[1]: Starting NFS server and services…
– Subject: A start job for unit nfs-server.service has begun execution
– Defined-By: systemd


– A start job for unit nfs-server.service has begun execution.

– The job identifier is 3947.

Output of systemctl status nfs-server

● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: activating (start-pre) since Mon 2020-03-23 08:03:52 CET; 16min ago
Cntrl PID: 1575 (exportfs)
Tasks: 3 (limit: 2094)
Memory: 1000.0K
CPU: 18ms
CGroup: /system.slice/nfs-server.service
├─ 928 /usr/sbin/rpc.nfsd
├─1575 /usr/sbin/exportfs -r
└─1793 /usr/sbin/exportfs -au

Mär 23 08:03:52 my-nfs-server systemd[1]: Starting NFS server and services…

I found that the start-pre command is exportfs -r . Thist recreates the file /var/lib/nfs/etab. It reads the content of the /etc/exports file and the files under /etc/exports.d/ . If I start exportfs -r manually it does nothing and the etab file is empty. I deleted the etab file, disabled the nfs-server and reboot the system. After this I ran this command exportfs -v -r. The etab file was created with the correct content.
I realized that the nfslcd.service failed to start. I found a thread https://bbs.archlinux.org/viewtopic.php?id=247282 which give me the solution for this error . The last reply in this thread explained to stop the nfslcd.service before and delete the files /var/lib/nfs/nfsdcltrack/main.sqlite AND /var/lib/nfs/nfsdcld/main.sqlite. Then I rebooted my server and start the nfs-server.service with systemctl start nfs-server. Now it run!!!

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.