Web GUI Login Loop Issue

Hey everyone,

I am a bit of a novice to omv and am at a loss at what is happening or happened. I turned on my main windows desktop and tried to login to the web gui and was thrown into a login loop. I tried everything from resetting Firefox to default settings and downloading Chromium but I still could not get passed the login screen. I have two users (both mine) and both of them made no difference. I can ssh into the system and when I tried everything I found online (sudo upgrade/update, firstaid and restarting nginx) nothing worked. I fear that I have to reinstall the OS but want to kick that can down as far as possible down the road. If anyone can lend a hand that would be greatly appreciated. I only have Photoprism setup and samba for my windows machine setup so I don't know what could have gone wrong.

Quote from Soma

Either your OS is full or you are not using the "admin" user.

df -h

Woah okay I checked using that command and I have no idea how that happened, and thank you for the help

This is what the output is, how do you recommend I fix this?

Filesystem      Size  Used Avail Use% Mounted on
udev             12G     0   12G   0% /dev
tmpfs           2.4G  3.0M  2.4G   1% /run
/dev/nvme0n1p2  233G  229G     0 100% /
tmpfs            12G   84K   12G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/nvme0n1p1  511M  152K  511M   1% /boot/efi
tmpfs            12G     0   12G   0% /tmp
/dev/md1        1.9T   44G  1.8T   3% /srv/dev-disk-by-uuid-f75e94aa-d896-4ba3-a7bc-ef7a7344c311
/dev/md2        931G  6.6G  925G   1% /srv/dev-disk-by-uuid-93317f76-7d12-47ca-9687-e07f9197f016
shm              63M     0   63M   0% /var/lib/containers/storage/overlay-containers/f0fa09fd889bc19aa8f34bdd59a1989fa6eec3debe4368cc4b5ba01f24592d02/userdata/shm
overlay         233G  229G     0 100% /var/lib/containers/storage/overlay/3f17a3afaad2c146d64522624459e24621405654d415394b5a03a5c293fe5a05/merged
overlay         233G  229G     0 100% /var/lib/containers/storage/overlay/cd0c1ad2401496a0601c05af2d3f86b14bf8af26e6c6b21ba4a5ee80b9aede1f/merged
shm              63M     0   63M   0% /var/lib/containers/storage/overlay-containers/c3011f7f835271d5b912b5781b061278268caa49a9505839dc239a563e5ad22d/userdata/shm
overlay         233G  229G     0 100% /var/lib/containers/storage/overlay/4e507ff4065187c4414f2d4916bb41268aa0e29829b1a69123329b857d21469d/merged
overlay         233G  229G     0 100% /var/lib/containers/storage/overlay/156a58c14311ef1e8e585d31b7b11c2fd48a83cd99ea57068010187ca147405f/merged
/dev/md0        466G   85G  370G  19% /srv/dev-disk-by-uuid-cea46171-cde3-4824-84c0-defdc2b3f272
overlay         233G  229G     0 100% /var/lib/containers/storage/overlay/805c6456bea6b47cd9967f5a66f9cf4c3ba85d14f6f333d4a237f7bd3fbaed96/merged
overlay         233G  229G     0 100% /var/lib/containers/storage/overlay/bf9d5accc4a42d721daefb158a017554ee9768d808ba436b1a7575170ceb9090/merged
overlay         233G  229G     0 100% /var/lib/containers/storage/overlay/e8694f5f936a3eafd3d5ac7361d871e1464d503b3a10c365e8d53d8f2bd8ee0d/merged

Quote from chente

You can follow the guide linked in post 3.

It seems that the problem has been caused by docker.

You will have to find out what exactly has filled the drive. If it is a system with a lot of time, it is possible that they are only unused images. You could run docker system prune -a in CLI and see the result. If that allows you to access the GUI it might be easier from there to purge files you don't need.

It would be a good idea to make docker independent of the operating system to prevent this from happening to you again.

I am going through what macom linked to and it so far hasn't changed. I had some log files that were above 100 gb for some dumb reason and i used rm to clear out everything. Also trying the command "docker system prune -a" gave me this output? I quickly reinstalled docker and it still gave me this output. I will wear my dunce cap later but what and how lol? and thank you for the help.

-bash: docker: command not found

Quote from chente

The output should have been like this:

Code

~# docker system prune -a
WARNING! This will remove:
  - all stopped containers
  - all networks not used by at least one container
  - all images without at least one container associated to them
  - all build cache

Are you sure you want to continue? [y/N]

I'm guessing you've removed something you shouldn't have removed and uninstalled docker, or at least corrupted it.

In the GUI go to Services>Compose>Settings and Press the Reinstall Docker button. That should fix it.

Heh yea I think maybe I did and after a few reboots and praying I think it worked? I went around and deleting logs and anything I could find that would be temporary. I can log in now and but is there a way I can avoid this problem in the future? This feels like I will face this issue again down the road.

Quote from chente

Yeah.

Install docker on a separate drive. You have 3 options at a glance:

1. Install OMV on a USB stick and use that SSD drive for docker. Ideal.

2. Partition the SSD. But to do this you will have to install debian by partitioning and then OMV on the debian partition (it is the easiest way, there are others).

3. Install docker on a data drive that allows it and leave the SSD for OMV.

Hmm I have a spare 250GB Samsung SSD laying around and could use that. You mind telling me how I could move docker to it and keep omv on the internal SSD?