[SOLVED] rpc.statd does not kick in

kaz2100 · 02-24-2019, 08:48 PM

Hya,

System Debian amd64, all up-to-date buster. Several Penguins are networked and one of them is a nfs file server.

Problem On the server Penguin, rpc.statd does not kick in on boot, and things get upside down.

Gorilla patch solution After boot

Code:

start-statd

troubleshooting When checking several logs on nfs server and clients, there not much informative ones. Both server and clients

Code:

 penelve systemd[1]: /lib/systemd/system/rpc-statd.service:13: PIDFile= references path below legacy directory /var/run/, updating /var/run/rpc.statd.pid -> /run/rpc.statd.pid; please update the unit file accordingly.

This thread is not much help. There are several old bugs in Debian (562757, 484861), which look irrelevant.

Penguins can survive with a patch above, but it may not be a good idea.

Does anybody know what happened and have a good idea?

cheers

kaz2100 · 02-27-2019, 10:52 PM

Self reply:

I found

Code:

* 27-systemd-enable-with-systemctl-statd.patch: let the admin
    enable/disable statd via systemd tools. (LP: #1428486)
  * debian/rules: don't start statd by default (or it will trigger upstart
    and systemd statd unit startup).

in the changelog of nfs-utils.
Then,

Code:

systemctl enable rpc-statd.service

does the job.

I was checking only nfs-common package!!