File Browser plugin error when enabling

hAxelS · 2. April 2022

Hi guys! I installed the File Browser plugin, install worked but when i try to enable it i get this error and was wondering if anyone could help! Thanks in advance.

Fyi im running OMV6 on a Raspberry Pi 4

Error:

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': raspberrypi:

----------

ID: create_filebrowser_container_systemd_unit_file

Function: file.managed

Name: /etc/systemd/system/container-filebrowser.service

Result: True

Comment: File /etc/systemd/system/container-filebrowser.service is in the correct state

Started: 22:44:26.406795

Duration: 152.537 ms

Changes:

----------

ID: filebrowser_systemctl_daemon_reload

Function: module.run

Result: True

Comment: service.systemctl_reload: True

Started: 22:44:26.561780

Duration: 733.404 ms

Changes:

----------

service.systemctl_reload:

True

----------

ID: filebrowser_pull_app_image

Function: cmd.run

Name: podman pull docker.io/filebrowser/filebrowser:latest

Result: True

Comment: unless condition is true

Started: 22:44:27.299482

Duration: 4509.487 ms

Changes:

----------

ID: filebrowser_app_image_exists

Function: cmd.run

Name: podman image exists docker.io/filebrowser/filebrowser:latest

Result: True

Comment: Command "podman image exists docker.io/filebrowser/filebrowser:latest" run

Started: 22:44:31.809805

Duration: 185.192 ms

Changes:

----------

pid:

952077

retcode:

0

stderr:

stdout:

----------

ID: create_filebrowser_database

Function: file.managed

Name: /var/cache/filebrowser/database.db

Result: True

Comment: File /var/cache/filebrowser/database.db exists with proper permissions. No changes made.

Started: 22:44:31.995719

Duration: 5.358 ms

Changes:

----------

ID: configure_filebrowser

Function: file.managed

Name: /var/cache/filebrowser/filebrowser.json

Result: True

Comment: File /var/cache/filebrowser/filebrowser.json is in the correct state

Started: 22:44:32.001534

Duration: 30.595 ms

Changes:

----------

ID: start_filebrowser_service

Function: service.running

Name: container-filebrowser

Result: False

Comment: Job for container-filebrowser.service failed because the control process exited with error code.

See "systemctl status container-filebrowser.service" and "journalctl -xe" for details.

Started: 22:44:32.034023

Duration: 993.817 ms

Changes:

Summary for raspberrypi

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

Succeeded: 6 (changed=2)

Failed: 1

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

Total states run: 7

Total run time: 6.610 s

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': raspberrypi:

----------

ID: create_filebrowser_container_systemd_unit_file

Function: file.managed

Name: /etc/systemd/system/container-filebrowser.service

Result: True

Comment: File /etc/systemd/system/container-filebrowser.service is in the correct state

Started: 22:44:26.406795

Duration: 152.537 ms

Changes:

----------

ID: filebrowser_systemctl_daemon_reload

Function: module.run

Result: True

Comment: service.systemctl_reload: True

Started: 22:44:26.561780

Duration: 733.404 ms

Changes:

----------

service.systemctl_reload:

True

----------

ID: filebrowser_pull_app_image

Function: cmd.run

Name: podman pull docker.io/filebrowser/filebrowser:latest

Result: True

Comment: unless condition is true

Started: 22:44:27.299482

Duration: 4509.487 ms

Changes:

----------

ID: filebrowser_app_image_exists

Function: cmd.run

Name: podman image exists docker.io/filebrowser/filebrowser:latest

Result: True

Comment: Command "podman image exists docker.io/filebrowser/filebrowser:latest" run

Started: 22:44:31.809805

Duration: 185.192 ms

Changes:

----------

pid:

952077

retcode:

0

stderr:

stdout:

----------

ID: create_filebrowser_database

Function: file.managed

Name: /var/cache/filebrowser/database.db

Result: True

Comment: File /var/cache/filebrowser/database.db exists with proper permissions. No changes made.

Started: 22:44:31.995719

Duration: 5.358 ms

Changes:

----------

ID: configure_filebrowser

Function: file.managed

Name: /var/cache/filebrowser/filebrowser.json

Result: True

