Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
rpc.statd goes non-responsive, Ubuntu machine caused?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Networking & Security
View previous topic :: View next topic  
Author Message
mgnut57
n00b
n00b


Joined: 12 Jan 2008
Posts: 55

PostPosted: Fri Oct 29, 2010 12:32 am    Post subject: rpc.statd goes non-responsive, Ubuntu machine caused? Reply with quote

I have a really odd situation. I just added an Ubuntu 10.04 Desktop to my network. The home directory for the main user of this Ubuntu machine is auto-mounted from my Gentoo server.

It seems that immediately after the Ubuntu machine mounts the nfs export and then attempts to lock a file (I assume any of the files which contain user preferences/setup) the statd daemon stops responding. I haven't seen this happen with my Gentoo Desktop (which also auto-mounts home directories from the same Gentoo server), just the Ubuntu Desktop.

Here is an example of the relevant message on the server:
Oct 28 17:15:55 localhost klogd: statd: server rpc.statd not responding, timed out

Does anyone have any ideas what could cause this odd behavior and, more importantly, how I fix it?

Naturally, I ran revdep-rebuild as the first check for problems, but it reported no issues.
Back to top
View user's profile Send private message
Jaglover
Advocate
Advocate


Joined: 29 May 2005
Posts: 4666
Location: Saint Amant, Acadiana

PostPosted: Fri Oct 29, 2010 11:57 am    Post subject: Reply with quote

I had similar problem, a few Gentoo boxes mounted portage from FBSD server. Every now and then statd stopped responding. Finally I upgraded that FBSD box and problem went away.
Back to top
View user's profile Send private message
mgnut57
n00b
n00b


Joined: 12 Jan 2008
Posts: 55

PostPosted: Fri Oct 29, 2010 2:56 pm    Post subject: Reply with quote

Jaglover wrote:
I had similar problem, a few Gentoo boxes mounted portage from FBSD server. Every now and then statd stopped responding. Finally I upgraded that FBSD box and problem went away.


I am beginning to suspect that it is due to mis-configured and conflicting dns/hosts. The client used a server called "fileserver", which resolved to a 192.168.x.x address, but on the server, "fileserver" referred to 127.0.0.1 in the /etc/hosts file (which has precedence).
Back to top
View user's profile Send private message
mgnut57
n00b
n00b


Joined: 12 Jan 2008
Posts: 55

PostPosted: Sat Oct 30, 2010 9:35 pm    Post subject: Reply with quote

mgnut57 wrote:
Jaglover wrote:
I had similar problem, a few Gentoo boxes mounted portage from FBSD server. Every now and then statd stopped responding. Finally I upgraded that FBSD box and problem went away.


I am beginning to suspect that it is due to mis-configured and conflicting dns/hosts. The client used a server called "fileserver", which resolved to a 192.168.x.x address, but on the server, "fileserver" referred to 127.0.0.1 in the /etc/hosts file (which has precedence).


I fixed the DNS config and the problem remains, so my idea that it was related to the DNS/hosts setup is clearly false.
Back to top
View user's profile Send private message
mgnut57
n00b
n00b


Joined: 12 Jan 2008
Posts: 55

PostPosted: Thu Jan 17, 2013 6:12 am    Post subject: Re: rpc.statd goes non-responsive, Ubuntu machine caused? Reply with quote

mgnut57 wrote:
I have a really odd situation. I just added an Ubuntu 10.04 Desktop to my network. The home directory for the main user of this Ubuntu machine is auto-mounted from my Gentoo server.

It seems that immediately after the Ubuntu machine mounts the nfs export and then attempts to lock a file (I assume any of the files which contain user preferences/setup) the statd daemon stops responding. I haven't seen this happen with my Gentoo Desktop (which also auto-mounts home directories from the same Gentoo server), just the Ubuntu Desktop.

Here is an example of the relevant message on the server:
Oct 28 17:15:55 localhost klogd: statd: server rpc.statd not responding, timed out

Does anyone have any ideas what could cause this odd behavior and, more importantly, how I fix it?

Naturally, I ran revdep-rebuild as the first check for problems, but it reported no issues.


A long-overdue followup.

I eventually found a file permission issue in my logfiles. Can't remember what the file was, but once I changed the permissions (or ownership), the problem went away. The reason that the Ubuntu box caused this while the Gentoo box did not was that the Ubuntu box was accessing the NFS files using the /net automount, which uses "showmount" against the nfs server. It was the showmount query (along with the permission issue) against the NFS server that caused rpc.statd to go unresponsive.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Networking & Security All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum