Freenas NFS log review

[bako]

Sorry, BSD isn't quite my forte. Can anybody tell me how to review the live log for NFS?

I'm trying to mount an NFS share in GNU Linux with the line below in my fstab and it doesn't seem to be doing anything.

/etc/fstab:
10.0.0.240:/mnt/MAIN/Owncloud /var/www/storage.boydhanaleiako.me nfs rw,intr,hard 0 0


mounting:
[root@nx74205 www]# mount -vvv /var/www/storage.boydhanaleiako.me
mount.nfs: timeout set for Mon Jan 27 00:40:56 2020
mount.nfs: trying text-based options 'intr,hard,vers=4.1,addr=10.0.0.240,clientaddr=10.0.0.249'

 

[Fredda]

What have you configured on your server? (Services->NFS, Sharing->Unix (NFS) Shares)
What is the output of showmount -e 10.0.0.240 run on your Linux client.

 

[bako]

What have you configured on your server? (Services->NFS, Sharing->Unix (NFS) Shares)
What is the output of showmount -e 10.0.0.240 run on your Linux client.

[root@nx74205 www]# showmount -e 10.0.0.240
Export list for 10.0.0.240:
/mnt/MAIN/Owncloud (everyone)

 

[Fredda]

That is just half of the information I asked for, anyway. This looks OK so far.
Please show contents of /etc/exports on the server.
What happens if you mount directly mount -t nfs 10.0.0.240:/mnt/MAIN/Owncloud /mnt?
Any error message? If not, what is the output of mount?
Check for NFS related messages on the server in /var/log/messages.
And of course the information, which should included in all questions asked here, which FreeNAS version?

 

[bako]

That is just half of the information I asked for, anyway. This looks OK so far.
Please show contents of /etc/exports on the server.

[root@abyss /mnt/MAIN/HOME/binary]# cat /etc/exports
V4: / -sec=sys:krb5:krb5i:krb5p
/mnt/MAIN/Owncloud -alldirs

What happens if you mount directly mount -t nfs 10.0.0.240:/mnt/MAIN/Owncloud /mnt?
Any error message? If not, what is the output of mount?

Same thing.

[root@nx74205 www]# mount -v -t nfs 10.0.0.240:/mnt/MAIN/Owncloud /var/www/storage.boydhanaleiako.me
mount.nfs: timeout set for Mon Jan 27 09:22:23 2020
mount.nfs: trying text-based options 'vers=4.1,addr=10.0.0.240,clientaddr=10.0.0.249'

Check for NFS related messages on the server in /var/log/messages.

Same thing.

A bunch of nothing. The only thing that shows up is if I use the webui to stop and restart it in which generates the below.

[root@abyss /var/log]# grep -i -e nfs -e rpc messages
Jan 27 00:17:15 abyss.neverland.ddns.me nfsd: can't register svc name
Jan 27 00:18:51 abyss.neverland.ddns.me nfsd: can't register svc name
Jan 27 00:22:32 abyss.neverland.ddns.me nfsd: can't register svc name
Jan 27 09:15:29 abyss.neverland.ddns.me nfsd: can't register svc name

And of course the information, which should included in all questions asked here, which FreeNAS version?

FreeNAS-11.2-U7

 

[Fredda]

And still not answered, what I asked in my first post:

What have you configured on your server? (Services->NFS, Sharing->Unix (NFS) Shares)

And also:

What happens if you mount directly mount -t nfs 10.0.0.240:/mnt/MAIN/Owncloud /mnt?
Any error message? If not, what is the output of mount?

Your command looks like it worked, are you sure your share is not there?

Your exports file looks like you have some kerberos options set. Maybe that is your problem.

[root@abyss /var/log]# grep -i -e nfs -e rpc messages
Jan 27 00:17:15 abyss.neverland.ddns.me nfsd: can't register svc name

This is not a problem normally, but ths means kerberos is not working

https://redmine.ixsystems.com/issues/11351

 

[bako]

And still not answered, what I asked in my first post:

And also:

Your command looks like it worked, are you sure your share is not there?

Your exports file looks like you have some kerberos options set. Maybe that is your problem.

This is not a problem normally, but ths means kerberos is not working

https://redmine.ixsystems.com/issues/11351

Yes, I did configure the NFS shares. I assumed that would be answered when I clipped the showmount command on the client.

The mount command hangs and doesn't exit back to the shell. Hitting enter a bunch doesn't do anything.

As for Kerberos, I don't really think it's an issue. The client is setup to use kerberos, but the Freenas server isn't. I'm waiting for the Freenas update to use FreeIPA for authentication.

 

[Fredda]

