July 4, 20242 yr I got a panicked call from my wife after our plex server was "not found." I took a look and saw all of my docker containers were stopped (even though they are set to auto start). I didn't stop them. I don't run the backup plugin, so now I need some guidance as to where I should look next to figure out why they all stopped and didn't start back up again. Pointers?
July 4, 20242 yr Community Expert You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.
July 4, 20242 yr Community Expert Could not spot anything in the diagnostics to suggest why docker containers should have been shutdown. BTW: You seem to have scheduled parity checks set to run once a week? That is far more frequently than most people go for. Monthly (or longer) intervals are far more common.
July 6, 20241 yr Dockers stopped starting All was well and then when I woke up - Docker Service failed to start. Attached Diagnostics. I have appdata backups and such, but hopefully that is not needed. (The fact that unraid can see all my drives is a persistent problem and not the cause of the docker issue.) Thanks in advance galaxy-diagnostics-20240706-1154.zip Edited July 6, 20241 yr by Profezor extra info
July 6, 20241 yr Community Expert Jul 6 07:34:26 Galaxy kernel: ata9: found unknown device (class 0) Jul 6 07:34:26 Galaxy kernel: ata9: SATA link down (SStatus 0 SControl 310) Jul 6 07:34:26 Galaxy kernel: ata9: limiting SATA link speed to 1.5 Gbps Jul 6 07:34:26 Galaxy kernel: ata10: found unknown device (class 0) Jul 6 07:34:26 Galaxy kernel: ata10: SATA link down (SStatus 0 SControl 310) Jul 6 07:34:26 Galaxy kernel: ata10: limiting SATA link speed to 1.5 Gbps Log is being being spammed with errors like the above, do you know which devices are these? They are not identified in the diags, possibly not really linking.
July 6, 20241 yr Thanks. There is a problem seeing all the drives I have installed, but this has not been a problem with the docker, only with my storage. So unfortunately, this is not teh current docker problem.
July 6, 20241 yr Community Expert 32 minutes ago, Profezor said: So unfortunately, this is not teh current docker problem. Yeah, but because of all the log spam, we can't see what is the docker problem, you can disconnect those disks and post new diags after array start.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.