Error when I add a share!

chrbar · 28. März 2019

Hi,

I run OVM 4.1.20-1, and I meet some problems when I add a share.

I've an existing LVM from an old OVM 0.5.60, which is correctly detected by LVM Plugin, and I'm able to mount it correctly from OVM "FileSystems" panel.

But when I try to add share from this LVM, I obtain an error when I apply change:

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; systemctl restart 'sharedfolders-documents.mount' 2>&1' with exit code '1': A dependency job for sharedfolders-documents.mount failed. See 'journalctl -xe' for details.

with the details:

Code

Error #0:
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; systemctl restart 'sharedfolders-documents.mount' 2>&1' with exit code '1': A dependency job for sharedfolders-documents.mount failed. See 'journalctl -xe' for details. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)
#1 /usr/share/php/openmediavault/system/systemctl.inc(160): OMV\System\SystemCtl->exec('restart', NULL, false)
#2 /usr/share/openmediavault/engined/module/sharedfolders.inc(66): OMV\System\SystemCtl->restart()
#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleSharedfolders->startService()
#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus8e...', '/tmp/bgoutput6K...')
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#13 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#14 {main}

Alles anzeigen

"journalctl -xe" give:

Code

Mar 27 22:17:15 nas systemd[1]: sharedfolders.mount: Starting requested but asserts failed.
Mar 27 22:17:15 nas systemd[1]: Assertion failed for Mount shared folder / to /sharedfolders//.
-- Subject: Unit sharedfolders.mount has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit sharedfolders.mount has failed.
--
-- The result is assert.
Mar 27 22:17:15 nas systemd[1]: Dependency failed for Mount shared folder documents to /sharedfolders/documents.
-- Subject: Unit sharedfolders-documents.mount has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit sharedfolders-documents.mount has failed.
--
-- The result is dependency.
Mar 27 22:17:15 nas systemd[1]: sharedfolders-documents.mount: Job sharedfolders-documents.mount/start failed with result 'dependency'.

Alles anzeigen

I obtain the same error when I try to add a share from another disk (external disk) newly added and formatted from OVM.
I don't have another internal disk, then I didn't try to add a share from an "generic"internal hdd.

Does someone have some idea why I meet this problem?

If you want I can send you an OVM System Report.

Thanks,
Chris

ryecoaaron · 30. März 2019

Are you trying to create a shared folder called documents?

chrbar · 30. März 2019

Yes, I try to create a shared folder called "documents".
In this case, the folder "documents" is already existing on the "device".
But I obtain the fail, if I try to create a new shared folder on this device (LVM) or on another device.

ryecoaaron · 30. März 2019

Post the output of:

cat /etc/systemd/system/sharedfolders-documents.mount
cat /etc/systemd/system/sharedfolders-documents.automount

chrbar · 31. März 2019

Thanks ryecoaaron, here the results:

At the start (after reboot):

Code

root@nas:~# cat /etc/systemd/system/sharedfolders-documents.mount
cat: /etc/systemd/system/sharedfolders-documents.mount: No such file or directory
root@nas:~# cat /etc/systemd/system/sharedfolders-documents.automount
cat: /etc/systemd/system/sharedfolders-documents.automount: No such file or directory

After having create the share:

Code

root@nas:~# cat /etc/systemd/system/sharedfolders-documents.mount
cat: /etc/systemd/system/sharedfolders-documents.mount: No such file or directory
root@nas:~# cat /etc/systemd/system/sharedfolders-documents.automount
cat: /etc/systemd/system/sharedfolders-documents.automount: No such file or directory

After "Apply" the change:

Code

root@nas:~# cat /etc/systemd/system/sharedfolders-documents.mount
# This configuration file is auto-generated.
[Unit]
Description=Mount shared folder documents to /sharedfolders/documents
DefaultDependencies=no
After=zfs-mount.service
Conflicts=umount.target
RequiresMountsFor=/srv/dev-disk-by-label-4TB1
AssertPathIsDirectory=/srv/dev-disk-by-label-4TB1/documents
AssertPathIsDirectory=/sharedfolders
AssertPathIsMountPoint=/srv/dev-disk-by-label-4TB1


