Hi list,
this is probably an Ubuntu bug, however it put two different servers in
the dumps, running different kernels so I send this in case it may help
someone.
Here is the sort of messages clogging the NFS servers logs:
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipntheo12
statd: server rpc.statd not responding, timed out
lockd: cannot unmonitor ipnnester13
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipngrid01.in2p3.fr
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipngrid01.in2p3.fr
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipngrid01.in2p3.fr
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipnweb2
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipnweb2
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipnweb2
lockd: server ipnweb2 not responding, timed out
lockd: server ipnweb2 not responding, timed out
There are about 80 NFS clients (home directories) on these. They worked
perfectly for years until 2 clients were upgraded to 13.04.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@xxxxxxxxxxxxxx>
| +33 1 78 94 84 02
------------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
