LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   NFS not working in RHEL6.2 (https://www.linuxquestions.org/questions/linux-newbie-8/nfs-not-working-in-rhel6-2-a-4175489575/)

boby.kumar 12-30-2013 08:07 AM

NFS not working in RHEL6.2
 
Hi,

NFS server is not working in client side and getting the following error while mounting the remote..

[root@localhost ~]# mount -t nfs 192.168.50.5:/home/samb/rncit /var/log/logs
mount: mount to NFS server '192.168.50.5' failed: RPC Error: Program not registered.

NFS Server details
[root@localhost ~]# uname -a
Linux localhost 2.6.32-220.el6.i686 #1 SMP Wed Nov 9 08:02:18 EST 2011 i686 i686 i386 GNU/Linux

[root@localhost ~]# cat /etc/exports
/home/ 192.168.50.0/24(rw,sync,no_root_squash)

[root@localhost ~]# rpcinfo -p
No remote programs registered
.

[root@localhost ~]# showmount -e
Export list for localhost:
/home 192.168.50.0/24

[root@localhost ~]# service nfs restart
Shutting down NFS mountd: [ OK ]
Shutting down NFS daemon: [ OK ]
Shutting down NFS quotas: [ OK ]
Shutting down NFS services: [ OK ]
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]

[root@localhost ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:sunrpc
ACCEPT udp -- anywhere anywhere state NEW udp dpt:sunrpc
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:pftp
ACCEPT udp -- anywhere anywhere state NEW udp dpt:pftp
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:892
ACCEPT udp -- anywhere anywhere state NEW udp dpt:892
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:nfs
ACCEPT udp -- anywhere anywhere state NEW udp dpt:nfs
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:32803
ACCEPT udp -- anywhere anywhere state NEW udp dpt:32803
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:filenet-rpc
ACCEPT udp -- anywhere anywhere state NEW udp dpt:filenet-rpc

[root@localhost ~]# /etc/init.d/rpcbind status
rpcbind (pid 6172) is running...

[root@localhost ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

[root@localhost ~]# /etc/init.d/iptables status
iptables: Firewall is not running.


all the services is running and restarted several times.

can any one explain what is wrong with this?

Thanks in Advance

michaelk 12-30-2013 08:47 AM

It appears that rpcbind is not running which starts as a separate service from nfs.

boby.kumar 12-30-2013 09:02 AM

Here it is

Quote:

[root@localhost ~]# /etc/init.d/rpcbind status
rpcbind (pid 6172) is running...

jpollard 12-30-2013 09:13 AM

Make sure the firewall on the server knows to permit NFS and rpcbind.

You might also need to check the SELinux boolean flags to permit NFS exports (you can check with "getsebool -a | grep -i nfs", then select the ones you want/need.

boby.kumar 12-30-2013 10:31 PM

Here the output
[root@localhost ~]# getsebool -a | grep -i nfs
allow_ftpd_use_nfs --> off
allow_nfsd_anon_write --> off
cobbler_use_nfs --> off
git_system_use_nfs --> off
httpd_use_nfs --> off
nfs_export_all_ro --> on
nfs_export_all_rw --> on

qemu_use_nfs --> on
samba_share_nfs --> off
use_nfs_home_dirs --> on
virt_use_nfs --> off
xen_use_nfs --> off

It seems nothing is blocked. Is there another way to proceed for the same?

btmiller 01-01-2014 01:06 AM

Looks at "iptables -L" and see if there's a firewall rule preventing NFS traffic.

boby.kumar 01-01-2014 01:37 AM

Finally I got the solution. it was missing with RPCBIND.

thanks for help.

"If you begin with the notion that something is impossible, then it obviously will be for you." - Unknown

michaelk 01-01-2014 06:05 AM

Well done.

You can mark the thread as solved via the thread tools menu at the top of the thread.


All times are GMT -5. The time now is 03:39 AM.