Error When Apply NFS Configuration

DuDu371 · Jul 20th 2023

Hello,

i use OMV from version 2 and it's fantastic. Recently I have encuntered a problem with the service NFS.

I am running version 6.5.0-2 and i cannot change any NFS configuration. When i do so, the service nfs-server will not start.

This is the error that OMV gave me:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color nfs 2>&1' with exit code '1': /usr/local/lib/python3.9/dist-packages/_distutils_hack/__init__.py:33: UserWarning: Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
NasCube:
----------
          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: 11:51:13.314355
    Duration: 114.886 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: 11:51:13.429433
    Duration: 24.623 ms
     Changes:
----------
          ID: configure_nfsd_exports
    Function: file.managed
        Name: /etc/exports
      Result: True
     Comment: File /etc/exports updated
     Started: 11:51:13.454247
    Duration: 80.799 ms
     Changes:
              ----------
              diff:
                  ---
                  +++
                  @@ -3,7 +3,6 @@

                   # /etc/exports: the access control list for filesystems which may be exported
                   #               to NFS clients.  See exports(5).
                  -/export/TempStorage 192.168.1.0/24(fsid=21c1d2be-30ef-4a0d-9705-1a0c4ebd907a,rw,subtree_check,insecure,no_root_squash)
                   /export/Storage 192.168.1.0/24(fsid=064121a0-1dc6-492e-a749-29e042f283b5,rw,subtree_check,insecure)
                   /export/Public 192.168.1.0/24(fsid=ce8480a5-6504-47cd-94f3-887d10305478,rw,subtree_check,insecure)
                   /export/BackupTemp 192.168.1.0/24(fsid=b92cae1e-998a-48a9-b393-ba7f392181b3,rw,subtree_check,insecure)
----------
          ID: start_rpc_statd_service
    Function: service.running
        Name: rpc-statd
      Result: True
     Comment: The service rpc-statd is already running
     Started: 11:51:13.560490
    Duration: 53.241 ms
     Changes:
----------
          ID: start_nfs_server_service
    Function: service.running
        Name: nfs-server
      Result: False
     Comment: A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
     Started: 11:51:13.752877
    Duration: 167.555 ms
     Changes:

Summary for NasCube
------------
Succeeded: 4 (changed=1)
Failed:    1
------------
Total states run:     5
Total run time: 441.104 ms
[ERROR   ] Command 'systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-r887fae4b66b44a8b85cca6d2d74f2f61.scope
A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
[ERROR   ] retcode: 1
[ERROR   ] A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
[ERROR   ] Command 'systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-r5ccabc5da32c4651b89149e446051374.scope
A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
[ERROR   ] retcode: 1
[ERROR   ] A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color nfs 2>&1' with exit code '1': /usr/local/lib/python3.9/dist-packages/_distutils_hack/__init__.py:33: UserWarning: Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
NasCube:
----------
          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: 11:51:13.314355
    Duration: 114.886 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: 11:51:13.429433
    Duration: 24.623 ms
     Changes:
----------
          ID: configure_nfsd_exports
    Function: file.managed
        Name: /etc/exports
      Result: True
     Comment: File /etc/exports updated
     Started: 11:51:13.454247
    Duration: 80.799 ms
     Changes:
              ----------
              diff:
                  ---
                  +++
                  @@ -3,7 +3,6 @@

                   # /etc/exports: the access control list for filesystems which may be exported
                   #               to NFS clients.  See exports(5).
                  -/export/TempStorage 192.168.1.0/24(fsid=21c1d2be-30ef-4a0d-9705-1a0c4ebd907a,rw,subtree_check,insecure,no_root_squash)
                   /export/Storage 192.168.1.0/24(fsid=064121a0-1dc6-492e-a749-29e042f283b5,rw,subtree_check,insecure)
                   /export/Public 192.168.1.0/24(fsid=ce8480a5-6504-47cd-94f3-887d10305478,rw,subtree_check,insecure)
                   /export/BackupTemp 192.168.1.0/24(fsid=b92cae1e-998a-48a9-b393-ba7f392181b3,rw,subtree_check,insecure)
----------
          ID: start_rpc_statd_service
    Function: service.running
        Name: rpc-statd
      Result: True
     Comment: The service rpc-statd is already running
     Started: 11:51:13.560490
    Duration: 53.241 ms
     Changes:
