Hi, On Sat, Mar 16, 2024 at 08:13:44PM +0100, Harald Dunkel wrote: > Package: nfs-common > Version: 1:2.6.4-3 > > Restarting rpc-statd.service (e.g via needrestart at upgrade time) > runs into a timeout: > > Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: State > 'stop-sigterm' timed out. Killing. > Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Killing process > 2342 (rpc.statd) with signal SIGKILL. > Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Main process > exited, code=killed, status=9/KILL > Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Failed with > result 'timeout'. > Mar 16 20:06:58 lola.afaics.de systemd[1]: Stopped rpc-statd.service - NFS > status monitor for NFSv2/3 locking.. > Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpcbind.service - RPC > bind portmap service... > Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpcbind.service - RPC bind > portmap service. > Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpc-statd.service - NFS > status monitor for NFSv2/3 locking.... > Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Version 2.6.4 starting > Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Flags: TI-RPC > Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpc-statd.service - NFS > status monitor for NFSv2/3 locking.. > > Please reassign if necessary
I cannot reproduce this. If this was not a one-time off issue on your system, do you have a way to reproduce the behaviour to further investigate it? Regards, Salvatore
