SOLVED Clients can no longer connect to NFS share

[Roger]

Hi All,

Please forgive me if i leave any thing out...

I Have installed freenas 8.3.1 and set up nfs shares on a RAIDZ2 volume.
Volume = store
Datasets (All datasets are at root level of store) = music, pictures
So mount paths on my local Ubuntu pc are 'sudo mount -t nfs 192.168.1.20:/mnt/store/pictures /mnt/pic'
It was working well up until i upgraded using the gui method to the latest download 9.1.0.
The upgrade seemed to go well, the system restarted all OK (with the old config) but I can no longer mount any NFS share to my local pc (client), the connection times out.
I can ping to/from the freenas server
There are 2 NICs (different models) set up in an aggregate (round robin) at the single IP
Manually tried to restart NFS (shell) and it seems to be successful but NFSv4 seems to be disabled.
Checked the /etc/exports file all required shares are listed.
Is there a firewall blocking access, if so where do I find the config?
I am at a bit of a loss to fix this (yes-tried rebooting/shutdown and restart).

If you require any more info happy to provide.

 

[cyberjock]

I'd try disabling your lagg. There's been a few people that have had problems with the config from 8.3.1 to 9.1. Maybe get rid of it, test your logins, then try to set it up again in 9.1 with the same settings?

 

[Roger]

Thanks for the idea but nope, no good. The connection still times out.
Below is a snippett from the console message.
Each nic is now DHCP and I cannot connect to NFS on either address (Rebooted several times)
The console gives me an error that it cant bind the old IP to the web interface (changed IP).
I have explicitly allowed my IP (192.168.1.140 to a nfs share (currently the whole network is under Authorised networks)
I do note below says bad exports list line????

Note: nfsd is running

Code:

Aug  9 19:05:06 freenas last message repeated 2 times
Aug  9 19:06:36 freenas last message repeated 3 times
Aug  9 19:08:09 freenas notifier: Stopping lockd.
Aug  9 19:08:09 freenas notifier: Waiting for PIDS: 1924.
Aug  9 19:08:09 freenas notifier: Stopping statd.
Aug  9 19:08:09 freenas notifier: Waiting for PIDS: 1913.
Aug  9 19:08:09 freenas notifier: Stopping mountd.
Aug  9 19:08:09 freenas notifier: Waiting for PIDS: 1887.
Aug  9 19:08:09 freenas notifier: Stopping nfsd.
Aug  9 19:08:09 freenas notifier: Waiting for PIDS: 1901 1902.
Aug  9 19:08:10 freenas notifier: Starting mountd.
Aug  9 19:08:10 freenas notifier: mountd already running? (pid=5200).
Aug  9 19:08:10 freenas notifier: NFSv4 is disabled
Aug  9 19:08:10 freenas notifier: Starting nfsd.
Aug  9 19:08:10 freenas notifier: Starting statd.
Aug  9 19:08:10 freenas notifier: Starting lockd.
Aug  9 19:10:16 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v
Aug  9 19:10:16 freenas last message repeated 2 times
Aug  9 19:11:26 freenas last message repeated 3 times
Aug  9 19:11:38 freenas mountd[5200]: can't get address info for host 192.168.1.140/24
Aug  9 19:11:38 freenas mountd[5200]: bad host 192.168.1.140/24, skipping
Aug  9 19:11:38 freenas mountd[5200]: bad exports list line /mnt/store/pictures  -alldirs -mapall
Aug  9 19:11:38 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v
Aug  9 19:11:39 freenas last message repeated 2 times
Aug  9 19:11:47 freenas notifier: Will not 'reload' istgt because istgt_enable is NO.
Aug  9 19:11:48 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v
Aug  9 19:11:48 freenas last message repeated 2 times
Aug  9 19:12:54 freenas last message repeated 3 times

 

[paleoN]

The upgrade seemed to go well, the system restarted all OK (with the old config) but I can no longer mount any NFS share to my local pc (client), the connection times out.

This is often a DNS issue. You can try adding the client's DNS info to the FreeNAS's hosts file.

 

[Roger]

Thanks but I am a bit unsure about what you are suggesting here.
Do you want me to add 'my PCs' DNS entry into the FREENAS host's file?

And if so then I would need to add all clients into the Host file?
BTW - CIFS works perfectly

 

[Roger]

BUT DNS was the problem..... as soon as I added it it worked perfectly. I had looked at dns but it worked on the windows machine plus browsing, so I dismissed it.

How f.....g annoying, so now i have rebooted the router and hopefully eliminated this as a future issue.

Thanks for your help.

 

[Malo]

Hi, i've a very similar problem. After a fresh new install of Freenas 9.1.1 I could not connect to my nfs share (freenas 192.168.11.9). Here are the config and the log

/etc/export (oly for viewing purpose, not edited)

Code:

/mnt/Master/home/malo/scaricati  -alldirs -maproot=malo:malo -network 192.168.11.0/24

Logs:
Aug 30 14:34:26 freenas mountd[1613]: bad exports list line /mnt/Master/home/malo/scaricati
Aug 30 14:34:26 freenas mountd[1613]: bad exports list line /mnt/Master/home/malo/scaricati
Aug 30 14:34:28 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Aug 30 14:34:29 freenas last message repeated 3 times
Aug 30 14:36:32 freenas mountd[1613]: bad exports list line /mnt/Master/home/malo/scaricati
Aug 30 14:36:32 freenas mountd[1613]: bad exports list line /mnt/Master/home/malo/scaricati
Aug 30 14:36:34 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v

 

[Malo]

Hi.. It was simple. No nfs-utils package installed on my linux client
For me it's resolved!

 

[cyberjock]

Hi.. It was simple. No nfs-utils package installed on my linux client
For me it's resolved!

That would be a problem. :P

 

[sandrom]

Well, the same thing happened to me.
After some long hours troubleshooting the issue I confirmed what paleoN mentioned in #4.
It is really a DNS issue.

I SSHed into the FreeNAS and tried pinging a public URL (www.google.com).
The ping reply took way too long and this confirmed that something wasn't right.

The answer came when I dumped /etc/resolv.conf
Somehow the first line had an IP for a DNS server that was deprecated in our network.
I manually deleted that from /etc/resolv.conf and it immediately started working fine. My NFS mounts were working again.
Shortly after I found that this can also be edited through the UI on the:
Network>GlobalConfiguration>Nameserver #: