Package: nfs-common
Followup-For: Bug #740491
I've had this happen on two machines I've upgrade so far.
It turns out that you get an error (sorry, didn't copy down the exact
message) when you try to run:
rpcinfo -d status 1
to un-register the service.
On a third machine, I ran that *beofor
I had a look at this issue, and the underlying problem seem to be that
rpcbind do not notice that rpc.statd was stopped, and believe the port
it request is occupied by another already running process when it try to
register its port when it start again. The 'status' RPC service stay in
the list e
Hello,
I have seen this behaviour too after upgrading my testing installation
yesterday. In my case I'm not using systemd, so the output is somewhat
different (the dist-upgrade doesn't notice anything is wrong so doesn't fail)
but the result is the same: statd won't start so nfs-common doesn't
Package: nfs-common
Version: 1:1.2.8-6
Severity: serious
On upgrading today, I got:
Setting up nfs-common (1:1.2.8-6) ...
Installing new version of config file /etc/init.d/nfs-common ...
insserv: warning: current start runlevel(s) (2 3 4 5 S) of script `nfs-common'
overrides LSB defaults (S).
Jo
4 matches
Mail list logo
