Help Docker’s will not start on reboot

[Maticks]

Probably best to describe why i rebooted first.

I woke up this morning to my medusa docker not responding on its webui.

I checked my other dockers they were working, i tried to restart medusa docker and it wouldn’t restart.

 

i did a quick check in dashboard and noticed that the flash docker log was at 100% i have never seen it more than 20% full ever.

My Cache drive was at around 30% full, none of my hard drives are full either.

 

I decided to reboot the box so i restarted it, my vm’s took a while but finally booted back up but dockers never started.

When i click on the dockers tab, it says the docker service failed to start.. what do i do? i haven’t had this issue before.

 

Can anyone help point me in the right direction.

 

[John_M]

33 minutes ago, Maticks said:

Can anyone help point me in the right direction.

 

Tools -> Diagnostics. Post the zip file.

 

[Maticks]

As attached

vault-diagnostics-20180411-0841.zip

[Maticks]

i am assuming its this.

but i have a heaps of space...

 

ime="2018-04-11T07:12:08+10:00" level=error msg="garbage collection failed" error="write /var/lib/docker/containerd/daemon/io.containerd.metadata.v1.bolt/meta.db: no space left on device" module="containerd/io.containerd.gc.v1.scheduler"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x8ae367]

 

[Maticks]

just increased my docker image size to 30G so i can start it.

looks to be working...

[Maticks]

well found the 6.1GB log file with the same entry.

bit weird though..

 

{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445811136Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445815478Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.44582013Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.4458232Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445825713Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445829377Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445833706Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445836275Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445838856Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445843206Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445847761Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445850568Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445854268Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445858084Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445860761Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445865003Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445868597Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445871172Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445873674Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445876963Z"}
{"log":"Found pihole-FTL process with PID 534 (my PID 625) - killing it ...\n","stream":"stdout","time":"2018-04-10T23:06:50.445885869Z"}

[John_M]

I don't use pihole. Is it misconfigured?

[Maticks]

i think the docker got an update last night with some issues. after dropping the log file and restarting the docker it still went over and created endless log errors with the wrong pid error.

so i forced an update of the docker which had two updates. that fixed it.

the log output is now fixed. maybe someone made a mistake and pushed an update. hrmm i think ill set my docker auto update to the weekends from now on.

 

[John_M]

I don't like auto updates, myself. I like to be informed that updates are available but I prefer to install them manually after I've read the release notes.