Comment: File /var/cache/filebrowser/filebrowser.json is in the correct state

Started: 22:44:32.001534

Duration: 30.595 ms

Changes:

----------

ID: start_filebrowser_service

Function: service.running

Name: container-filebrowser

Result: False

Comment: Job for container-filebrowser.service failed because the control process exited with error code.

See "systemctl status container-filebrowser.service" and "journalctl -xe" for details.

Started: 22:44:32.034023

Duration: 993.817 ms

Changes:

Summary for raspberrypi

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

Succeeded: 6 (changed=2)

Failed: 1

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

Total states run: 7

Total run time: 6.610 s in /usr/share/php/openmediavault/system/process.inc:197

Stack trace:

#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

#1 /usr/share/openmediavault/engined/rpc/config.inc(170): 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(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusOi...', '/tmp/bgoutputz9...')

#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

#7 /usr/share/openmediavault/engined/rpc/config.inc(192): 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}

Cht64bit · 3. April 2022

I have the same issue.

votdev · 3. April 2022

Will be fixed in next version.

hAxelS · 3. April 2022

Zitat von votdev

Will be fixed in next version.

Alright! Do u have any information on when the new update is coming?

Thanks for letting me know!

votdev · 3. April 2022

It's out now. Redeploy with omv-salt deploy run filebrowser after the package has been upgraded. When the new plugins have been stabilized the manual redeployment is not necessary anymore.

sacc · 16. Mai 2022

i have the same issue.

version:

openmediavault-filebrowser/shaitan,shaitan,shaitan,shaitan,now 6.0.1-1 all [installed]

openmediavault File Browser plugin.

is it the newest version now?

sacc · 16. Mai 2022

after adding ssl certification and share folders, and press save button,it failed.

then i use omv-salt deploy run xxx

ID: start_filebrowser_service

Function: service.running

Name: pod-filebrowser

Result: False

Comment: 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.

Started: 17:03:30.082553

Duration: 21920.337 ms

Changes:

Summary for blackstar

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

Succeeded: 11 (changed=3)

Failed: 1

Zoki · 16. Mai 2022

Did you do that:

See "systemctl status pod-filebrowser.service" and "journalctl -xe" for details.

sacc · 17. Mai 2022

systemctrl output:

● pod-filebrowser.service - Podman pod-filebrowser.service