----------
          ID: start_nfs_server_service
    Function: service.running
        Name: nfs-server
      Result: False
     Comment: A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
     Started: 11:51:13.752877
    Duration: 167.555 ms
     Changes:

Summary for NasCube
------------
Succeeded: 4 (changed=1)
Failed:    1
------------
Total states run:     5
Total run time: 441.104 ms
[ERROR   ] Command 'systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-r887fae4b66b44a8b85cca6d2d74f2f61.scope
A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
[ERROR   ] retcode: 1
[ERROR   ] A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
[ERROR   ] Command 'systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-r5ccabc5da32c4651b89149e446051374.scope
A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
[ERROR   ] retcode: 1
[ERROR   ] A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. in /usr/share/php/openmediavault/system/process.inc:220
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(174): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatush9...', '/tmp/bgoutput1I...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(195): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Display More

Then i start digging into the configuration file and found that the service nfs-mountd (/usr/sbin/rpc.mountd) is not starting. The problem seems that the arguments of rpc.mountd that OMV generate into the file /run/sysconfig/nfs-utils are not correct. This is nfs-utils

Code

 PIPEFS_MOUNTPOINT=/run/rpc_pipefs
RPCNFSDARGS="--no-nfs-version 2 --nfs-version --nfs-version 3 --nfs-version 4 --nfs-version 4.1 --nfs-version 4.2 8"
RPCMOUNTDARGS="--no-nfs-version 2 --nfs-version 0 --nfs-version 3 --nfs-version 4 --manage-gids"
STATDARGS=""
GSSDARGS=""
RPCSVCGSSDARGS=""
SVCGSSDARGS=""

The service nfs-mountd is trying to start /usr/sbin/rpc.mountd with $RPCMOUNTARGS and /usr/sbin/rpc.mountd can't recognize the option "--nfs-version 0"..

If i remove that from the file the services are working again.

Any advice?

Thx

ryecoaaron · Jul 20th 2023

What is the output of:

sudo cat /proc/fs/nfsd/versions

sudo awk '{ for (i=1; i<=NF; i++) if ($i > 0) printf "%s,", $i }' /proc/fs/nfsd/versions | sed -e 's/+//g' -e 's/,$//'

votdev · Jul 20th 2023

Please post the output of

Bash

# cat /proc/fs/nfsd/versions
# cat /etc/default/nfs-kernel-server
# cat /etc/default/nfs-common
# omv-confdbadm read --prettify conf.service.nfs

votdev · Jul 20th 2023

Please go to the NFS settings page and re-configure the service.

Select the required NFS versions and uncheck the Enabled checkbox. Save. Enable the checkbox again. Save. Apply the configuration.

DuDu371 · Jul 20th 2023

Quote from votdev

Please go to the NFS settings page and re-configure the service.

Select the required NFS versions and uncheck the Enabled checkbox. Save. Enable the checkbox again. Save. Apply the configuration.

Thank you a lot, after these instrucions, it's working fine!

Britaniola · Jan 21st 2024

Thanks! I had the same issue after an update and this worked perfectly!

Yhoni · Apr 2nd 2024

Quote from votdev

Please go to the NFS settings page and re-configure the service.

Select the required NFS versions and uncheck the Enabled checkbox. Save. Enable the checkbox again. Save. Apply the configuration.

Cool !!

I had the same problem, I followed your instruccions and it worked correctly.

Now OMV is updated and running well.

Thanks.

niemer · May 7th 2024

I'm having this same issue, and the below solution is not working for me. I do have one NFS share working, but I'm unable to add any more.

Quote from votdev

Please go to the NFS settings page and re-configure the service.

Select the required NFS versions and uncheck the Enabled checkbox. Save. Enable the checkbox again. Save. Apply the configuration.

Here's the output of the requested info above

Code

root@vmnas01:~# cat /proc/fs/nfsd/versions
+3 +4 +4.1 +4.2

Code

root@vmnas01:~# cat /etc/default/nfs-kernel-server
# Number of servers to start up
RPCNFSDCOUNT=8

# Runtime priority of server (see nice(1))
RPCNFSDPRIORITY=0