Yes, I did configure the NFS shares. I assumed that would be answered when I clipped the showmount command on the client.

This was kind of clear. But you did now show how you configured it and how you configured your NFSD service.

The mount command hangs and doesn't exit back to the shell. Hitting enter a bunch doesn't do anything.

You did not mention that before.

As for Kerberos, I don't really think it's an issue. The client is setup to use kerberos, but the Freenas server isn't.

Sure? The first line of you exports file shows V4: / -sec=sys:krb5:krb5i:krb5p
So it would be interesting to see if the checkbox [ ] Require Kerberos for NFSv4 is set, among the other options for your nfsd service.
You should also make sure there is no firewall involved in the connection, on you linux client or on the network gear in between.

 

[bako]

This was kind of clear. But you did now show how you configured it and how you configured your NFSD service.

You did not mention that before.

Sure? The first line of you exports file shows V4: / -sec=sys:krb5:krb5i:krb5p
So it would be interesting to see if the checkbox [ ] Require Kerberos for NFSv4 is set, among the other options for you sshd service.
You should also make sure there is no firewall involved in the connection, on you linux client or on the network gear in between.

ugh... You're one of those... lol... Here's screenshots of the config. And below that are is the firewall info on the client. I added the nfs and nfs3 services; but I don't think those would do anything for a client. There's no firewall between them as it's a VM on the server.

[root@nx74205 www]# for srv in $(firewall-cmd --list-services); do firewall-cmd --info-service=$srv; done
dhcpv6-client
ports: 546/udp
protocols:
source-ports:
modules:
destination: ipv6:fe80::/64
http
ports: 80/tcp
protocols:
source-ports:
modules:
destination:
https
ports: 443/tcp
protocols:
source-ports:
modules:
destination:
jackett
ports: 9117/tcp
protocols:
source-ports:
modules:
destination:
mysql
ports: 3306/tcp
protocols:
source-ports:
modules:
destination:
nfs
ports: 2049/tcp
protocols:
source-ports:
modules:
destination:
nfs3
ports: 2049/tcp 2049/udp
protocols:
source-ports:
modules:
destination:
ssh
ports: 22/tcp
protocols:
source-ports:
modules:
destination:
subsonic
ports: 4040/tcp
protocols:
source-ports:
modules:
destination:

 

[Fredda]

ugh... You're one of those... lol...

???

Here's screenshots of the config.

These look good IMHO.

And below that are is the firewall info on the client. There's no firewall between them as it's a VM on the server.

I don't really know the semantics of the firewall-cmd tool. Just make sure all the relevant ports for NFS on the server can be reached.
Check the output of rpcinfo -p <server> on your client. Also, I don't quite get you remark on the VM? Which instance
is running in a VM? This would have also been something you should have mentioned in the beginning. This adds a new layer of
possible problems...

But I'm out of ideas. Sorry...

 

[Tony-1971]

Hello,

To exclude firewall problems you can try to use nmap from client.
An example from my setup:

Code:

[root@plex-server ~]# nmap freenas-emx -p 2049,111 -sU
Starting Nmap 7.80 ( https://nmap.org ) at 2020-01-30 09:35 CET
Nmap scan report for freenas-emx (192.168.50.3)
Host is up (0.00039s latency).
rDNS record for 192.168.50.3: freenas-emx.localdomain

PORT     STATE  SERVICE
111/udp  open   rpcbind
2049/udp closed nfs
MAC Address: AC:1F:6B:7C:DE:15 (Super Micro Computer)

Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds


[root@plex-server ~]# nmap freenas-emx -p 2049,111
Starting Nmap 7.80 ( https://nmap.org ) at 2020-01-30 09:35 CET
Nmap scan report for freenas-emx (192.168.50.3)
Host is up (0.00042s latency).
rDNS record for 192.168.50.3: freenas-emx.localdomain

PORT     STATE SERVICE
111/tcp  open  rpcbind
2049/tcp open  nfs
MAC Address: AC:1F:6B:7C:DE:15 (Super Micro Computer)

Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds

Best Regards,
Antonio

 

[xiaojueguan]

I also have the similar problem when using the nfs service of freeNas as a backend storage of k8s. After exploring the history of this thread, i also found i have no access of creating anything in the mount points with below details in the client.

Code:

root@k8s1:~# mount -t nfs 10.10.1.139:/mnt/Media/nfs /mnt
root@k8s1:~# cd /mnt/
root@k8s1:/mnt# l
root@k8s1:/mnt# ls
root@k8s1:/mnt# touch test.txt
touch: cannot touch 'test.txt': Permission denied
root@k8s1:/mnt#