I installed two F16 machines, and NFS was working just fine between those and my other systems. I took one of those two F16 machines and did a fresh install to F17. Now the F17 machine can't even automount (autofs) itself. Nor are other machines able to mount it. To troubleshoot this I had a look with showmount.
Code:
[kevinc@f16good-kevinc #26] sudo showmount -e
[sudo] password for kevinc:
Export list for f16good.somewhere.com:
/projects 192.168.1.0/24
/nobackup 192.168.1.0/24
/music 192.168.1.0/24
/home 192.168.1.0/24
[kevinc@f17bad ~]$ sudo showmount -e
[sudo] password for kevinc:
clnt_create: RPC: Port mapper failure - Authentication error
The above points to an RPC problem on the F17 machine. So, I ran rpcinfo on both machines.
Code:
[kevinc@f16good-kevinc #27] rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100011 1 udp 875 rquotad
100011 2 udp 875 rquotad
100011 1 tcp 875 rquotad
100011 2 tcp 875 rquotad
100024 1 udp 4001 status
100024 1 tcp 4001 status
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 2 tcp 2049 nfs_acl
100227 3 tcp 2049 nfs_acl
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100227 2 udp 2049 nfs_acl
100227 3 udp 2049 nfs_acl
100021 1 udp 4002 nlockmgr
100021 3 udp 4002 nlockmgr
100021 4 udp 4002 nlockmgr
100021 1 tcp 4002 nlockmgr
100021 3 tcp 4002 nlockmgr
100021 4 tcp 4002 nlockmgr
100005 1 udp 20048 mountd
100005 1 tcp 20048 mountd
100005 2 udp 20048 mountd
100005 2 tcp 20048 mountd
100005 3 udp 20048 mountd
100005 3 tcp 20048 mountd
[kevinc@f17bad ~]$ rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 49054 status
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 2 tcp 2049 nfs_acl
100227 3 tcp 2049 nfs_acl
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100227 2 udp 2049 nfs_acl
100227 3 udp 2049 nfs_acl
100024 1 tcp 37154 status
100021 1 udp 58856 nlockmgr
100021 3 udp 58856 nlockmgr
100021 4 udp 58856 nlockmgr
100021 1 tcp 48762 nlockmgr
100021 3 tcp 48762 nlockmgr
100021 4 tcp 48762 nlockmgr
100005 1 udp 20048 mountd
100005 1 tcp 20048 mountd
100005 2 udp 20048 mountd
100005 2 tcp 20048 mountd
100005 3 udp 20048 mountd
100005 3 tcp 20048 mountd
The above shows that rquotad fails to run on the F17 machine. Looking through NFS documentation it looks like rquotad is something that's supposed to be started by the other NFS processes, and not via user interaction.
For completeness, the /etc/exports files of the two machines are as follows:
Code:
::::::::::::::
f16good/exports
::::::::::::::
/home 192.168.1.0/24(rw,no_root_squash,sync)
/music 192.168.1.0/24(rw,no_root_squash,sync)
/nobackup 192.168.1.0/24(rw,no_root_squash,sync)
/projects 192.168.1.0/24(rw,no_root_squash,sync)
::::::::::::::
f17bad/exports
::::::::::::::
/ 192.168.1.0/24(rw,no_root_squash,sync)
/home 192.168.1.0/24(rw,no_root_squash,sync)
/extra 192.168.1.0/24(rw,no_root_squash,sync)
The /etc/hosts.allow and /etc/hosts.deny files are identical between the two machines. The /etc/hosts files are identical except that each of them has their own IP address as the first entry in their respective copy of that file.
Turning off the firewall on the F17 machine has no effect. That's what I'd anticipate, given that the two firewalls are set up identically.
Any ideas folks? I'm not sure how to continue troubleshooting this problem.
Thanks....
---------- Post added at 05:06 PM ---------- Previous post was at 09:00 AM ----------
Two new pieces of information. I should have said that this is with x86_64. Both the working systems and the now not-working system are x86_64. The other machines, which are also fine, but are Mandriva, are i686.
Also, I now notice that when I try to automount I get "SELinux has detected a problem." The details are:
Code:
The source process: /usr/bin/automount
Attempted this access: read
On this file: /etc/hosts
Well, of course it did. Maybe this is a slightly malconfigured SELinux out of the F17 box? I altered /etc/selinux/config changing SELINUX=enforcing to SELINUX=disabled. I'll reboot in a minute, and then maybe I'll know whether that's the cause.
Alright, everyone hold their breath while I try it.
---------- Post added at 05:16 PM ---------- Previous post was at 05:06 PM ----------
For everyone holding their breath, I got back here as quickly as I could. Disabling SELinux enables NFS on F17 x86_64. That seems like a bug to me. I'll report it.
Cheerio....
Linear Mode