# Options for rpc.mountd.
# If you have a port-based firewall, you might want to set up
# a fixed port here using the --port option. For more information, 
# see rpc.mountd(8) or http://wiki.debian.org/SecuringNFS
# To disable NFSv4 on the server, specify '--no-nfs-version 4' here
RPCMOUNTDOPTS="--manage-gids"

# Do you want to start the svcgssd daemon? It is only required for Kerberos
# exports. Valid alternatives are "yes" and "no"; the default is "no".
NEED_SVCGSSD=""

# Options for rpc.svcgssd.
RPCSVCGSSDOPTS=""

Display More

Code

root@vmnas01:~# cat /etc/default/nfs-common
# If you do not set values for the NEED_ options, they will be attempted
# autodetected; this should be sufficient for most people. Valid alternatives
# for the NEED_ options are "yes" and "no".

# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=

# Options for rpc.statd.
#   Should rpc.statd listen on a specific port? This is especially useful
#   when you have a port-based firewall. To use a fixed port, set this
#   this variable to a statd argument like: "--port 4000 --outgoing-port 4001".
#   For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS
STATDOPTS=

# Do you want to start the idmapd daemon? It is only needed for NFSv4.
NEED_IDMAPD=

# Do you want to start the gssd daemon? It is required for Kerberos mounts.
NEED_GSSD=

Display More

Code

root@vmnas01:~# omv-confdbadm read --prettify conf.service.nfs
{
    "enable": true,
    "shares": {
        "share": [
            {
                "client": "192.168.10.0/24",
                "comment": "",
                "extraoptions": "subtree_check,insecure,no_root_squash,anonuid=1000,anongid=100",
                "mntentref": "86e3fde9-a7c5-47bf-b792-4ec5e34d6e11",
                "options": "rw",
                "sharedfolderref": "03ca9c1a-5aa8-44ff-b5b5-e91a8b208550",
                "uuid": "1ef294f5-ca64-4a0c-aa77-ccd79ab0370b"
            },
            {
                "client": "192.168.10.0/24",
                "comment": "",
                "extraoptions": "subtree_check,insecure,no_root_squash,anonuid=34,anongid=34",
                "mntentref": "95530f64-99ff-441f-96e2-8bc038781dc0",
                "options": "rw",
                "sharedfolderref": "7e922b12-f4f2-4d52-b818-041f99e27795",
                "uuid": "a13aabf7-3a15-47b3-8e32-65a1879e3959"
            }
        ]
    },
    "versions": "3,4,4.1,4.2"
}

Display More

ryecoaaron · May 7th 2024

Quote from niemer

I'm having this same issue, and the below solution is not working for me.

You don't have nfs version 0 in your output. So, it is a different problem. What error are you getting? What is the output of: sudo omv-salt deploy run nfs

niemer · May 7th 2024

Woops, my symptom is the same, but cause is probably different. Would you like me to create a new post for this?

Here's the output in the meantime.

Code

root@vmnas01:~# sudo omv-salt deploy run nfs
debian:
----------
          ID: configure_nfs_conf
    Function: file.managed
        Name: /etc/nfs.conf.d/99-openmediavault.conf
      Result: True
     Comment: File /etc/nfs.conf.d/99-openmediavault.conf is in the correct state
     Started: 12:40:54.861108
    Duration: 81.077 ms
     Changes:   
----------
          ID: configure_idmapd_conf
    Function: file.managed
        Name: /etc/idmapd.conf
      Result: True
     Comment: File /etc/idmapd.conf is in the correct state
     Started: 12:40:54.942296
    Duration: 83.95 ms
     Changes:   
----------
          ID: divert_idmapd_conf
    Function: omv_dpkg.divert_add
        Name: /etc/idmapd.conf
      Result: True
     Comment: Leaving 'local diversion of /etc/idmapd.conf to /etc/idmapd.conf.distrib'
     Started: 12:40:55.029331
    Duration: 8.346 ms
     Changes:   
----------
          ID: configure_nfs_exports
    Function: file.managed
        Name: /etc/exports
      Result: True
     Comment: File /etc/exports is in the correct state
     Started: 12:40:55.037817
    Duration: 112.296 ms
     Changes:   
