December 16, 20241 yr Unraid ver 6.12.14 Hardware: Intel® Core™ i3-8100 Gigabyte Technology Co., Ltd. H310M S2H GSM 32 GiB DDR4 Corsair 650 W Power Supply Samsung BAR Plus 64 GB Hard Drives: 1 x HGST Ultrastar DC HC520 12TB SATA 6Gb 256MB 3.5" Enterprise HDD- HUH721212ALE601 2 x HGST HUH728080ALE600 8TB 7200 RPM 128MB Cache SATA 6.0Gb/s LFF Drive Summary: Unraid crash is causing my web gui and my services to be inaccessible. Details: I can ping the server from another machine and it gets ping but the I cannot access the gui and all my docker containers are unreachable. I connected a physical display and keyboard to the unraid server and accessing my root user but I got time out when just entering the user name. I have had this issue for a few months now inconsistently. I am not sure what exactly is causing it. The few times before were during use and the most recent one was last night unattented. My uptime kuma (which is running on another machine) notified me that my containers were timed out. As far I have know, I do not have any scheduled at around the time of the crash. The crash seems to have happened at Dec 16 02:26:23 in the syslog I have attached. Diagnostics zip is also attached. Can someone please hel pme diagnose what the issue is? syslog-192.168.50.231.log plutus-diagnostics-20241216-1258.zip Edited December 16, 20241 yr by KnightElm Added unraid version and hardware details
December 16, 20241 yr Community Expert There appears to be a container constantly restarting, check their uptimes.
December 16, 20241 yr Author I will check. The first one to break at least according to the uptime kuma is navidrome which just had some reserve proxy errors. I fixed them. Not sure why it would crsah. Is there another way to check what might have crashed?
December 17, 20241 yr Community Expert Post a new syslog after fixing the container issues, but a rogue container can crash the server.
December 17, 20241 yr Author plutus-diagnostics-20241217-1828.zipsyslog-192.168.50.231.log Here's the latest syslog and diagnositics!
December 18, 20241 yr Community Expert What time was the last crash? Also recommend disabling mover logging, it's spamming the log.
December 18, 20241 yr Author It was the same as in my original post on December 16th at around 02:30 am. I had to force shut it down when i woke up at around 07:00. I will disable mover logging. Would you like another syslog?
December 18, 20241 yr Community Expert 4 minutes ago, KnightElm said: December 16th at around 02:30 am There are some ngixn errors logged at that time, try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again, and retest.
December 18, 20241 yr Author I will try that but the only issue with retesting is that the crash is not consistent. It only happens very rarely. It hasn't happened again since December 16th. I'm not sure if I can recreate it.
December 31, 20241 yr Author So I have updated my mover tuner plugin and also changed some of the schedules. So far it seems to be okay.
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.