March 17, 20251 yr My unraid ui becoems unresponsive after some time from a restart. I try to keep the page closed to not have an open tab on my browser too long which I know has caused issues in the past, but it's still having the issue. Any help would be appreciated. Thanks! andromeda-diagnostics-20250317-1155.zip
March 17, 20251 yr Community Expert Syslog is full of Nginx errors, try rebooting in safe mode, let the server run for an hour or so, and post new diags.
March 18, 20251 yr Author Here's the new diag. It's been about 20 mins but the UI is already unresponsive andromeda-diagnostics-20250317-1702.zip
March 18, 20251 yr Author Here is another 1 in safe mode, confirmed it was in safe mode too andromeda-diagnostics-20250318-1406.zip
March 19, 20251 yr Community Expert There appears to be a container constantly restarting, see if you can find out which by looking at their uptimes.
March 19, 20251 yr Author Hmm I'm looking through Unraid's dashboard on the containers and nothing is showing as restarted more than 12 hours ago (when I last rebooted). Is there something else I should check?
March 19, 20251 yr Author I've turned off many dockers proactively to just what I consider my core dockers. Logs seem much cleaner than before Mar 19 12:17:02 Andromeda emhttpd: read SMART /dev/sdd Mar 19 12:17:24 Andromeda emhttpd: read SMART /dev/sdb Mar 19 12:18:31 Andromeda nginx: 2025/03/19 12:18:31 [error] 27738#27738: MEMSTORE:00: tried adding WAITING chanhead 00000000008FD780 m/ Mar 19 12:18:31 Andromeda nginx: 2025/03/19 12:18:31 [error] 27738#27738: MEMSTORE:00: tried adding WAITING chanhead 00000000008FD780 m/ Mar 19 12:18:31 Andromeda nginx: 2025/03/19 12:18:31 [error] 27738#27738: MEMSTORE:00: tried adding WAITING chanhead 00000000008FD780 m/ Mar 19 12:19:09 Andromeda emhttpd: read SMART /dev/sde Mar 19 12:22:42 Andromeda emhttpd: error: publish, 172: Connection reset by peer (104): read Mar 19 12:23:15 Andromeda kernel: veth51f6bf9: renamed from eth0 Mar 19 12:23:15 Andromeda kernel: docker0: port 23(veth413a115) entered disabled state Mar 19 12:23:15 Andromeda kernel: docker0: port 23(veth413a115) entered disabled state Mar 19 12:23:15 Andromeda kernel: device veth413a115 left promiscuous mode Mar 19 12:23:15 Andromeda kernel: docker0: port 23(veth413a115) entered disabled state Mar 19 12:24:15 Andromeda kernel: br-fb0d039ca56f: port 20(vethb12b49c) entered disabled state Mar 19 12:24:15 Andromeda kernel: veth9f18505: renamed from eth0 Mar 19 12:24:15 Andromeda kernel: br-fb0d039ca56f: port 20(vethb12b49c) entered disabled state Mar 19 12:24:15 Andromeda kernel: device vethb12b49c left promiscuous mode Mar 19 12:24:15 Andromeda kernel: br-fb0d039ca56f: port 20(vethb12b49c) entered disabled state Mar 19 12:25:03 Andromeda kernel: docker0: port 2(veth3981603) entered disabled state Mar 19 12:25:03 Andromeda kernel: vethd6c5cef: renamed from eth0 Mar 19 12:25:03 Andromeda kernel: docker0: port 2(veth3981603) entered disabled state Mar 19 12:25:03 Andromeda kernel: device veth3981603 left promiscuous mode Mar 19 12:25:03 Andromeda kernel: docker0: port 2(veth3981603) entered disabled state Mar 19 12:28:26 Andromeda kernel: docker0: port 2(veth9b0ac81) entered blocking state Mar 19 12:28:26 Andromeda kernel: docker0: port 2(veth9b0ac81) entered disabled state Mar 19 12:28:26 Andromeda kernel: device veth9b0ac81 entered promiscuous mode Mar 19 12:28:29 Andromeda kernel: eth0: renamed from veth32e16d2 Mar 19 12:28:29 Andromeda kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9b0ac81: link becomes ready Mar 19 12:28:29 Andromeda kernel: docker0: port 2(veth9b0ac81) entered blocking state Mar 19 12:28:29 Andromeda kernel: docker0: port 2(veth9b0ac81) entered forwarding state Mar 19 13:36:15 Andromeda kernel: docker0: port 6(vethe484515) entered blocking state Mar 19 13:36:15 Andromeda kernel: docker0: port 6(vethe484515) entered disabled state Mar 19 13:36:15 Andromeda kernel: device vethe484515 entered promiscuous mode Mar 19 13:36:18 Andromeda kernel: eth0: renamed from vethc929149 Mar 19 13:36:18 Andromeda kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe484515: link becomes ready Mar 19 13:36:18 Andromeda kernel: docker0: port 6(vethe484515) entered blocking state Mar 19 13:36:18 Andromeda kernel: docker0: port 6(vethe484515) entered forwarding state Mar 19 13:36:57 Andromeda kernel: docker0: port 6(vethe484515) entered disabled state Mar 19 13:36:57 Andromeda kernel: vethc929149: renamed from eth0 Mar 19 13:36:58 Andromeda kernel: docker0: port 6(vethe484515) entered disabled state Mar 19 13:36:58 Andromeda kernel: device vethe484515 left promiscuous mode Mar 19 13:36:58 Andromeda kernel: docker0: port 6(vethe484515) entered disabled state Mar 19 13:38:04 Andromeda nginx: 2025/03/19 13:38:04 [alert] 13698#13698: worker process 13699 exited on signal 6 Mar 19 13:38:05 Andromeda nginx: 2025/03/19 13:38:05 [alert] 13698#13698: worker process 13707 exited on signal 6 Mar 19 13:40:10 Andromeda nginx: 2025/03/19 13:40:10 [alert] 21261#21261: worker process 21262 exited on signal 6 Mar 19 13:40:12 Andromeda nginx: 2025/03/19 13:40:12 [alert] 21261#21261: worker process 21286 exited on signal 6 Mar 19 13:40:13 Andromeda nginx: 2025/03/19 13:40:13 [alert] 21261#21261: worker process 21371 exited on signal 6 Mar 19 13:40:15 Andromeda nginx: 2025/03/19 13:40:15 [alert] 21261#21261: worker process 21408 exited on signal 6 Mar 19 13:42:15 Andromeda nginx: 2025/03/19 13:42:15 [alert] 28625#28625: worker process 28626 exited on signal 6 Mar 19 13:44:20 Andromeda nginx: 2025/03/19 13:44:20 [alert] 4713#4713: worker process 4716 exited on signal 6 Mar 19 13:44:22 Andromeda nginx: 2025/03/19 13:44:22 [alert] 4713#4713: worker process 4728 exited on signal 6 Mar 19 13:44:23 Andromeda nginx: 2025/03/19 13:44:23 [alert] 4713#4713: worker process 4772 exited on signal 6 Mar 19 13:44:25 Andromeda nginx: 2025/03/19 13:44:25 [alert] 4713#4713: worker process 4811 exited on signal 6 Mar 19 14:05:32 Andromeda emhttpd: spinning down /dev/sdd Mar 19 14:28:35 Andromeda emhttpd: spinning down /dev/sdb Mar 19 14:28:49 Andromeda emhttpd: spinning down /dev/sde Mar 19 14:33:46 Andromeda emhttpd: read SMART /dev/sdb Mar 19 14:42:50 Andromeda emhttpd: read SMART /dev/sde Mar 19 14:51:10 Andromeda nginx: 2025/03/19 14:51:10 [error] 10414#10414: MEMSTORE:00: tried adding WAITING chanhead 0000000000A2B400 m/ Any ideas what else to try to investigate
March 20, 20251 yr Community Expert 12 hours ago, ryphez said: Hmm I'm looking through Unraid's dashboard on the containers and nothing is showing as restarted more than 12 hours ago So was the GUI unresponsive or not in safe mode?
March 31, 20251 yr Community Expert One thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the docker containers.
May 21, 20251 yr Author On 3/31/2025 at 1:18 AM, JorgeB said:One thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the docker containers. Got caught up with other things, would you enable all dockers or start 1 by 1?
May 21, 20251 yr Community Expert Up to you, you can also enable half of them, and if there are still issues try the other half.
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.