October 7, 20196 yr So I clicked on "Update All" under my dockers, and it hung trying to shutdown one of them, Netdata. So I tried opening a new webUI window and could no longer see any of my dockers. All of them are not responding. I tried using the WebUI to restart, didn't work. As in the machine won't reboot. I get a 504 error after some time. Tried restarting from the commandline, and it just hangs here and doesn't actually restart: root@Dataserver2:~# /sbin/reboot Broadcast message from root@Dataserver2 (pts/1) (Mon Oct 7 13:19:45 2019): The system is going down for reboot NOW! Are the machines finally taking over?
October 17, 20196 yr Author I've already had to pull the plug to get this to restart, but does no one have any idea what caused this?
October 17, 20196 yr First of all, I see a Python process that's segfaulting: Aug 20 10:06:25 Dataserver2 kernel: python[31677]: segfault at 6e6f68747988 ip 0000147723a127e8 sp 000014771b8cf098 error 6 in ld-musl-x86_64.so.1[147723a05000+46000] It seems to happen after autofan adjusts your sever fan speeds, so maybe it's related. Secondly, there's this: Aug 21 16:33:48 Dataserver2 nginx: 2019/08/21 16:33:48 [error] 4260#4260: *847010 user "root": password mismatch, client: 167.220.149.78, server: , request: "GET /Main HTTP/1.1", host: "turtlerr.com" Do you recognise the 167.220.149.78 address? You could be being attacked from outside if you have ports open to the Internet. Thirdly, more worrying attempts to connect, trying different user names: Aug 26 07:22:48 Dataserver2 nginx: 2019/08/26 07:22:48 [error] 4260#4260: *2792365 user "admin" was not found in "/etc/nginx/htpasswd", client: 23.225.205.151, server: , request: "GET /Main HTTP/1.1", host: "99.61.88.74", referrer: "http://99.61.88.74/" Aug 26 07:22:48 Dataserver2 nginx: 2019/08/26 07:22:48 [error] 4260#4260: *2792371 user "super" was not found in "/etc/nginx/htpasswd", client: 23.225.205.151, server: , request: "GET /Main HTTP/1.1", host: "99.61.88.74", referrer: "http://99.61.88.74/" A different IP address. Do you recognise it? These are repeated over and over, testing a variety of different usernames. This goes on for several days. You should close all ports and use a VPN instead. Fourthly, this: Oct 7 12:48:48 Dataserver2 kernel: BUG: unable to handle kernel paging request at 0000000000006111 Oct 7 12:48:48 Dataserver2 kernel: PGD 0 P4D 0 Oct 7 12:48:48 Dataserver2 kernel: Oops: 0000 [#1] SMP PTI Oct 7 12:48:48 Dataserver2 kernel: CPU: 21 PID: 11162 Comm: chown Tainted: P O 4.19.56-Unraid #1 Oct 7 12:48:48 Dataserver2 kernel: Hardware name: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F/X9SRE/X9SRE-3F/X9SRi/X9SRi-3F, BIOS 3.3 05/29/2018 A bug, a kernel oops and a call trace. It looks as though it tries to shut down when commanded to but doesn't make it: Oct 7 13:10:51 Dataserver2 shutdown[20380]: shutting down for system reboot Probably the system is too messed up by that time. My advice is to get it secured behind a firewall and update the OS to version 6.8.0-rc1, which has a much newer kernel. Update your plugins and apps too. I understand that there have been some dockerhub outages recently, affecting certain regions of the world.
October 17, 20196 yr Author Someone trying to log in from externally shouldn't stop the system from being shutdown. This is clearly a bug.
October 17, 20196 yr Author Well here's the problem, this has only happened once so I don't have a repro of this issue. If I update now and it never happens again, I have no idea if the update fixed it, or if it was something else that was just once in a million to repro. It'd be nice if more folks could look over these logs that have more familiarity with unRAIDs code and give input. But thank you for your help thus far! I really do appreciate it, John.
Archived
This topic is now archived and is closed to further replies.