Filebrowser No Longer works after restart of OMV

mjhos · Nov 22nd 2023

Hey peeps! So I am running OMV on my Raspberry Pi 4 for almost about a month now and everything was going well with the "File Browser" plugin.

Today I had to restart my Pi as I was moving racks and then when I turned it back on, everything is working file other than the "File Browser" everytime I try to enable it there is an internal error (The error message is posted below).

All commands outputs are given below. Would highly appreciate for any help thank you.

Raspberry Pi Info:

Code

OS: Raspbian GNU/Linux 11 (bullseye) aarc
Host: Raspberry Pi 4 Model B Rev 1.5
Kernel: 6.1.21-v8+
Uptime: 44 mins
Packages: 712 (dpkg)
Shell: bash 5.1.4
Terminal: /dev/pts/0
CPU: BCM2835 (4) @ 1.800GHz
Memory: 776MiB / 7812MiB

ERROR Message:

Diff

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 filebrowser 2>&1' with exit code '1': pi-nas:
----------
diff:
---
+++
@@ -12,7 +12,7 @@
Restart=on-failure
TimeoutStopSec=70
ExecStartPre=/bin/rm -f %t/pod-filebrowser.pid %t/pod-filebrowser.pod-id
-ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfile %t/pod-filebrowser.pid --pod-id-file %t/pod-filebrowser.pod-id --name=filebrowser -p 8080:8443 --replace
+ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfile %t/pod-filebrowser.pid --pod-id-file %t/pod-filebrowser.pod-id --name=filebrowser -p 3670:8443 --replace
ExecStart=/usr/bin/podman pod start --pod-id-file %t/pod-filebrowser.pod-id
ExecStop=/usr/bin/podman pod stop --ignore --pod-id-file %t/pod-filebrowser.pod-id
ExecStopPost=/usr/bin/podman pod rm --ignore -f --pod-id-file %t/pod-filebrowser.pod-id
----------



Summary for pi-nas
-------------
Succeeded: 11 (changed=4)
Failed:     1
-------------
Total states run:     12
Total run time:   10.016 s
[ERROR   ] Command '/bin/systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-rda94832c0f88403da8c6196a77e606f7.scope
Job for pod-filebrowser.service failed because the control process exited with error code.
See "systemctl status pod-filebrowser.service" and "journalctl -xe" for details.
[ERROR   ] retcode: 1
[ERROR   ] Job for pod-filebrowser.service failed because the control process exited with error code.
See "systemctl status pod-filebrowser.service" and "journalctl -xe" for details.
[ERROR   ] Command '/bin/systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-rde1c73b0982642d0b163a3f87d432ca2.scope
Job for pod-filebrowser.service failed because the control process exited with error code.
See "systemctl status pod-filebrowser.service" and "journalctl -xe" for details.
[ERROR   ] retcode: 1
[ERROR   ] Job for pod-filebrowser.service failed because the control process exited with error code.
See "systemctl status pod-filebrowser.service" and "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 filebrowser 2>&1' with exit code '1': pi-nas:


Summary for pi-nas
-------------
Succeeded: 11 (changed=4)
Failed:     1
-------------
Total states run:     12
Total run time:   10.016 s
[ERROR   ] Command '/bin/systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-rda94832c0f88403da8c6196a77e606f7.scope
Job for pod-filebrowser.service failed because the control process exited with error code.
See "systemctl status pod-filebrowser.service" and "journalctl -xe" for details.
[ERROR   ] retcode: 1
[ERROR   ] Job for pod-filebrowser.service failed because the control process exited with error code.
See "systemctl status pod-filebrowser.service" and "journalctl -xe" for details.
[ERROR   ] Command '/bin/systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-rde1c73b0982642d0b163a3f87d432ca2.scope
Job for pod-filebrowser.service failed because the control process exited with error code.
See "systemctl status pod-filebrowser.service" and "journalctl -xe" for details.
[ERROR   ] retcode: 1
[ERROR   ] Job for pod-filebrowser.service failed because the control process exited with error code.
See "systemctl status pod-filebrowser.service" and "journalctl -xe" for details. in /usr/share/php/openmediavault/system/process.inc:242
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(178): 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(620): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusEQ...', '/tmp/bgoutputdT...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(199): 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

