OMV Web login fails

    • OMV 4.x

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

    • OMV Web login fails

      Hello,

      the log in to the webinterface is failing. On the first time that happens wars the / spammed by Docker, so i'm deleted all containers and set it to another SSD (not / ). that seems to be fine and im going to recreate all my docker containers. this hapens yersterday, today is the same problem but on / is enougy space:

      Source Code

      1. root@OMV:/# du -hxd1
      2. 91M ./boot
      3. 4,0K ./export
      4. 39G ./192.168.178.35
      5. 4,0K ./home
      6. 815M ./var
      7. 16K ./opt
      8. 16K ./lost+found
      9. 24K ./srv
      10. 4,0K ./lib64
      11. 13M ./bin
      12. 15M ./sbin
      13. 4,0K ./sharedfolders
      14. 8,0K ./media
      15. 4,0K ./mnt
      16. 7,8M ./etc
      17. 702M ./lib
      18. 1,5G ./usr
      19. 3,5G ./root
      20. 45G .
      Display All
      Is ist docker again? By the way has somebody an comand to clean up the Docker automatically?
    • Your output is not helpful because we don't know the size of the drive. df -h would be helpful. That said, it isn't docker since images are stored in /var/lib/docker. Your /root/ directory has the most spaced used. What did you fill /root/ with??
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Ok it is an 500 ssd with ca 4 Gb for / . On the first it wars Docker that it fill up my / so that i'm set it up to another SSD.

      Source Code

      1. root@OMV:~# du -hxd1
      2. 3,5G ./192.168.178.35
      3. 44K ./.config
      4. 12K ./.ssh
      5. 3,5G .
      the /192.168.178.35 is an remote mount. Iḿ not understanding why it is blow up my root ?(

      Any ideas what is wrong?
    • indigo wrote:

      the /192.168.178.35 is an remote mount. Iḿ not understanding why it is blow up my root
      Because you are using the -x flag on du, it would look at disk use on a different mount point. So, the 192.168.178.35 isn't a mount point. It is a directory with files in it. Something is wrong with your remote mount.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • indigo wrote:

      can i'm delet it over ssh?
      Assuming you don't want anything in that directory, yes. rm -rfv /root/192.168.178.35

      I would also give yourself more space in the OS partition if you are going to use docker. 4GB is enough without docker but...
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • indigo wrote:

      I have docker outsorced to another ssd in the pluginsettings, is that enough?
      probably

      indigo wrote:

      How i can automatically clean up my docker?
      Not sure. Maybe watchtower does that? I don't use docker very often.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • indigo wrote:

      Any idea what is happend there and why is this folder created?
      Not really. I would guess an rsync or rsnapshot job that was trying to write to something that wasn't mounted. None of the plugins would write to /root/. So, I can only guess it is something you wrote.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Your setup is wrong and is causing the issue. You have the IP address of the remote server but no path. Look at the notes below that field for the proper format.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Oh yes, thaks for that. I have corrected but i some werid messeage:


      please wait, syncing </srv/dev-disk-by-label-cc/kona/> to <niko@192.168.178.35:kona> ...

      Host key verification failed.
      rsync: connection unexpectedly closed (0 bytes received so far) [sender]
      rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]


      The synchronisation has completed successfully.

      Well for me it is not succesfully... Niko is the user and he has full acess to the folder, so what goes here wrong?

      Post by macom ().

      This post was deleted by the author themselves ().
    • indigo wrote:

      so what goes here wrong?
      No idea since I know nothing about the remote server. Do you have rsync listening on that server? If not, ssh keys need to be setup. There are guides for that.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!