----------
          ID: divert_nfs_exports
    Function: omv_dpkg.divert_add
        Name: /etc/exports
      Result: True
     Comment: Leaving 'local diversion of /etc/exports to /etc/exports.distrib'
     Started: 12:40:55.150281
    Duration: 6.552 ms
     Changes:   
----------
          ID: stop_nfs_blkmap_service
    Function: service.dead
        Name: nfs-blkmap
      Result: True
     Comment: The service nfs-blkmap is already dead
     Started: 12:40:57.306321
    Duration: 19.763 ms
     Changes:   
----------
          ID: mask_nfs_blkmap_service
    Function: service.masked
        Name: nfs-blkmap
      Result: True
     Comment: Service nfs-blkmap is already masked
     Started: 12:40:57.326185
    Duration: 0.416 ms
     Changes:   
----------
          ID: start_nfs_server_service
    Function: service.running
        Name: nfs-server
      Result: True
     Comment: The service nfs-server is already running
     Started: 12:40:57.326970
    Duration: 17.617 ms
     Changes:   
----------
          ID: restart_nfs_utils_service
    Function: service.running
        Name: nfs-utils
      Result: True
     Comment: The service nfs-utils is already running
     Started: 12:40:57.344777
    Duration: 17.965 ms
     Changes:   

Summary for debian
------------
Succeeded: 9
Failed:    0
------------
Total states run:     9
Total run time: 347.982 ms

Display More

ryecoaaron · May 7th 2024

That looks fine. What error are you getting when adding another share? Please cut&paste the error from the bell in the top right of the omv interface.

niemer · May 7th 2024

It's a long one, too long to post here. I've created a gist for it here: OMV NFS Error (github.com)

ryecoaaron · May 7th 2024

I would remove quotas from the filesystems with the mounteditor plugin. Then try again. If that doesn't work, reboot and try again.

Quote from niemer

I've created a gist for it here:

You can attach a text file on the forum too.

niemer · May 7th 2024

I removed quotas from all mount points with the plugin and it looks like one NFS share stuck, but I'm getting the same error when I try to add another. Reboot did not make a difference.

However, they all seem to show up in Proxmox, but one is missing from OMV...

I put them in pastebins or gists because some people have had issue with downloading random files in my past. It's pretty habitual now.

ryecoaaron · May 8th 2024

Quote from niemer

I removed quotas from all mount points with the plugin and it looks like one NFS share stuck, but I'm getting the same error when I try to add another. Reboot did not make a difference.

The mounteditor plugin should remove the aquota files. If it isn't able to, you should click the remove quotas button again after the reboot.

niemer · May 8th 2024

I got the last share to stick around, but it's still behaving oddly. These are the steps I took:

Created the share
Rebooted
Removed quotas on all mount points
Applied changes
- The error popped up at this point
Reverted the changes

After all of that the share is still there. I'm not sure why I'm having to jump through all these hoops.

ryecoaaron · May 8th 2024

Quote from niemer

Reverted the changes

After all of that the share is still there. I'm not sure why I'm having to jump through all these hoops.

Because you reverted the changes. Don't do that (at least while I am helping). I have no idea why you have to do this because I can't reproduce it and no one else seems to be having this issue. Do this (doesn't matter if you have already done it - please do it again since I don't know what condition reverting has put your system):

