April 1, 20233 yr Every now and then, the server will just lock up. No webgui, no video output if I connect a monitor directly to the server, no response to SSH requests, but the power is still on. Sometimes, if I catch the problem early, I can telnet into the server and send a reboot command (SSH does not work at this point). I posted about this in February, and was advised to disable C states and make sure my RAM was not overclocked, which I did at that point...but the problem persists. Diagnostics are attached. System is a Ryzen 3 3200G 32 gb RAM MSI B450 Gaming Pro Carbon AC I mostly use it for storage, but have 3 docker containers: UrBackup, DuckDNS, and Plex. I have 6 data drives and one parity drive, all are connected through a Dell H310 SAS HBA which has been flashed with IT firmware. Any idea what's going on? tower-diagnostics-20230401-1535.zip
April 3, 20233 yr Author Ok, I have set the syslog to mirror to flash, and will post it here next time it crashes.
May 17, 20233 yr Author It's been a while, I was hoping the problem had spontaneously solved itself, but after having to shut down the server yesterday due to a power outage (it is on a UPS), it booted back up, worked fine for several hours, and then went unresponsive sometime overnight. I have attached the syslog file. syslog
May 18, 20233 yr Community Expert That's the regular syslog after a reboot, not the persistent one from the syslog server.
May 20, 20233 yr Community Expert Solution May 16 16:33:32 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 16 16:33:32 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
May 22, 20233 yr Author On 5/20/2023 at 3:57 AM, JorgeB said: May 16 16:33:32 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 16 16:33:32 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)). I have done that, and due to how intermittent this problem is, I have marked that as the solution. I will start a new thread if it happens again; I still have persistent syslog going just in case.
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.