HELP! Cannot Log Into Web GUI

  • I've seen a similar problem on multiple threads here. The most recent one being here.

    Cannot login to Web interface


    • We can cut to the chase and basically say I've tried everything these other users tried. Except mine didn't work.

      The only thing I can think of that might have made some difference was to uncomment a piece of code in the config file to prevent my laptop (don't laugh) from suspending when the lid is shut.

      I cannot login with any other user name.
      I did change the password for the admin account with no effect. There are no errors on login unless I deliberately do use a wrong password.
    • SSH works just fine.
    • I tried omv-firstaid:
      • I used the rescue option with no effect. Clearing the login counter says "No locked/banned users or candidates exist."
      • I cleared browser cache. I even used a completely different browser on a different device.
      • I tried changing the port number in workbench configuration. No change.
      • I reconfigured the time zone just in case since earlier cases referred to that. (Time zones with apache server.) Didn't work. Even restarted the server.
      • I don't have a configuration backup to restore (But I will after I fix this problem!!!!)
      • I cleared the local upload package repository.
      • "Configuration status file is valid."
      • "ALL RRD database files are valid."

    Here's a couple of other things that people diagnosed.

    root@casavault:~# df -h

    Filesystem Size Used Avail Use% Mounted on

    udev 1.9G 0 1.9G 0% /dev

    tmpfs 383M 3.8M 380M 1% /run

    /dev/sda2 227G 216G 0 100% /

    tmpfs 1.9G 88K 1.9G 1% /dev/shm

    tmpfs 5.0M 4.0K 5.0M 1% /run/lock

    tmpfs 1.9G 0 1.9G 0% /tmp

    /dev/sda1 511M 296K 511M 1% /boot/efi

    /dev/sdd1 1.8T 289G 1.6T 16% /srv/dev-disk-by-uuid-e906d41d-fe09-4b24-847f-fa31925ccca0 /dev/sdb1 458G 72K 458G 1% /srv/dev-disk-by-uuid-fc9bc854-54bd-414d-b3a6-94d20f5f3be8

    /dev/sdc1 3.7T 3.4T 256G 94% /srv/dev-disk-by-uuid-62C4AC07C4ABDC13 /dev/mmcblk0p1 57G 48K 57G 1% /srv/dev-disk-by-uuid-c5e32d82-0211-4bad-962e-bd032c34f5de

    //192.168.1.6/ADMIN$ 1.9T 1.6T 269G 86% /mnt/192.168.1.6/ADMIN$

    //192.168.1.6/C DRIVE 1.9T 1.6T 269G 86% /mnt/192.168.1.6/C DRIVE

    //192.168.1.6/C$ 1.9T 1.6T 269G 86% /mnt/192.168.1.6/C$

    //192.168.1.6/CONTENT 1.9T 1.6T 269G 86% /mnt/192.168.1.6/CONTENT //192.168.1.6/O$ 13T 13T 302G 98% /mnt/192.168.1.6/O$

    //192.168.1.6/print$ 1.9T 1.6T 269G 86% /mnt/192.168.1.6/print$

    //192.168.1.6/S$ 3.7T 3.0T 695G 82% /mnt/192.168.1.6/S$ //192.168.1.6/SHARE 3.7T 3.0T 695G 82% /mnt/192.168.1.6/SHARE //192.168.1.6/Users 1.9T 1.6T 269G 86% /mnt/192.168.1.6/Users

    //192.168.1.6/W$ 4.6T 3.7T 887G 81% /mnt/192.168.1.6/W$

    //192.168.1.6/WORK 4.6T 3.7T 887G 81% /mnt/192.168.1.6/WORK

    synactics_google_drive_1692186339: 15G -16E 16E - /mnt/synactics_google_drive_1692186339

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/12aa88f8e32e59ce6358d9dcc1168a1c0970416053975cd8120243348acc316e/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/d1dbf9530940079a80804b1442450647d855f9a1549aef970a87248af00eff13/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/1adca721955316b9dd7c877d446ba002771552d8d51e5c6c0be6f343b7c8e16e/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/6882654bbbf848ad8e5159c3a88ec4e408f956becfb51f3c3e02a27a2299e57c/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/e0e2946959fb150620bd05d662bf7b7fbbbffdd03e3d739f81090b9c6b4a2b0c/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/c3865d6e92277573559157568388c480190e7d2a1bb1f7021212472e625215a4/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/3cad88ba94f7c78d4916c3d1969214b32aa8916b39bd0cef8b3e696e7bd7d7d1/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/d5bc2a449241ae185a1af55643d5ba818b623ca6604af0d9b7205c2624e127f5/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/061ebb8ccb6b836800be7abd90822421eb7ab297f4b82d8ec5b56a3f7f1a24ad/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/c7298be1264bded62e4e39efd7ed6a4c54afeb58460d7edb8e2a4c806a00dc52/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/58ad318095b6a086d235b0c91dd554a75ab5b05e31e0f2354e7a3450076267fd/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/d4fb865f99d09b432b5ff17c175b65bba8a82ae634bf710f380f261281b41ef5/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/8606f1efc5efd3be4c0f4d8ad07e8f7f07a68da386bdf7f316170a571fed9079/merged

    overlay 227G 216G 0 100% /var/lib/docker/overlay2/ed8968dff979ae800fdfb54ef48f5cb96d2a5de2f30f5af3321a76f037fef29f/merged

    tmpfs 383M 0 383M 0% /run/user/0


    • I looked at newer threads on this and tried this. "omv-salt deploy run nginx phpfpm". Again, after clearing cache and even trying a different browser, it didn't work. One thing DID change after this script was run. I was getting this error on the server's screen before. It has now gone away.
    Code
    Out of memory: Killed process 6137 (python3) total-vm:436096kB, anon-rss:79104KB, file-rss:okB, shmem-rss:OkB, UID:1000 pgtables:436kB com score edi


    • I tried this as well:
    • Application & plugin versions here:
  • chente

    Approved the thread.
    • Official Post

    /dev/sda2 227G 216G 0 100% /

    Never share your config.xml file like that, there is sensitive information inside. Edit your post and delete that file please, I tried to do it myself but I couldn't.


    Is your OMV system unit sda2? That unit is full. That could be the reason why you can't enter the GUI.

  • I appreciate the response. I've been off grid dealing with some in real life issues.

    Okay, so I guess the real question is:

    1) WHY is that disk completely full? How do I determine what is doing that and prevent it from happening in the future?

    2) What can I safely do to wipe out the unnecessary data (or even determine what that is?


    3) How do I keep this sucker stable? Because an unstable file and media server won't do the trick for me. I might just as well use windows 11 if I want that. (LOL_

    Thanks in advance.

  • It appears that you specified /var/lib/docker for the Docker storage location in Services | Compose | Settings | Docker | Docker storage.


    This location is on the root filesystem and doing so is a commonly made mistake that often leads to filling the filesystem. Use a directory on a data drive instead.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


  • That would make sense. Any idea out to change that setting without being able to get into the web GUI? Is there a config file for manual changes?

    • Official Post

    Any idea out to change that setting without being able to get into the web GUI? Is there a config file for manual changes?

    There is nothing similar, you should follow the guide that I linked to you in post 2 to make room on the system unit.

    If the problem is docker, you can also try to delete docker images that are not in use from the CLI.

  • The guides provided here were very helpful. My issue was I forgot to plugin a power cable for a backup HDD and a scheduled rsyncsnapshot job went to the system drive. So my new assumption is that the /srv location works like a symlink to the physical volumes - is that right? That would make sense for why data intended for another drive went to OS drive.

    NAS Spec 👇

  • The /srv/dev-disk-by-uuid-* location is a directory on your system drive that serves as a mountpoint for a disk.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


  • It appears that you specified /var/lib/docker for the Docker storage location in Services | Compose | Settings | Docker | Docker storage.


    This location is on the root filesystem and doing so is a commonly made mistake that often leads to filling the filesystem. Use a directory on a data drive instead.

    @"gderf"

    Would it make a sense to note that in OMV GUI (Service --> Compose --> Settings Docker Storage) ?. Is there way to "clean" original location in the system drive?. Can I just rm docker from /var/lib ?.

    Arch Linux, Linux Mint 22, FreeBSD KDE Plasma6

    OMV7 NAS 10GB Fiber, Fractal Design Define R5 Case, Kodi "Omega", pfSense Plus firewall/router

    Edited once, last by andrzejls ().

  • You can stop the docker service and delete the directory.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!