delete your nfs shares (don't apply since we know it will fail)

Click remove quota options for your filesystems

reboot

Click remove quota options for your filesystems

reboot

sudo omv-salt deploy run nfs

create an nfs share

niemer · May 8th 2024

The hoops I was referring to have nothing to do with your support, for that I am immensely appreciative, I was referring to the steps I had to take to get the share to remain displayed in the list. Sorry if there was any confusion.

I followed your steps and got the error again.

ryecoaaron · May 8th 2024

Quote from niemer

I was referring to the steps I had to take to get the share to remain displayed in the list.

They aren't typical.

Quote from niemer

I followed your steps and got the error again.

At which step? What is the error? The same error trying to delete the aquota files? If yes, what is the output of:

find /srv/dev-* -maxdepth 1 -name "aquota*" -ls

niemer · May 8th 2024

It doesn't actually seem like mounteditor is deleting the quota files. I did ls -la /srv/dev-disk-by-uuid-1f791413-f69b-4b93-9e49-12802fa61dcd/ before and after using mounteditor to delete quota files and this was the output both before and after.

Code

root@vmnas01:~# ls -la /srv/dev-disk-by-uuid-1f791413-f69b-4b93-9e49-12802fa61dcd/
total 3617760
drwxr-xr-x  4 root root        4096 May  8 04:06 .
drwxr-xr-x 19 root root        4096 Apr 30 20:02 ..
-rw-------  1 root root        7168 Feb  6 18:28 aquota.group
-rw-------  1 root root        7168 Feb  6 18:28 aquota.user
drwxrwsr-x  7 root users       4096 Feb 20 21:11 data
drwx------  2 root root       16384 Jul 16  2020 lost+found
-rw-------  1 root root  3704534563 May  8 04:05 snapraid.content

The errors were

Code

[ERROR   ] retcode: 1
[ERROR   ] {'pid': 12622, 'retcode': 1, 'stdout': '', 'stderr': "find: cannot delete '/srv/dev-disk-by-uuid-71bd77f0-1485-4b1a-b76e-92a3192acc9e/aquota.group': Operation not permitted\nfind: cannot delete '/srv/dev-disk-by-uuid-71bd77f0-1485-4b1a-b76e-92a3192acc9e/aquota.user': Operation not permitted"}
[ERROR   ] Command 'find' failed with return code: 1
[ERROR   ] stderr: find: cannot delete '/srv/dev-disk-by-uuid-1f791413-f69b-4b93-9e49-12802fa61dcd/aquota.group': Operation not permitted
find: cannot delete '/srv/dev-disk-by-uuid-1f791413-f69b-4b93-9e49-12802fa61dcd/aquota.user': Operation not permitted

Here's the output you requested

Code

root@vmnas01:~# find /srv/dev-* -maxdepth 1 -name "aquota*" -ls
       13      8 -rw-------   1 root     root         7168 Feb  6 18:28 /srv/dev-disk-by-uuid-1f791413-f69b-4b93-9e49-12802fa61dcd/aquota.group
       12      8 -rw-------   1 root     root         7168 Feb  6 18:28 /srv/dev-disk-by-uuid-1f791413-f69b-4b93-9e49-12802fa61dcd/aquota.user
       13      8 -rw-------   1 root     users        6144 Feb  6 18:28 /srv/dev-disk-by-uuid-71bd77f0-1485-4b1a-b76e-92a3192acc9e/aquota.group
       14      8 -rw-------   1 root     users        6144 Feb  6 18:28 /srv/dev-disk-by-uuid-71bd77f0-1485-4b1a-b76e-92a3192acc9e/aquota.user
       12      8 -rw-------   1 root     root         7168 Feb  6 18:28 /srv/dev-disk-by-uuid-8f5e1760-8adc-4f81-a24d-025d7c004253/aquota.user
       13      8 -rw-------   1 root     root         7168 Feb  6 18:28 /srv/dev-disk-by-uuid-8f5e1760-8adc-4f81-a24d-025d7c004253/aquota.group
       12      8 -rw-------   1 root     users        7168 Feb  6 18:28 /srv/dev-disk-by-uuid-9c387abb-39ec-4126-895a-b233c5525bbf/aquota.group
       16      8 -rw-------   1 root     users        7168 Feb  6 18:28 /srv/dev-disk-by-uuid-9c387abb-39ec-4126-895a-b233c5525bbf/aquota.user
       13      8 -rw-------   1 root     root         7168 Feb  6 18:28 /srv/dev-disk-by-uuid-9cc2d925-e459-4037-9d45-5e030b5af1f6/aquota.group
       15      8 -rw-------   1 root     root         7168 Feb  6 18:28 /srv/dev-disk-by-uuid-9cc2d925-e459-4037-9d45-5e030b5af1f6/aquota.user

Display More

Error When Apply NFS Configuration

votdev Jul 20th 2023

votdev Jan 22nd 2024

Participate now!

Similar Threads

omv-extras 6.3 / openmediavault-compose 6.7

OMV6 reboots when applying configuration change

Can't login to webui after upgrading from omv5 to omv6? [Connection Refused]

Upgraded to 6.4.0 from 6.3.10 and having problems booting

ZFS webui can not apply changes.

Error 0 to enable NFS