NFS down with Omv 6.5.7 update

Quote from ryecoaaron

What is the output of:

sudo systemctl stop nfs-server

sudo omv-salt deploy run nfs

I managed to get nfs working again by a combination of enabling / disabling versions and rebooting.

Here is the output after it was fixed, jut for info -

root@omvll:~# sudo systemctl stop nfs-server

root@omvll:~# sudo omv-salt deploy run nfs

debian:

----------

ID: configure_default_nfs-common

Function: file.managed

Name: /etc/default/nfs-common

Result: True

Comment: File /etc/default/nfs-common is in the correct state

Started: 15:52:44.014297

Duration: 414.699 ms

Changes:

----------

ID: configure_default_nfs-kernel-server

Function: file.managed

Name: /etc/default/nfs-kernel-server

Result: True

Comment: File /etc/default/nfs-kernel-server is in the correct state

Started: 15:52:44.429255

Duration: 257.307 ms

Changes:

----------

ID: configure_nfsd_exports

Function: file.managed

Name: /etc/exports

Result: True

Comment: File /etc/exports is in the correct state

Started: 15:52:44.686763

Duration: 366.805 ms

Changes:

----------

ID: start_rpc_statd_service

Function: service.running

Name: rpc-statd

Result: True

Comment: The service rpc-statd is already running

Started: 15:52:55.282375

Duration: 61.865 ms

Changes:

----------

ID: start_nfs_server_service

Function: service.running

Name: nfs-server

Result: True

Comment: Service nfs-server is already enabled, and is running

Started: 15:52:55.345567

Duration: 1476.248 ms

Changes:

----------

nfs-server:

True

Summary for debian

------------

Succeeded: 5 (changed=1)

Failed: 0

------------

Total states run: 5

Total run time: 2.577 s

Quote from votdev

Check out https://github.com/openmediavault/openmediavault/issues/1583. The user reported the issue did not configure the NFS share correctly.

Run journalctl -u nfs-server | tee to get more info why the daemon is not starting.

I did eventually get it running, but I'm intrigued as to what the

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/seagate1media (fsid=11807640-0262-4435-b9ec-fe635ac42e5e,rw,subtree_check,insecure), suggest *(fsid=11807640-0262-4435-b9ec-fe635ac42e5e,rw,subtree_check,insecure) to avoid warning

messages are telling me. Should I modify my nfs shares?

Anyway here is the first part of the full output of journalctl -u nfs-server | tee in case it helps..

-- Journal begins at Fri 2022-10-21 21:15:13 BST, ends at Fri 2023-08-18 16:01:54 BST. --

Oct 21 21:15:14 omvll systemd[1]: Starting NFS server and services...

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/sabnzbd (fsid=33905c64-aa35-4451-bb92-6280e84f4277,rw,subtree_check,insecure), suggest *(fsid=33905c64-aa35-4451-bb92-6280e84f4277,rw,subtree_check,insecure) to avoid warning

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/seagate1media (fsid=11807640-0262-4435-b9ec-fe635ac42e5e,rw,subtree_check,insecure), suggest *(fsid=11807640-0262-4435-b9ec-fe635ac42e5e,rw,subtree_check,insecure) to avoid warning

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/seagate2media (fsid=5b5f752d-a686-4b78-a5a6-0c2858e45638,rw,subtree_check,insecure), suggest *(fsid=5b5f752d-a686-4b78-a5a6-0c2858e45638,rw,subtree_check,insecure) to avoid warning

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/seagate3media (fsid=dbbb977d-4961-4601-9a31-29c25a269ae2,rw,subtree_check,insecure), suggest *(fsid=dbbb977d-4961-4601-9a31-29c25a269ae2,rw,subtree_check,insecure) to avoid warning

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/seagate4media (fsid=b0bfeb8b-5a1b-400a-9242-28102f57b388,rw,subtree_check,insecure), suggest *(fsid=b0bfeb8b-5a1b-400a-9242-28102f57b388,rw,subtree_check,insecure) to avoid warning

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/seagate5media (fsid=b8be7d76-4772-4b25-aeef-239487475624,rw,subtree_check,insecure), suggest *(fsid=b8be7d76-4772-4b25-aeef-239487475624,rw,subtree_check,insecure) to avoid warning

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/wd1media (fsid=74a0d595-be73-4e33-b07c-cb34b4ed19ae,rw,subtree_check,insecure), suggest *(fsid=74a0d595-be73-4e33-b07c-cb34b4ed19ae,rw,subtree_check,insecure) to avoid warning

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/seagate6media (fsid=427cdd6d-be4e-4d02-9dcb-2e70c04856b3,rw,subtree_check,insecure), suggest *(fsid=427cdd6d-be4e-4d02-9dcb-2e70c04856b3,rw,subtree_check,insecure) to avoid warning

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export/public (fsid=fa34f3ad-0f0d-4b6b-8299-33065448d719,rw,subtree_check,insecure), suggest *(fsid=fa34f3ad-0f0d-4b6b-8299-33065448d719,rw,subtree_check,insecure) to avoid warning

Oct 21 21:15:14 omvll exportfs[715]: exportfs: No host name given with /export (ro,fsid=0,root_squash,no_subtree_check,hide), suggest *(ro,fsid=0,root_squash,no_subtree_check,hide) to avoid warning

Oct 21 21:15:16 omvll systemd[1]: Started NFS server and services.

Oct 21 21:51:25 omvll systemd[1]: Stopping NFS server and services...

Oct 21 21:51:25 omvll systemd[1]: nfs-server.service: Succeeded.

Oct 21 21:51:25 omvll systemd[1]: Stopped NFS server and services.

Oct 21 21:51:26 omvll systemd[1]: Starting NFS server and services...

Quote from votdev

You need to set the IP range that is allowed to access the share in the NFS share settings page. It seems a * is also allowed.

Thanks.

From memory, previous releases allowed you to leave the IP range blank, but since the last OMV upgrade new shares required it. I think I had some of my older shares with the IP range blank. I've now edited all the entries to have an IP range assigned.