[Mount]
What=/srv/dev-disk-by-label-4TB1/documents
Where=/sharedfolders/documents
Type=none
Options=bind,nofail


[Install]
WantedBy=local-fs.target


root@nas:~# cat /etc/systemd/system/sharedfolders-documents.automount
cat: /etc/systemd/system/sharedfolders-documents.automount: No such file or directory
root@nas:~#

Alles anzeigen

"Apply" error message:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; systemctl restart 'sharedfolders-documents.mount' 2>&1' with exit code '1': A dependency job for sharedfolders-documents.mount failed. See 'journalctl -xe' for details.

"Apply" error details:

Code

Error #0:
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; systemctl restart 'sharedfolders-documents.mount' 2>&1' with exit code '1': A dependency job for sharedfolders-documents.mount failed. See 'journalctl -xe' for details. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)
#1 /usr/share/php/openmediavault/system/systemctl.inc(160): OMV\System\SystemCtl->exec('restart', NULL, false)
#2 /usr/share/openmediavault/engined/module/sharedfolders.inc(66): OMV\System\SystemCtl->restart()
#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleSharedfolders->startService()
#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusK5...', '/tmp/bgoutputEq...')
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#13 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#14 {main}

Alles anzeigen

"journalctl -xe" result:

Code

Mar 30 23:07:00 nas systemd[1]: sharedfolders.mount: Starting requested but asserts failed.
Mar 30 23:07:00 nas systemd[1]: Assertion failed for Mount shared folder / to /sharedfolders//.
-- Subject: Unit sharedfolders.mount has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit sharedfolders.mount has failed.
--
-- The result is assert.
Mar 30 23:07:00 nas systemd[1]: Dependency failed for Mount shared folder documents to /sharedfolders/documents.
-- Subject: Unit sharedfolders-documents.mount has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit sharedfolders-documents.mount has failed.
--
-- The result is dependency.
Mar 30 23:07:00 nas systemd[1]: sharedfolders-documents.mount: Job sharedfolders-documents.mount/start failed with result 'dependency'.

Alles anzeigen

After "revert" (to remove "Apply")

Code

root@nas:~# cat /etc/systemd/system/sharedfolders-documents.mount
# This configuration file is auto-generated.
[Unit]
Description=Mount shared folder documents to /sharedfolders/documents
DefaultDependencies=no
After=zfs-mount.service
Conflicts=umount.target
RequiresMountsFor=/srv/dev-disk-by-label-4TB1
AssertPathIsDirectory=/srv/dev-disk-by-label-4TB1/documents
AssertPathIsDirectory=/sharedfolders
AssertPathIsMountPoint=/srv/dev-disk-by-label-4TB1


[Mount]
What=/srv/dev-disk-by-label-4TB1/documents
Where=/sharedfolders/documents
Type=none
Options=bind,nofail


[Install]
WantedBy=local-fs.target
root@nas:~# cat /etc/systemd/system/sharedfolders-documents.automount
cat: /etc/systemd/system/sharedfolders-documents.automount: No such file or directory
root@nas:~#

Alles anzeigen

ryecoaaron · 31. März 2019

That all looks ok. What is the output of:
grep 4TB1 /proc/mounts
ls -al /srv/dev-disk-by-label-4TB1/

chrbar · 31. März 2019

Thanks, here the outputs...

Current state:

Code

root@nas:~# cat /etc/systemd/system/sharedfolders-documents.mount
cat: /etc/systemd/system/sharedfolders-documents.mount: No such file or directory


root@nas:~# cat /etc/systemd/system/sharedfolders-documents.automount
cat: /etc/systemd/system/sharedfolders-documents.automount: No such file or directory


root@nas:~# grep 4TB1 /proc/mounts
/dev/mapper/4TB1-4TB1 /srv/dev-disk-by-label-4TB1 ext4 rw,noexec,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0


root@nas:~# ls -al /srv/dev-disk-by-label-4TB1/
total 56
drwxr-sr-x 10 openmediavault-webgui users 4096 Mar 30 23:31 .
drwxr-xr-x  4 root                  root  4096 Mar 27 22:14 ..
-rw-------  1 root                  users 7168 Mar 28 21:25 aquota.group
-rw-------  1 root                  users 7168 Mar 28 21:25 aquota.user
drwxr-s---  7 root                  users 4096 Feb 16  2014 documents
drwx------  2 root                  root  4096 Feb 24  2014 lost+found
drwxr-s---  5 root                  users 4096 Feb 16  2014 multimedia
drwxr-s--- 11 root                  users 4096 Mar 25  2014 technology
drwxr-s---  2 root                  users 4096 Mar 28 21:18 test
drwxrwsrwx  2 root                  users 4096 Mar 30 23:28 test1
drwxr-s---  2 root                  users 4096 Mar 30 23:30 test2
drwxrwsr-x  2 root                  users 4096 Mar 30 23:31 test3
root@nas:~#

Alles anzeigen

And after having add share:

Code

root@nas:~# cat /etc/systemd/system/sharedfolders-documents.mount
# This configuration file is auto-generated.
[Unit]
Description=Mount shared folder documents to /sharedfolders/documents
DefaultDependencies=no
After=zfs-mount.service
Conflicts=umount.target
RequiresMountsFor=/srv/dev-disk-by-label-4TB1
AssertPathIsDirectory=/srv/dev-disk-by-label-4TB1/documents
AssertPathIsDirectory=/sharedfolders
AssertPathIsMountPoint=/srv/dev-disk-by-label-4TB1


[Mount]
What=/srv/dev-disk-by-label-4TB1/documents
Where=/sharedfolders/documents
Type=none
Options=bind,nofail


[Install]
WantedBy=local-fs.target


root@nas:~# cat /etc/systemd/system/sharedfolders-documents.automount
cat: /etc/systemd/system/sharedfolders-documents.automount: No such file or directory


root@nas:~# grep 4TB1 /proc/mounts
/dev/mapper/4TB1-4TB1 /srv/dev-disk-by-label-4TB1 ext4 rw,noexec,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0


root@nas:~# ls -al /srv/dev-disk-by-label-4TB1/
total 56
drwxr-sr-x 10 openmediavault-webgui users 4096 Mar 30 23:31 .
drwxr-xr-x  4 root                  root  4096 Mar 27 22:14 ..
-rw-------  1 root                  users 7168 Mar 28 21:25 aquota.group
-rw-------  1 root                  users 7168 Mar 28 21:25 aquota.user
drwxr-s---  7 root                  users 4096 Feb 16  2014 documents
drwx------  2 root                  root  4096 Feb 24  2014 lost+found
drwxr-s---  5 root                  users 4096 Feb 16  2014 multimedia
drwxr-s--- 11 root                  users 4096 Mar 25  2014 technology
drwxr-s---  2 root                  users 4096 Mar 28 21:18 test
drwxrwsrwx  2 root                  users 4096 Mar 30 23:28 test1
drwxr-s---  2 root                  users 4096 Mar 30 23:30 test2
drwxrwsr-x  2 root                  users 4096 Mar 30 23:31 test3
root@nas:~#

Alles anzeigen

KM0201 · 31. März 2019

I had a very similar problem that seemed to start creeping up around the first of the month...

I think somehow it was related to Docker...

Container folder not allowing new folders to be created?

chrbar · 31. März 2019

Thanks KM0201, yes could be... and the error source could be a conflict from the last updates.

In my side, I've no docker running, and I've not yet install the Docker plugin, but I was able to add shares one month ago, including the share "documents" and others folders from the LVM.

To try to find the cause of this error, I've unset all settings that I've done:
- disable SMB,
- umount/mount LVM (or other files systems)
- delete all firewall rules,
- set back default port (80/443),
- uninstall omvextraorg plugin,
but I still have this error!

The last thing that I didn't remove since my last share adding, is default updates.
And if I didn't do a mistake, problem has appeared after updates on 2019-03-17.

KM0201 · 1. April 2019

Then I have no idea what it could be... In my case, the folders I was adding had nothing to do with Docker or my Containers folder... but when I'd get the error, it always referenced my Containers folder.... this made me think to just disable all of my Docker containers an then try to add the share, and it worked perfectly.. restart Docker containers, problem repeats.

Once I remapped my Docker container paths, I've not had the problem since.

Since you're not running Docker, it would appear there is some sort of problem with how the webUI is accessing the shortcuts under /sharedfolders.. I've not saw any other posts on it though, so whatever it is must be a fairly unique set of circumstances, but I'm not really doing anything exotic on my NAS.

wgmcg · 30. August 2019

SO NO SOLUTION? This is kind of a massive show stopping bug.

ryecoaaron · 31. August 2019

Zitat von wgmcg

SO NO SOLUTION? This is kind of a massive show stopping bug.

I can't reproduce this. There are thousands of people using OMV 4.x and not running into this bug. So, I don't think it is so massive. Can you add sharedfolders for a folder that doesn't exist?

guyp2k · 3. November 2019

Zitat von KM0201

Then I have no idea what it could be... In my case, the folders I was adding had nothing to do with Docker or my Containers folder... but when I'd get the error, it always referenced my Containers folder.... this made me think to just disable all of my Docker containers an then try to add the share, and it worked perfectly.. restart Docker containers, problem repeats.

Once I remapped my Docker container paths, I've not had the problem since.

Since you're not running Docker, it would appear there is some sort of problem with how the webUI is accessing the shortcuts under /sharedfolders.. I've not saw any other posts on it though, so whatever it is must be a fairly unique set of circumstances, but I'm not really doing anything exotic on my NAS.

I am having a similar problem, running OMV 5.0.12-1 and Docker. If I disable Docker I can add the share. Did you just remap to the same sharedfolders for your containers? On some of my containers I am binding volumes to /sharedfolders/xxxxx.

Thanks

macom · 3. November 2019

Yes, you should change from

/sharedfolders/xxxx

to

/srv/dev-disk-by-label..../xxxx

Cannot create shared folder on new or existing drive

guyp2k · 3. November 2019

Last question, I am using snapraid and unionfs and have the following:

9281424326658 4 drwxr-xr-x 9 root root 4096 Nov 3 10:09 7b9a5991-098e-4993-a5e3-b9db0fc5699e
2752551 4 drwxrwxrwx 2 root root 4096 Oct 31 16:23 dev-disk-by-label-Docker
2752555 4 drwxrwxrwx 2 root root 4096 Nov 3 07:42 dev-disk-by-label-Test
2 4 drwxr-xr-x 4 root root 4096 Nov 3 08:53 dev-disk-by-label-appdata
2 4 drwxr-xr-x 5 root root 4096 Nov 3 00:59 dev-disk-by-label-data1
2 4 drwxr-xr-x 7 root root 4096 Nov 3 00:59 dev-disk-by-label-data2
2 4 drwxr-xr-x 5 root root 4096 Nov 3 00:59 dev-disk-by-label-data3
2 4 drwxr-xr-x 7 root root 4096 Nov 3 00:59 dev-disk-by-label-data4
2 4 drwxr-xr-x 9 root root 4096 Nov 3 00:59 dev-disk-by-label-data5
2 4 drwxr-xr-x 8 root root 4096 Nov 3 00:59 dev-disk-by-label-data6
2 4 drwxr-xr-x 9 root root 4096 Nov 3 10:09 dev-disk-by-label-data7
2 4 drwxr-xr-x 3 root root 4096 Nov 3 00:59 dev-disk-by-label-parity
2752514 4 drwxr-xr-x 2 ftp nogroup 4096 Oct 30 21:07 ftp
2752516 4 drwxr-xr-x 3 root root 4096 Nov 2 14:49 pillar
2752523 4 drwxr-xr-x 5 root root 4096 Nov 2 14:49 salt

I assume the path would be /srv/7b9a5991-098e-4993-a5e3-b9db0fc5699e/shareX? Given that is the unionFS...

Jetzt mitmachen!