Loaded: loaded (/etc/systemd/system/pod-filebrowser.service; disabled; vendor p>

Active: activating (start-pre) since Tue 2022-05-17 09:17:01 CST; 29s ago

Process: 10320 ExecStartPre=/bin/rm -f /run/pod-filebrowser.pid /run/pod-filebro>

Cntrl PID: 10321 (podman)

Tasks: 11 (limit: 18736)

Memory: 11.4M

CPU: 282ms

CGroup: /system.slice/pod-filebrowser.service

└─10321 /usr/bin/podman pod create --infra-conmon-pidfile /run/pod-file>

May 17 09:17:01 star systemd[1]: Starting Podman pod-filebrowser.service...

journal output

A start job for unit container-filebrowser-proxy.service has finished with a fail>

The job identifier is 7465 and the job result is dependency.

May 17 09:26:07 blackstar systemd[1]: container-filebrowser-proxy.service: Job conta>

May 17 09:26:07 star systemd[1]: Dependency failed for Podman container-filebro>

Subject: A start job for unit container-filebrowser-app.service has failed

Defined-By: systemd.

Support: https://www.debian.org/support

A start job for unit container-filebrowser-app.service has finished with a failur>

The job identifier is 7364 and the job result is dependency.

May 17 09:26:07 blackstar systemd[1]: container-filebrowser-app.service: Job contain>

May 17 09:26:07 star systemd[1]: pod-filebrowser.service: Scheduled restart job>

Subject: Automatic restarting of a unit has been scheduled

Defined-By: systemd

Support: https://www.debian.org/support

Automatic restarting of the unit pod-filebrowser.service has been sche

Zoki · 17. Mai 2022

A dependency failed:

systemctl list-dependencies pod-filebrowser

and check these services starting from top

sacc · 19. Mai 2022

i checked the images and containers by command 'podman'.

i found there were images (caddy and filebrowser), but no containers.

"systemctl list-dependencies pod-filebrowser"

├─container-filebrowser-app.service

├─container-filebrowser-proxy.service

the two container doesn't exist.

votdev · 19. Mai 2022

Zitat von sacc

i checked the images and containers by command 'podman'.
i found there were images (caddy and filebrowser), but no containers.
"systemctl list-dependencies pod-filebrowser"
├─container-filebrowser-app.service
├─container-filebrowser-proxy.service
the two container doesn't exist.

Alles anzeigen

In that case a omv-salt deploy run filebrowser will pull the container images and redeploy the service configuration.

sacc · 19. Mai 2022

Zitat von votdev

In that case a omv-salt deploy run filebrowser will pull the container images and redeploy the service configuration.

i have try that, and the result is below

ID: start_filebrowser_service

Function: service.running

Name: pod-filebrowser

Result: False

Comment: 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.

Started: 21:37:35.295591

Duration: 46387.496 ms

Changes:

systemctl status pod-filebrowser.service

● pod-filebrowser.service - Podman pod-filebrowser.service

Loaded: loaded (/etc/systemd/system/pod-filebrowser.service; disabled; vendor p>

Active: activating (start-pre) since Thu 2022-05-19 21:40:23 CST; 2s ago

Process: 199596 ExecStartPre=/bin/rm -f /run/pod-filebrowser.pid /run/pod-filebr>

Cntrl PID: 199597 (podman)

Tasks: 9 (limit: 18736)

Memory: 11.1M

CPU: 292ms

CGroup: /system.slice/pod-filebrowser.service

└─199597 /usr/bin/podman pod create --infra-conmon-pidfile /run/pod-fil>

May 19 21:40:23 blackstar systemd[1]: Starting Podman pod-filebrowser.service...

journalctl -xe

░░ Automatic restarting of the unit pod-filebrowser.service has been scheduled, as t>

░░ the configured Restart= setting for the unit.

May 19 21:41:23 blackstar systemd[1]: Stopped Podman pod-filebrowser.service.

░░ Subject: A stop job for unit pod-filebrowser.service has finished

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ A stop job for unit pod-filebrowser.service has finished.

░░

░░ The job identifier is 177509 and the job result is done.

May 19 21:41:23 blackstar systemd[1]: Starting Podman pod-filebrowser.service...

░░ Subject: A start job for unit pod-filebrowser.service has begun execution

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ A start job for unit pod-filebrowser.service has begun execution.

░░

░░ The job identifier is 177509.

May 19 21:41:24 blackstar systemd[1]: Created slice cgroup machine-libpod_pod_3e6a18>

░░ Subject: A start job for unit machine-libpod_pod_3e6a18cc53a7c7f8ee096b76c0de9b96>

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ A start job for unit machine-libpod_pod_3e6a18cc53a7c7f8ee096b76c0de9b96b5ff7b638>

░░

░░ The job identifier is 177719.

May 19 21:41:24 blackstar systemd[165785]: run-docker-runtime\x2drunc-moby-273493c87>

░░ Subject: Unit succeeded

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ The unit UNIT has successfully entered the 'dead' state.

May 19 21:41:24 blackstar systemd[1]: run-docker-runtime\x2drunc-moby-273493c879ec56>

░░ Subject: Unit succeeded

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ The unit run-docker-runtime\x2drunc-moby-273493c879ec56a25d7555570244aa361418a958>

May 19 21:41:34 blackstar systemd[165785]: run-docker-runtime\x2drunc-moby-273493c87>

░░ Subject: Unit succeeded

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ The unit UNIT has successfully entered the 'dead' state.

votdev · 19. Mai 2022

What is the output of sudo podman images?

sacc · 19. Mai 2022

Zitat von votdev

What is the output of sudo podman images?

REPOSITORY TAG IMAGE ID CREATED SIZE

docker.io/library/caddy latest e63f36e9049f 12 days ago 44.9 MB

docker.io/filebrowser/filebrowser latest a4a102abcc8d 2 months ago 31.7 MB

sacc · 23. Mai 2022

Zitat von sacc

REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/library/caddy latest e63f36e9049f 12 days ago 44.9 MB
docker.io/filebrowser/filebrowser latest a4a102abcc8d 2 months ago 31.7 MB

it sounds like the images are not deployed.

If the certifications of ssl was not selected, the filebrowser service can be setup in omv webui, but in the fact it doesn't work. Still no containers.

lyj0309 · 30. Oktober 2022

same issue

Code

root@nas:~# omv-salt deploy run filebrowser
debian:
----------
          ID: create_filebrowser_app_container_systemd_unit_file
    Function: file.managed
        Name: /etc/systemd/system/container-filebrowser-app.service
      Result: True
     Comment: File /etc/systemd/system/container-filebrowser-app.service is in the correct state
     Started: 21:21:10.506139
    Duration: 295.459 ms
     Changes:   
----------
          ID: create_filebrowser_pod_systemd_unit_file
    Function: file.managed
        Name: /etc/systemd/system/pod-filebrowser.service
      Result: True
     Comment: File /etc/systemd/system/pod-filebrowser.service is in the correct state
     Started: 21:21:10.802219
    Duration: 36.473 ms
     Changes:   
----------
          ID: filebrowser_pull_app_image
    Function: cmd.run
        Name: podman pull docker.io/filebrowser/filebrowser:latest
      Result: True
     Comment: unless condition is true
     Started: 21:21:10.841522
    Duration: 9780.092 ms
     Changes:   
----------
          ID: filebrowser_app_image_exists
    Function: cmd.run
        Name: podman image exists docker.io/filebrowser/filebrowser:latest
      Result: True
     Comment: Command "podman image exists docker.io/filebrowser/filebrowser:latest" run
     Started: 21:21:20.625855
    Duration: 250.828 ms
     Changes:   
              ----------
              pid:
                  75763
              retcode:
                  0
              stderr:
              stdout:
----------
          ID: create_filebrowser_database
    Function: file.managed
        Name: /var/lib/filebrowser/database.db
      Result: True
     Comment: File /var/lib/filebrowser/database.db exists with proper permissions. No changes made.
     Started: 21:21:20.877511
    Duration: 6.397 ms
     Changes:   
----------
          ID: configure_filebrowser
    Function: file.managed
        Name: /var/lib/filebrowser/filebrowser.json
      Result: True
     Comment: File /var/lib/filebrowser/filebrowser.json is in the correct state
     Started: 21:21:20.884331
    Duration: 35.152 ms
     Changes:   
----------
          ID: stop_filebrowser_proxy_service
    Function: service.dead
        Name: container-filebrowser-proxy
      Result: True
     Comment: The named service container-filebrowser-proxy is not available
     Started: 21:21:20.920085
    Duration: 87.665 ms
     Changes:   
----------
          ID: purge_filebrowser_proxy_container_caddyfile
    Function: file.absent
        Name: /var/lib/filebrowser/Caddyfile
      Result: True
     Comment: File /var/lib/filebrowser/Caddyfile is not present
     Started: 21:21:21.008654
    Duration: 3.082 ms
     Changes:   
----------
          ID: purge_filebrowser_proxy_container_systemd_unit_file
    Function: file.absent
        Name: /etc/systemd/system/container-filebrowser-proxy.service
      Result: True
     Comment: File /etc/systemd/system/container-filebrowser-proxy.service is not present     Started: 21:21:21.012373
    Duration: 3.475 ms
     Changes:   
----------
          ID: filebrowser_systemctl_daemon_reload
    Function: module.run
      Result: True
     Comment: service.systemctl_reload: True
     Started: 21:21:21.016310
    Duration: 1134.219 ms
     Changes:   
              ----------
              service.systemctl_reload:
                  True
----------
          ID: start_filebrowser_service
    Function: service.running
        Name: pod-filebrowser
      Result: False
     Comment: Job for pod-filebrowser.service failed because the control process exited with error code.
              See "systemctl status pod-filebrowser.service" and "journalctl -xeu pod-filebrowser.service" for details.
     Started: 21:21:22.157641
    Duration: 57113.35 ms
     Changes:   

Summary for debian
-------------
Succeeded: 10 (changed=2)
Failed:     1
-------------
Total states run:     11
Total run time:   68.746 s

Alles anzeigen

File Browser plugin error when enabling

Jetzt mitmachen!

Tags