July 10, 20233 yr Hi Everyone, Not sure how to tackle this issue so i am reaching out to you guys Every two days my Unraid becomes unresponsive in the sense that the server is not accessible via GUI however i can ping the server. I need to power cycle the server and works fine for two days then this happens again. Can anyone guide me on how i can potentially find out what is the issue? To note the server was ok until the last update once i made the update this happens. ( Sorry for my English not my first language)
July 10, 20233 yr Community Expert Enable the syslog server and post that after a crash together with the diagnostics.
July 10, 20233 yr Author I will turn on the server tonight as it crashed again and i will post again in 2 days. Thank you JorgeB I attached the diagnostics for the moment and i will come back with the syslog when the server is crashing tower-diagnostics-20230711-1044.zip Edited July 11, 20233 yr by Robert Sitavu Update
July 12, 20233 yr Author On 7/10/2023 at 11:06 AM, JorgeB said: Enable the syslog server and post that after a crash together with the diagnostics. Please find attached the syslog syslog also please note that the server become unresponsive around 01:17AM and i force restarted the server around 07:42AM. I would really appreciate your help guys as this is driving me crazy.
July 12, 20233 yr Community Expert Solution Jul 12 07:43:04 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 12 07:43:04 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Jul 12 07:43:04 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)).
July 12, 20233 yr Author 17 minutes ago, JorgeB said: Jul 12 07:43:04 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 12 07:43:04 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Jul 12 07:43:04 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 will do that now and i will update if it happens again. Thank you
July 14, 20233 yr Author Server just went down again at 04:30 AM tower-diagnostics-20230714-0852.zip syslog
July 14, 20233 yr Community Expert There's nothing logged, does the server just crash or it really shuts down?
July 14, 20233 yr Author 6 minutes ago, JorgeB said: There's nothing logged, does the server just crash or it really shuts down? It's crashing i need to force shutdown using the power button of the computer.
July 17, 20232 yr Author On 7/14/2023 at 10:33 AM, JorgeB said: Try again after this boot, post new syslog if crashes again. I have 3 days of up-time so i think it's ok now. Do you think it's safe to update to Unraid 6.12.3?
July 17, 20232 yr Community Expert 5 hours ago, Robert Sitavu said: Do you think it's safe to update to Unraid 6.12.3? Should be.
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.