OUTPUT of "systemctl status pod-filebrowser.service":

Code

pod-filebrowser.service - Podman pod-filebrowser.service
Loaded: loaded (/etc/systemd/system/pod-filebrowser.service; disabled; ven>
Active: failed (Result: exit-code) since Tue 2023-11-21 18:44:21 EST; 7min>
Process: 11487 ExecStartPre=/bin/rm -f /run/pod-filebrowser.pid /run/pod-fi>
Process: 11488 ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfi>
Process: 11519 ExecStart=/usr/bin/podman pod start --pod-id-file /run/pod-f>
Process: 11579 ExecStopPost=/usr/bin/podman pod rm --ignore -f --pod-id-fil>
CPU: 823ms

OUTPUT of "journalctl -xe":

Code

Nov 21 18:11:40 pi-nas sudo[5639]:    mjhos : TTY=pts/0 ; PWD=/home/mjhos ; USER=root ; COMMAND=/usr/bin/podman status
Nov 21 18:11:40 pi-nas sudo[5639]: pam_unix(sudo:session): session opened for user root(uid=0) by mjhos(uid=1000)
Nov 21 18:11:40 pi-nas sudo[5639]: pam_unix(sudo:session): session closed for user root
Nov 21 18:13:13 pi-nas sudo[5788]:    mjhos : TTY=pts/0 ; PWD=/home/mjhos ; USER=root ; COMMAND=/usr/bin/podman pod create --infra-conmon-pidfile /run/pod-filebrowser.pid --pod-id-file /run/pod-filebrowser.pod-id --name=filebrowser -p 8080:8443
Nov 21 18:13:13 pi-nas sudo[5788]: pam_unix(sudo:session): session opened for user root(uid=0) by mjhos(uid=1000)
Nov 21 18:13:13 pi-nas sudo[5788]: pam_unix(sudo:session): session closed for user root
Nov 21 18:14:15 pi-nas sudo[5920]:    mjhos : TTY=pts/0 ; PWD=/run ; USER=root ; COMMAND=/usr/bin/podman images
Nov 21 18:14:15 pi-nas sudo[5920]: pam_unix(sudo:session): session opened for user root(uid=0) by mjhos(uid=1000)
Nov 21 18:14:16 pi-nas systemd[5597]: var-lib-containers-storage-overlay.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit UNIT has successfully entered the 'dead' state.
Nov 21 18:14:16 pi-nas sudo[5920]: pam_unix(sudo:session): session closed for user root
Nov 21 18:16:46 pi-nas sudo[6282]:    mjhos : TTY=pts/0 ; PWD=/run ; USER=root ; COMMAND=/usr/bin/podman run --conmon-pidfile /run/container-filebrowser.pid --cidfile /run/container-filebrowser.ctr-id --cgroups=no-conmon -d --replace --pull=never --name=filebrowser -p 3670:3670 -u filebrowser:users
Nov 21 18:16:46 pi-nas sudo[6282]: pam_unix(sudo:session): session opened for user root(uid=0) by mjhos(uid=1000)
Nov 21 18:16:46 pi-nas sudo[6282]: pam_unix(sudo:session): session closed for user root
Nov 21 18:20:07 pi-nas systemd[5597]: var-lib-containers-storage-overlay.mount: Succeeded.

Display More

fbeye · Nov 22nd 2023

Mine still works it just magically doesnot like my l/p...which bitwarden has saved so ITS NOT FNG ME

votdev · Nov 22nd 2023

Are your plugin up to date? With the latest filebrowser plugin update the package dependency of catatonit has been added which seems to be necessary since some time.

fbeye · Nov 22nd 2023

It happened again, it literally happened again.

I logged in this morning... worked, saved it, again bitwarden, now it does not accept l/p

fbeye · Nov 22nd 2023

Well for whatever reason, filebrowser had no read/write access, re-enabled it, seems to work.

Filebrowser No Longer works after restart of OMV

Raspberry Pi Info:

ERROR Message:

OUTPUT of "systemctl status pod-filebrowser.service":

OUTPUT of "journalctl -xe":

ryecoaaron Nov 22nd 2023

Participate now!

Similar Threads

FileBrowser not accessible

Tags