Re: NFS Server statd: server rpc.statd not responding, timed out
Hallo,
ein reboot des Servers hat geholfen.
Am Fri, 9 Dec 2011 13:32:11 +0100
schrieb Chris <chris786@freenet.de>:
> Hallo,
> ich habe einen NFS-Server an dem einige Debian Clients dranhängen.
> Die letzten beiden Tage hatte ich folgende Meldung im Log:
> [1710902.440163] statd: server rpc.statd not responding, timed out
> [1710902.440189] lockd: cannot monitor metall94
> [1710937.440085] statd: server rpc.statd not responding, timed out
> [1710937.440111] lockd: cannot monitor metall94
> [1710972.440203] statd: server rpc.statd not responding, timed out
> [1710972.440228] lockd: cannot monitor metall94
> [1711007.440093] statd: server rpc.statd not responding, timed out
> [1711007.440118] lockd: cannot monitor metall94
> [1711042.440169] statd: server rpc.statd not responding, timed out
> [1711042.440194] lockd: cannot monitor metall94
> [1711077.440087] statd: server rpc.statd not responding, timed out
> [1711077.440111] lockd: cannot monitor metall94
> [1711112.440176] statd: server rpc.statd not responding, timed out
> [1711112.440205] lockd: cannot monitor metall94
> [1711147.440162] statd: server rpc.statd not responding, timed out
> [1711357.440193] lockd: cannot monitor metall94
> [1711392.440085] statd: server rpc.statd not responding, timed out
> [1711392.440110] lockd: cannot monitor metall45
> [1711427.440163] statd: server rpc.statd not responding, timed out
> [1711427.440188] lockd: cannot monitor metall32
> [1711462.440077] statd: server rpc.statd not responding, timed out
> [1711462.440102] lockd: cannot monitor metall45
> [1711497.440116] statd: server rpc.statd not responding, timed out
> [1711497.440141] lockd: cannot monitor metall32
> [1711532.440077] statd: server rpc.statd not responding, timed out
> [1711532.440102] lockd: cannot monitor metall31
> [1711567.440165] statd: server rpc.statd not responding, timed out
> [1711567.440200] lockd: cannot monitor metall32
> [1711602.440165] statd: server rpc.statd not responding, timed out
> [1711602.440190] lockd: cannot monitor metall31
> [1711637.440082] statd: server rpc.statd not responding, timed out
> [1711637.440107] lockd: cannot monitor metall94
> [1711672.440247] statd: server rpc.statd not responding, timed out
> [1711672.440274] lockd: cannot monitor metall32
> [1711707.440081] statd: server rpc.statd not responding, timed out
> [1711707.440106] lockd: cannot monitor metall31
> [1711742.440165] statd: server rpc.statd not responding, timed out
> [1711742.440191] lockd: cannot monitor metall94
> [1711777.440083] statd: server rpc.statd not responding, timed out
> [1711777.440108] lockd: cannot monitor metall32
> [1711812.440162] statd: server rpc.statd not responding, timed out
> [1711812.440198] lockd: cannot monitor metall31
> [1711847.440085] statd: server rpc.statd not responding, timed out
> [1711847.440111] lockd: cannot monitor metall45
> [1711882.440174] statd: server rpc.statd not responding, timed out
> [1711882.440199] lockd: cannot monitor metall32
> [1711917.440081] statd: server rpc.statd not responding, timed out
> [1711917.440106] lockd: cannot monitor metall31
> [1711952.440167] statd: server rpc.statd not responding, timed out
> [1711952.440192] lockd: cannot monitor metall32
> [1711987.440083] statd: server rpc.statd not responding, timed out
> [1711987.440178] lockd: cannot monitor metall31
> [1712022.440159] statd: server rpc.statd not responding, timed out
> [1712022.440184] lockd: cannot monitor metall94
> [1712057.440078] statd: server rpc.statd not responding, timed out
> [1712057.440103] lockd: cannot monitor metall32
> [1712092.440170] statd: server rpc.statd not responding, timed out
> [1712092.440195] lockd: cannot monitor metall31
> [1712127.440082] statd: server rpc.statd not responding, timed out
> [1712127.440107] lockd: cannot monitor metall94
> Der NFS-Server ist dann nicht mehr ansprechbar - tot.
> Nach einem
> /etc/init.d/nfs-common restart
> /etc/init.d/nfs-kernel-server restart
> /etc/init.d/portmap restart
> geht er wieder. Das Problem tritt immer morgens auf.
>
> Das Log sagt zum Neustart folgendes:
> [1712127.442192] nfsd: last server has exited, flushing export cache
> [1712127.445895] svc: failed to register lockdv1 RPC service (errno
> 97). [1712127.446990] NFSD: Using /var/lib/nfs/v4recovery as the
> NFSv4 state recovery directory
>
> Auf dem ersten Client ist folgendes im Log zu finden.
> [ 737.924068] lockd: server 192.168.45.6 not responding, still trying
> [ 737.924071] lockd: server 192.168.45.6 not responding, still trying
> [ 737.924073] lockd: server 192.168.45.6 not responding, still trying
> [ 1104.977154] lockd: server 192.168.45.6 OK
> [ 1164.976035] lockd: server 192.168.45.6 not responding, still trying
> [ 1174.978224] lockd: server 192.168.45.6 OK
> [ 1234.976047] lockd: server 192.168.45.6 not responding, still trying
> [ 1279.979766] lockd: server 192.168.45.6 OK
> [ 1317.976029] xs_tcp_setup_socket: connect returned unhandled error
> -107
> [ 1323.980192] lockd: RPC call returned error 88
> [ 1323.980213] lockd: RPC call returned error 88
>
> Wir setzten NFS3 ein.
> /etc/exports auf dem Server
> XXXXXXXXXXX(rw,root_squash,async,no_subtree_check)
>
> Die Clients werden mit nfs default in der fstab eingebunden.
>
>
> Geändert haben wir die letzten Wochen nix außer das wir fast alle
> Clients von Lenny to Squeeze(KDE4) geupdatet haben.
>
>
> Hat jemand eine Idee? Big Brother Google hat bisher auch nix ergeben.
>
> MfG
> Chris
>
>
--
Christopher Wieser
Meßkircher Straße 5
68239 Mannheim
info@chwieser.de
Reply to: