NLM: Failed to contact remote rpcbind

Status
Not open for further replies.

Dorin

Dabbler
Joined
Mar 31, 2014
Messages
12
Machine: Dual Core E5300, 8GB RAM, 2X2TB SATA hard disks, FreeNAS 9.2.1.8

I get tons of errors like this:
Oct 31 00:37:16 freenas kernel: NLM: failed to contact remote rpcbind, stat = 7, addr = 192.168.0.50, port = 28416
Oct 31 00:37:17 freenas last message repeated 9 times
Oct 31 00:38:49 freenas last message repeated 10 times

This IP is on my lab is the VMWare VCSA, and this error appears only to this machine. The mount is NFS and it's mounted on other machines, and I don't get any error regarding their IP's.

I checked rpcinfo -p localhost - everything looks perfectly ok (output here: http://pastebin.com/PvNarCCx )

Mounting the NFS volume on other machines (after this error) works, but the speed is really slow - 5MB on average, compared to 50+MB per second when this issue doesn't occur.

I had this error since 9.2.1.3 and then I updated to 9.2.1.8. The error didn't appear for few ours, but now it does...

No errors appear in /var/log/messages (other then this error):

Oct 30 12:04:57 freenas notifier: collectd not running?
Oct 30 12:04:57 freenas notifier: Starting collectd.
Oct 30 12:04:57 freenas notifier: kern.corefile: %N.core -> /mnt/main/.system/cores/%N.core
Oct 31 00:37:16 freenas kernel: NLM: failed to contact remote rpcbind, stat = 7, addr = 192.168.0.50, port = 28416
Oct 31 00:37:17 freenas last message repeated 9 times
Oct 31 00:38:49 freenas last message repeated 10 times

Any suggestions?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Can you post the debug file for your server?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
I just glanced through your debug and there's no smoking gun. I'll see if I can get someone to look at it tomorrow that might be able to help. If you don't get a response by this time tomorrow ask in the thread and I'll see the thread update.
 
Status
Not open for further replies.
Top