Sean O'Connell wrote:
On Mon, 2005-04-25 at 20:02 -0400, Mark Weaver wrote:
Paul Heinlein wrote:
On 04/25/2005 03:22 AM, Mark Weaver wrote:
yeah... there's something strange going on with the server because the share can't be mounted from any other machine either.
Is there anything in /etc/hosts.{allow,deny} that would block traffic to the portmap on the server?
not a thing. I've checked everywhere I can think of. The really strange thing is that apart from the /etc/exports file there doesn't appear to be ANY config files for NFS. That is just plain weird.
No Firewall No SELinux No Hosts Deny entries
Its as if it just decided it didn't want to work any more - it had been working flawlessly for many months.
Silly question, but are portmapper, mountd, lockd running? Has the machine been rebooted recently (I have *never* forgotten to do a chckonfig foo on .. after doing a service foo start and having it run, only to be unpleasantly surprised on a reboot). Have you restarted the nfsd service?
Does rpcinfo -p server return sane results?
yep... all the NFS regulars are running. Here are the results from "rpcinfo -p"
rpcinfo -p 192.168.0.4 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 1024 status 100024 1 tcp 1024 status 100021 1 udp 1025 nlockmgr 100021 3 udp 1025 nlockmgr 100021 4 udp 1025 nlockmgr 100021 1 tcp 1029 nlockmgr 100021 3 tcp 1029 nlockmgr 100021 4 tcp 1029 nlockmgr 100011 1 udp 950 rquotad 100011 2 udp 950 rquotad 100011 1 tcp 953 rquotad 100011 2 tcp 953 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 989 mountd 100005 1 tcp 992 mountd 100005 2 udp 989 mountd 100005 2 tcp 992 mountd 100005 3 udp 989 mountd 100005 3 tcp 992 mountd