Unable to log into web gui after update

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Unable to log into web gui after update

      Hi All

      I updated omv to 4.1.20-1 and since update I have not been able to log into OMV.

      I am presented with:

      OMV\Exception: Failed to read file '/var/cache/openmediavault/cache.omv\controlpanel\login_js.json' (size=0). in /usr/share/php/openmediavault/json/file.inc:207
      Stack trace:
      #0 /usr/share/php/openmediavault/json/file.inc(223): OMV\Json\File->getContents()
      #1 /usr/share/php/openmediavault/controlpanel/controlpanelabstract.inc(173): OMV\Json\File->read()
      #2 /var/www/openmediavault/index.php(46): OMV\ControlPanel\ControlPanelAbstract->render()
      #3 {main}

      I have accessed omv-firstaid and run command 'clear web control panel cache' and also reset browser cache however I am still presented with the above.
      I have also tried updating OMV through CLI however still no luck.

      Any advice would be appreciated.

      Many thanks

      PS All shares and dockers appear to be working ok and are accessible.
    • Thanks Ryecoaaron

      I tried the above however it did not appear to work. Once I ran omv-aptclean i did notice a few errors please see below:

      E: Failed to fetch packages.openmediavault.org/public/dists/arrakis/main/ binary-amd64/Packages Error writing to output file - write (28: No space left o n device) Error writing to file - write (28: No space left on device)
      E: Failed to fetch dl.bintray.com/openmediavault-plugin-developers/arrak is/dists/stretch/main/binary-amd64/Packages Write error - write (28: No space l eft on device)
      E: Failed to fetch ftp.uk.debian.org/debian/dists/stretch/main/source/Sou rces Error writing to output file - write (28: No space left on device) Error w riting to file - write (28: No space left on device)
      E: Failed to fetch security.debian.org/debian-security/dists/stretch/upda tes/non-free/source/Sources Error writing to output file - write (28: No space left on device) Error writing to file - write (28: No space left on device)
      E: Failed to fetch ftp.uk.debian.org/debian/dists/stretch-updates/non-fre e/source/Sources Error writing to output file - write (28: No space left on dev ice) Error writing to file - write (28: No space left on device)
      E: Failed to fetch dl.bintray.com/openmediavault-plugin-developers/arrak is-docker/dists/stretch/main/binary-amd64/Packages Write error - write (28: No space left on device)
      E: Failed to fetch openmediavault.github.io/packages/dists/arrakis/main/ binary-amd64/Packages Write error - write (28: No space left on device)
      E: Failed to fetch httpredir.debian.org/debian/dists/stretch-backports/ma in/binary-amd64/Packages Error writing to output file - write (28: No space lef t on device) Error writing to file - write (28: No space left on device)
      E: Failed to fetch download.docker.com/linux/debian/dists/stretch/stable /binary-amd64/Packages Write error - write (28: No space left on device)
      E: Some index files failed to download. They have been ignored, or old ones used instead.
      W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/openmediavault.list:1 and /etc/apt/sources.list.d/openme diavault.list:4
      W: Target Packages (main/binary-all/Packages) is configured multiple times in /e tc/apt/sources.list.d/openmediavault.list:1 and /etc/apt/sources.list.d/openmedi avault.list:4
      W: Target Translations (main/i18n/Translation-en) is configured multiple times i n /etc/apt/sources.list.d/openmediavault.list:1 and /etc/apt/sources.list.d/open mediavault.list:4

      Is it possible the boot disk is full?
    • andyw wrote:

      Thanks Ryecoaaron

      I tried the above however it did not appear to work. Once I ran omv-aptclean i did notice a few errors please see below:

      E: Failed to fetch packages.openmediavault.org/public/dists/arrakis/main/ binary-amd64/Packages Error writing to output file - write (28: No space left o n device) Error writing to file - write (28: No space left on device)
      E: Failed to fetch dl.bintray.com/openmediavault-plugin-developers/arrak is/dists/stretch/main/binary-amd64/Packages Write error - write (28: No space l eft on device)
      E: Failed to fetch ftp.uk.debian.org/debian/dists/stretch/main/source/Sou rces Error writing to output file - write (28: No space left on device) Error w riting to file - write (28: No space left on device)
      E: Failed to fetch security.debian.org/debian-security/dists/stretch/upda tes/non-free/source/Sources Error writing to output file - write (28: No space left on device) Error writing to file - write (28: No space left on device)
      E: Failed to fetch ftp.uk.debian.org/debian/dists/stretch-updates/non-fre e/source/Sources Error writing to output file - write (28: No space left on dev ice) Error writing to file - write (28: No space left on device)
      E: Failed to fetch dl.bintray.com/openmediavault-plugin-developers/arrak is-docker/dists/stretch/main/binary-amd64/Packages Write error - write (28: No space left on device)
      E: Failed to fetch openmediavault.github.io/packages/dists/arrakis/main/ binary-amd64/Packages Write error - write (28: No space left on device)
      E: Failed to fetch httpredir.debian.org/debian/dists/stretch-backports/ma in/binary-amd64/Packages Error writing to output file - write (28: No space lef t on device) Error writing to file - write (28: No space left on device)
      E: Failed to fetch download.docker.com/linux/debian/dists/stretch/stable /binary-amd64/Packages Write error - write (28: No space left on device)
      E: Some index files failed to download. They have been ignored, or old ones used instead.
      W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/openmediavault.list:1 and /etc/apt/sources.list.d/openme diavault.list:4
      W: Target Packages (main/binary-all/Packages) is configured multiple times in /e tc/apt/sources.list.d/openmediavault.list:1 and /etc/apt/sources.list.d/openmedi avault.list:4
      W: Target Translations (main/i18n/Translation-en) is configured multiple times i n /etc/apt/sources.list.d/openmediavault.list:1 and /etc/apt/sources.list.d/open mediavault.list:4

      Is it possible the boot disk is full?
      Yes, that's what the error message is telling you.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Is there a way I can find what is using the disk space? I have logged in via winscp and can't find the offending file.

      root@lh-omv-nas:~# df -h
      Filesystem Size Used Avail Use% Mounted on
      udev 3.9G 0 3.9G 0% /dev
      tmpfs 794M 9.4M 784M 2% /run
      /dev/sdb1 110G 109G 0 100% /
      tmpfs 3.9G 0 3.9G 0% /dev/shm
      tmpfs 5.0M 0 5.0M 0% /run/lock
      tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
      tmpfs 3.9G 0 3.9G 0% /tmp
      /dev/sdc1 2.8T 12G 2.8T 1% /srv/dev-disk-by-label-Nextcloud
      /dev/sda1 2.8T 208G 2.6T 8% /srv/dev-disk-by-label-Docker
      /dev/sde1 7.3T 234G 7.1T 4% /srv/dev-disk-by-label-Rsnapshot
      //192.168.10.246/RemoteBackup 7.3T 374G 7.0T 6% /srv/2b1385da-c097-4af7-8d5f-83da773d4b29
      overlay 110G 109G 0 100% /var/lib/docker/overlay2/e805aba40a5e232738435f858fb202611413895ff4a569859c808f6c2cc644f7/merged
      overlay 110G 109G 0 100% /var/lib/docker/overlay2/1bb93d795d93790555cade4c27f2b28765673b594ba15e4d5b7786044f450e4a/merged
      overlay 110G 109G 0 100% /var/lib/docker/overlay2/dacfcb5422d6922a081bdf59ff3c5807375859a408da7be74762430cb28ee1a9/merged
      overlay 110G 109G 0 100% /var/lib/docker/overlay2/3be85ec845f52f468981c6ee1a74cba1beeef84813ffb100bd44a712d2dcb53e/merged
      overlay 110G 109G 0 100% /var/lib/docker/overlay2/28f5e6285cb6404702a61090a5f75eb3a05798888a2aa5d514e08f36a3a7dc1b/merged
      overlay 110G 109G 0 100% /var/lib/docker/overlay2/b19b2003fb4af050aef7d83b3377c9a98bb966f96c7118676b25de3e863eac65/merged
      overlay 110G 109G 0 100% /var/lib/docker/overlay2/33b3d671e34abc938e64383c4007b5cf38c8781811b427a88f14bba0ab83d2d2/merged
      shm 64M 0 64M 0% /var/lib/docker/containers/5a8410a44e40c83d085bb8f81f0f0d86d93c434e3cf048862249c37d74a75103/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/c5b1c11399dcbf41804aa98c685ea3c6ae17cdee314b0c4ca642449bb9be60e7/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/2f2cf7e436379d5893303f9b779f1ce2949f6e75b8db6bfbaada3046dc87fb17/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/00b509b0ec635450528452144ff091b9867e53d2e42029fe461485a58be9fb43/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/071aff54b9075a0af3a6980d10d0e3a0699eb61869341bdac7a5f61713e20ae8/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/f04dfe06d693b0a67796294f791402aec59b3696b72e5ced9027d2c0725d06c6/mounts/shm
      shm 64M 8.0K 64M 1% /var/lib/docker/containers/07e57b25127c4860884e2d84b5558732bccb6452c29caa27fb6c6b364e6e0e85/mounts/shm
      overlay 110G 109G 0 100% /var/lib/docker/overlay2/e0595ffea34c748296043761a2424a712c24450d1ed9258967f3ad64445e5947/merged
      shm 64M 0 64M 0% /var/lib/docker/containers/35f81b915c9e6d75ba42f56510305d34d564b71f3d71200e3f925d5c2d31b2d8/mounts/shm

      Thank you for your assistance.

      Andy

      Post by andyw ().

      This post was deleted by ryecoaaron: dupe ().
    • Hi KM0201 thanks for you suggestion.

      I do have my containers on the boot drive however the default path '/var/lib/docker ' only appears to be 5.36GB and not the 110GB available space. Is there a way i can just find out what is using the space on 'sdb1'?

      Thanks in advance.
    • The output of docker system df is:

      root@lh-omv-nas:/# docker system df
      TYPE TOTAL ACTIVE SIZE RECLAIMABLE
      Images 14 8 2.423GB 1.225GB (50%)
      Containers 8 8 39.11MB 0B (0%)
      Local Volumes 0 0 0B 0B
      Build Cache 0 0 0B 0B

      What is really strange the file e805aba40a5e232738435f858fb202611413895ff4a569859c808f6c2cc644f7 is no longer present in /var/lib/docker/overlay2/. If that is of any help.
    • Thanks geaves

      It freed up 968.6MB however after trying df -h after prune the output still shows:

      root@lh-omv-nas:~# df -h
      Filesystem Size Used Avail Use% Mounted on
      udev 3.9G 0 3.9G 0% /dev
      tmpfs 794M 9.3M 784M 2% /run
      /dev/sdb1 110G 108G 0 100% /
      tmpfs 3.9G 0 3.9G 0% /dev/shm
      tmpfs 5.0M 0 5.0M 0% /run/lock
      tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
      tmpfs 3.9G 0 3.9G 0% /tmp
      /dev/sdc1 2.8T 12G 2.8T 1% /srv/dev-disk-by-label-Nextcloud
      /dev/sde1 7.3T 234G 7.1T 4% /srv/dev-disk-by-label-Rsnapshot
      /dev/sda1 2.8T 208G 2.6T 8% /srv/dev-disk-by-label-Docker
      //192.168.10.246/RemoteBackup 7.3T 142G 7.2T 2% /srv/2b1385da-c097-4af7-8d5f-83da773d4b29
      overlay 110G 108G 0 100% /var/lib/docker/overlay2/1bb93d795d93790555cade4c27f2b28765673b594ba15e4d5b7786044f450e4a/merged
      overlay 110G 108G 0 100% /var/lib/docker/overlay2/3be85ec845f52f468981c6ee1a74cba1beeef84813ffb100bd44a712d2dcb53e/merged
      overlay 110G 108G 0 100% /var/lib/docker/overlay2/b19b2003fb4af050aef7d83b3377c9a98bb966f96c7118676b25de3e863eac65/merged
      overlay 110G 108G 0 100% /var/lib/docker/overlay2/28f5e6285cb6404702a61090a5f75eb3a05798888a2aa5d514e08f36a3a7dc1b/merged
      overlay 110G 108G 0 100% /var/lib/docker/overlay2/33b3d671e34abc938e64383c4007b5cf38c8781811b427a88f14bba0ab83d2d2/merged
      overlay 110G 108G 0 100% /var/lib/docker/overlay2/dacfcb5422d6922a081bdf59ff3c5807375859a408da7be74762430cb28ee1a9/merged
      overlay 110G 108G 0 100% /var/lib/docker/overlay2/e809c9714f54e3136778096df01c667f76f5656371a4a7a8fc6b7de13f33c8c1/merged
      overlay 110G 108G 0 100% /var/lib/docker/overlay2/e0595ffea34c748296043761a2424a712c24450d1ed9258967f3ad64445e5947/merged
      shm 64M 0 64M 0% /var/lib/docker/containers/5a8410a44e40c83d085bb8f81f0f0d86d93c434e3cf048862249c37d74a75103/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/00b509b0ec635450528452144ff091b9867e53d2e42029fe461485a58be9fb43/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/c5b1c11399dcbf41804aa98c685ea3c6ae17cdee314b0c4ca642449bb9be60e7/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/04024178e37ca241a59caaf0bf200454ebe8e665ceb845631c44509ec847ecea/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/f04dfe06d693b0a67796294f791402aec59b3696b72e5ced9027d2c0725d06c6/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/071aff54b9075a0af3a6980d10d0e3a0699eb61869341bdac7a5f61713e20ae8/mounts/shm
      shm 64M 8.0K 64M 1% /var/lib/docker/containers/07e57b25127c4860884e2d84b5558732bccb6452c29caa27fb6c6b364e6e0e85/mounts/shm
      shm 64M 0 64M 0% /var/lib/docker/containers/35f81b915c9e6d75ba42f56510305d34d564b71f3d71200e3f925d5c2d31b2d8/mounts/shm
    • Even more indicative that is the problem....

      /var/lib/docker/overlay2/1bb93d795d93790555cade4c27f2b28765673b594ba15e4d5b7786044f450e4a/merged
      overlay 110G 108G 0 100%

      You cleared approx. 1gig, and now it's showing 108gigs instead of 109gig as it did originally
      Air Conditioners are a lot like PC's... They work great until you open Windows.