nfs client hanging
Guillaume Rousse
Guillaume.Rousse at inria.fr
Wed Jul 16 04:55:47 EDT 2008
J. Bruce Fields a écrit :
> In any case:
>
>> rpc.idmapd crashed, its last message occurs at 16:11:28, 12 minutes
>> before the trace. It seems to validate the hypothesis than the initial
>> failures comes from there, but doesn't get much information about why it
>> crashed, despite its verbosity level set to 3.
>
> Could get a backtrace, core dump, or something? What are the final
> messages before the crash?
The final message is a normal translation action, and nothing else:
Jul 15 16:11:28 localhost rpc.idmapd[3797]: Client 12: (user) name
"root at msr-inria.inria.fr" -> id "0"
I'm joining the log excerpt between this last message and the stack
trace, if it helps.
I don't have any core dump, given than they are automatically prohibited
by standard initscript. Apparently, setting DAEMON_COREFILE_LIMIT should
allow to get one. I'm rebooting the node with this value set.
--
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62
-------------- next part --------------
A non-text attachment was scrubbed...
Name: messages.bz2
Type: application/octet-stream
Size: 8889 bytes
Desc: not available
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20080716/3cf47279/attachment.obj
More information about the NFSv4
mailing list