Re: nfsd closes port 2049

[Andrea Righi <righiandr@users.sourceforge.net>]

Talpey, Thomas wrote:
> At 08:42 AM 10/18/2007, Andrea Righi wrote:
>> The NFS server is working fine for the 2nd day using the fix (with kernel
>> 2.6.16.53-0.8-smp), but I'm not yet using the no_subtree_check option. I tried
>> to stress the filesystem with multiple accesses from all the clients (256),
>> alterning with periods of inactivity. This was a good "pattern" to 
>> reproduce the
>> problem and since it didn't happen anymore I'm considering the issue resolved.
> 
> Great! Do you have any "nfsd_acceptable" failures in the server's syslog?
> If none, then the second issue didn't occur either, a good thing in itself. :-)
> 
> Tom.
> 

I rebooted the NFS server with the new kernel on Oct 17 10:45:24, and:

node0101:~ # (bzcat /var/log/messages-2007101[78].bz2; cat /var/log/messages) | grep nfsd_acceptable
Oct 16 23:04:41 node0101 kernel: nfsd_acceptable failed at ffff810155e88150
Oct 17 07:52:38 node0101 kernel: nfsd_acceptable failed at ffff81015da98970
Oct 17 10:22:33 node0101 kernel: nfsd_acceptable failed at ffff8100d8cffa40

So, any nfsd_acceptable failure in the logs.

-Andrea

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs