OMV Web login fails

indigo · 7. Februar 2019

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:

Code

root@OMV:/# du -hxd1
91M	./boot
4,0K	./export
39G	./192.168.178.35
4,0K	./home
815M	./var
16K	./opt
16K	./lost+found
24K	./srv
4,0K	./lib64
13M	./bin
15M	./sbin
4,0K	./sharedfolders
8,0K	./media
4,0K	./mnt
7,8M	./etc
702M	./lib
1,5G	./usr
3,5G	./root
45G	.

Alles anzeigen

Is ist docker again? By the way has somebody an comand to clean up the Docker automatically?

ryecoaaron · 7. Februar 2019

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??

indigo · 7. Februar 2019

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.

Code

root@OMV:~# du -hxd1
3,5G	./192.168.178.35
44K	./.config
12K	./.ssh
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?

ryecoaaron · 7. Februar 2019

Zitat von indigo

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.

indigo · 7. Februar 2019

can i'm delet it over ssh?

It seems to be an folder, stull like this i have syced over rsync but i have no idea why it is on this place.

ryecoaaron · 7. Februar 2019

Zitat von indigo

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

indigo · 7. Februar 2019

Thanks that works. I have docker outsorced to another ssd in the pluginsettings, is that enough?

How i can automatically clean up my docker?

ryecoaaron · 7. Februar 2019

Zitat von indigo

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

probably

Zitat von indigo

How i can automatically clean up my docker?

Not sure. Maybe watchtower does that? I don't use docker very often.

indigo · 7. Februar 2019

How ever thanks for help. Any idea what is happend there and why is this folder created?

ryecoaaron · 8. Februar 2019

Zitat von indigo

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.

indigo · 9. Februar 2019

It has something to to with am Rsync job. I have one job that has to push all the stuff inside one folder to diskstation. How ewer the folder is again there, with the same problem again. So i have delete it again to log in to the webinterface.

Here is an screanshot from the Rsync job.

ryecoaaron · 9. Februar 2019

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.

indigo · 10. Februar 2019

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?

ryecoaaron · 11. Februar 2019

Zitat von indigo

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.

Jetzt mitmachen!