Ask Your Question
0

Not able to connect to NFS server running on FC16

asked 2011-12-08 12:09:32 -0500

Usman Ansari gravatar image

updated 2011-12-08 19:04:02 -0500

Upgraded from FC 14 to FC 16 via yum. Now nfs clients are unable to connect to NFS server running on FC 16. I have turned on iptables, SElinux is already disabled, ' nfs is running (see below). When I try connecting from Scientific Linux 6, I get timeout after it tries for two minutes and if I try from FC 8, I get mount: mount to NFS server 'SERVER' failed: RPC Error: Program not registered.

exportfs correctly displays exported directories and exported to machines.

Any help will be greatly appreciated.

[root@bigguy ~]# systemctl status nfs-server.service

nfs-server.service - NFS Server

  Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled)

  Active: active (running) since Wed, 07 Dec 2011 18:39:57 -0800; 7s ago

 Process: 4235 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
 Process: 4234 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS)

 Process: 4246 ExecStartPost=/usr/lib/nfs-utils/scripts/nfs-server.postconfig (code=exited, status=0/SUCCESS)

 Process: 4244 ExecStartPost=/usr/sbin/rpc.mountd $RPCMOUNTDOPTS (code=exited, status=0/SUCCESS)

 Process: 4243 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS ${RPCNFSDCOUNT} (code=exited, status=0/SUCCESS)
 Process: 4242 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
 Process: 4240 ExecStartPre=/usr/sbin/rpc.rquotad $RPCRQUOTADOPTS (code=exited, status=0/SUCCESS)

 Process: 4238 ExecStartPre=/usr/lib/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS)

Main PID: 4241 (rpc.rquotad)

  CGroup: name=systemd:/system/nfs-server.service
      ├ 4241 /usr/sbin/rpc.rquotad

      └ 4245 /usr/sbin/rpc.mountd
edit retag flag offensive close merge delete

3 Answers

Sort by » oldest newest most voted
1

answered 2011-12-10 12:01:42 -0500

ZenDark gravatar image

Try this:

After the upgrade, the nfs config file is no longer valid. I had to replace it manually by the nfs.rpmnew. Strictly speaking was it the RPCNFSDCOUNT variable that obviously has no longer a default value but is needed to be set to bring up the server.

It could be a problem with the version shipped in F16 not being compatible with the config needed in F14/F15

Original post

edit flag offensive delete link more
0

answered 2012-03-21 17:32:58 -0500

Davinken gravatar image

updated 2012-03-21 17:37:21 -0500

I am running into this and found that the kernel modules needed are not installed by default in FC16. Typically, I get a "Function not implemented" error despite having a correct /etc/exports file and the nfs-utils package.

But the cause seems to be:

# lsmod | grep nfs

returns empty when it should be something like:

# lsmod | grep nfs
nfs                   294541  1 
fscache                43953  1 nfs
nfsd                  268260  13 
lockd                  66512  2 nfs,nfsd
nfs_acl                 2365  2 nfs,nfsd
auth_rpcgss            38179  2 nfs,nfsd
exportfs                3512  1 nfsd
sunrpc                198717  21 nfs,nfsd,lockd,nfs_acl,auth_rpcgss

The solution is to install the nfs and nfsd modules with

# modprobe nfs
# modprobe nfsd

After this, (re)start the nfsd daemon with

# systemctl (re)start nfsd

You can check that its now alive with

# pgrep -l nfs
12103 nfsiod
12198 nfsd4
12199 nfsd4_callbacks
12200 nfsd
12201 nfsd
12202 nfsd
12203 nfsd
12204 nfsd
12205 nfsd
12206 nfsd
12207 nfsd

Now NFS works for me. I'm on FC16 on a 64-bit machine.

edit flag offensive delete link more
-1

answered 2014-03-04 00:56:40 -0500

sunil gravatar image

When I am issuing -

systemctl (re)start nfsd

getting error that nfs.service not found........ Help me.

edit flag offensive delete link more

Comments

Please open a new question.

randomuser gravatar imagerandomuser ( 2014-03-04 00:59:30 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2011-12-08 12:09:32 -0500

Seen: 5,237 times

Last updated: Mar 04 '14