[SOLVED] Fedora 17 no NFS Functionality

[jlpierce]

Hello,

I have moved to Fedora 17 on 3 internal computers, all 3 were fresh installations. However, now I have no NFS server functionality.

I have enabled the nfs-server.service with systemctl and this is what happens when I start it with:

systemctl start nfs-server.service

and check the status with:

systemctl status nfs-server.service

nfs-server.service - NFS Server
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
Active: active (exited) since Fri, 06 Jul 2012 21:40:26 -0400; 1h 34min ago
Process: 3936 ExecStartPost=/usr/lib/nfs-utils/scripts/nfs-server.postconfig (code=exited, status=0/SUCCESS)
Process: 3923 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS ${RPCNFSDCOUNT} (code=exited, status=0/SUCCESS)
Process: 3920 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
Process: 3917 ExecStartPre=/usr/lib/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/nfs-server.service

At this point there are no mounts and no other computer mount a share.

This is the last 2 lines of the output from dmesg:

[ 6088.501748] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 6088.501787] NFSD: starting 90-second grace period

Any assistance with this issue would be greatly appreciated.

Thanks

[DBelton]

Originally Posted by jlpierce

Hello,

I have moved to Fedora 17 on 3 internal computers, all 3 were fresh installations. However, now I have no NFS server functionality.

I have enabled the nfs-server.service with systemctl and this is what happens when I start it with:

systemctl start nfs-server.service

and check the status with:

systemctl status nfs-server.service

nfs-server.service - NFS Server
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
Active: active (exited) since Fri, 06 Jul 2012 21:40:26 -0400; 1h 34min ago
Process: 3936 ExecStartPost=/usr/lib/nfs-utils/scripts/nfs-server.postconfig (code=exited, status=0/SUCCESS)
Process: 3923 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS ${RPCNFSDCOUNT} (code=exited, status=0/SUCCESS)
Process: 3920 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
Process: 3917 ExecStartPre=/usr/lib/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/nfs-server.service

This looks normal. Nothing wrong there. The nfs-server is running.

At this point there are no mounts and no other computer mount a share.

This is the last 2 lines of the output from dmesg:

[ 6088.501748] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 6088.501787] NFSD: starting 90-second grace period

Any assistance with this issue would be greatly appreciated.

Thanks

That also looks normal.

Did you set up your /etc/exports? What does it look like?

Did you allow access through the firewall?

How are you trying to mount your nfs shares on the client?

[jlpierce]

This is the /etc/exports file:

/music 192.168.1.*/24(rw,insecure,sync,no_root_squash)


I tried as root the following mount command:

mount -t nfs 192.168.1.30:/music /media/music

the /media/music directory exists as well.

Also, the firewall is turned off as well as selinux.

However, I do not believe that the server is running, notice the exited part in the following line:

Active: active (exited) since Fri, 06 Jul 2012 21:40:26 -0400; 1h 34min ago


I know there was some discussion around a missing var-run.mount dependency, but that issue has not surfaced here.

Thanks

---------- Post added at 11:04 PM ---------- Previous post was at 10:53 PM ----------

Follow up:

As a follow up to the part about the server not running, if I do a status check on the mysqld server I get this:

Active: active (running) since Fri, 06 Jul 2012 19:59:21 -0400; 4h 4min ago

There is also a PID associated with the server. I am not sure if that helps.

Again, thanks for the response.

---------- Post added at 11:14 PM ---------- Previous post was at 11:04 PM ----------

This might also be relevant, it is from the tail of /var/log/messages

Jul 7 00:09:56 linbooka systemd[1]: nfs-mountd.service: main process exited, code=exited, status=1
Jul 7 00:09:56 linbooka systemd[1]: Unit nfs-mountd.service entered failed state.
Jul 7 00:09:56 linbooka kernel: [15039.323440] nfsd: last server has exited, flushing export cache
Jul 7 00:10:02 linbooka kernel: [15045.661047] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory

Hope this might help.

[knesenko]

Check this liune in /etc/exports : /music 192.168.1.*/24(rw,insecure,sync,no_root_squash) - looks like a syntax issue here.
AFAIK wildcards are not allowed on ip addresses. Please try this:
/music 192.168.1.0/24(rw,insecure,sync,no_root_squash)

[jlpierce]

I appreciate the feedback, but still no joy. I changed the exports to the suggested line and still this:

Active: active (exited) since Sat, 07 Jul 2012 05:40:07 -0400; 3s ago

This is really puzzling to me, I have never had this much issue getting NFS to work.

[DBelton]

It is normal for it to show exited.

Here is what mine shows and it's up and running:

[root@tower11 ~]# systemctl status nfs-server.service
nfs-server.service - NFS Server
	  Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
	  Active: active (exited) since Fri, 06 Jul 2012 10:44:57 -0500; 20h ago
	 Process: 745 ExecStartPost=/usr/lib/nfs-utils/scripts/nfs-server.postconfig (code=exited, status=0/SUCCESS)
	 Process: 726 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS ${RPCNFSDCOUNT} (code=exited, status=0/SUCCESS)
	 Process: 718 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
	 Process: 707 ExecStartPre=/usr/lib/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/nfs-server.service
[root@tower11 etc]# exportfs
/nfs4exports  	192.168.1.0/24
/nfs4exports/Drive_C
		192.168.1.0/24
/nfs4exports/Drive_D
		192.168.1.0/24
/nfs4exports/Drive_E
		192.168.1.0/24
/nfs4exports/Drive_F
		192.168.1.0/24
/nfs4exports/Drive_G
		192.168.1.0/24
/nfs4exports/Drive_H
		192.168.1.0/24
/nfs4exports/Drive_I
		192.168.1.0/24
[root@tower11 etc]#

Using the exportfs command, that shows you what is actually being shared by nfs.

[jlpierce]

Ok, I miss spoke and did not give the system enough time to mount the exported file system.

It now mounts correctly as expected. It turned out to the be the exports file and that wildcard * I had there. Thanks for that information, I could have sworn that I had a wildcard in my previous configurations.

Thanks again for that assistance.