GM_XIII Posted February 29 Share Posted February 29 Hi all, I have been having stability issues with my server since updating and I am not very sure what is going on. I am attaching a syslog from today where it stopped working in the morning as well as a recent diagnostics. The server has been running a reduced number of dockers (home-assistant and mqtt) and I have now left it on with no dockers running. Can you see anything obviously wrong on the below? I will keep the server running on safe mode and see if it crashes without docker. Thanks! vader-diagnostics-20240229-1950.zip SyslogCatchAll-2024-02-29.txt Quote Link to comment
JorgeB Posted March 1 Share Posted March 1 2024-02-29 02:52:16 Kernel.Warning 192.168.21.21 Feb 29 02:52:20 Vader kernel: macvlan_broadcast+0x10a/0x150 [macvlan] 2024-02-29 02:52:16 Kernel.Warning 192.168.21.21 Feb 29 02:52:20 Vader kernel: ? _raw_spin_unlock+0x14/0x29 2024-02-29 02:52:16 Kernel.Warning 192.168.21.21 Feb 29 02:52:20 Vader kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually 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)), then reboot. Quote Link to comment
yayitazale Posted March 2 Share Posted March 2 On 3/1/2024 at 9:57 AM, JorgeB said: 2024-02-29 02:52:16 Kernel.Warning 192.168.21.21 Feb 29 02:52:20 Vader kernel: macvlan_broadcast+0x10a/0x150 [macvlan] 2024-02-29 02:52:16 Kernel.Warning 192.168.21.21 Feb 29 02:52:20 Vader kernel: ? _raw_spin_unlock+0x14/0x29 2024-02-29 02:52:16 Kernel.Warning 192.168.21.21 Feb 29 02:52:20 Vader kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually 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)), then reboot. Hi: I'm want to migrate from MACVLAN to IPVLAN but I can't select it from the drop-down menu. The option is not clickable. I don't see anything in the docs related to the required changes prior to switching from MACVLAN to IPVLAN, neither any manual or guide about how to perform this change. Can you help me please? Thanks. Quote Link to comment
JorgeB Posted March 2 Share Posted March 2 22 minutes ago, yayitazale said: I'm want to migrate from MACVLAN to IPVLAN but I can't select it from the drop-down menu. The option is not clickable. That suggests you have bridging disabled, with that only macvlan is possible, and safe to use, but if you want ipvlan enable bridging first. 1 Quote Link to comment
yayitazale Posted March 4 Share Posted March 4 On 3/2/2024 at 12:41 PM, JorgeB said: That suggests you have bridging disabled, with that only macvlan is possible, and safe to use, but if you want ipvlan enable bridging first. Thank you. 1 Quote Link to comment
yayitazale Posted March 4 Share Posted March 4 On 3/2/2024 at 12:41 PM, JorgeB said: That suggests you have bridging disabled, with that only macvlan is possible, and safe to use, but if you want ipvlan enable bridging first. Hi, I changed to ipvlan and I'm having again the same unresponsiveness issue. I have attached the diagnostics file downloaded just after a hard (button) restart of the server. I have a speedtest running every hour and I can see that tit was running flawlessly until the one at 19:00 when the server was unresponsive. This means it is a network error as the proceses and dockers were still alive. This errors stared with v6.12.3 What can I do? I'm going to be 1 month in the abroad and I will no have any way to restart the server with the button and I'm pretty sure it will no last responsive for that long.... tower-diagnostics-20240304-1905.zip Quote Link to comment
JorgeB Posted March 4 Share Posted March 4 19 minutes ago, yayitazale said: I have attached the diagnostics file downloaded just after a hard (button) Syslog starts over after every boot, enable the syslog server and post that after a crash. Quote Link to comment
yayitazale Posted March 14 Share Posted March 14 On 3/5/2024 at 3:37 AM, JorgeB said: Syslog starts over after every boot, enable the syslog server and post that after a crash. It happened again, now with syslog server activated. There you have the diagnostics file attached. tower-diagnostics-20240314-0915.zip Quote Link to comment
JorgeB Posted March 14 Share Posted March 14 You didn't post the persistent syslog from the syslog server. Quote Link to comment
yayitazale Posted March 23 Share Posted March 23 On 3/14/2024 at 10:07 AM, JorgeB said: You didn't post the persistent syslog from the syslog server. I have activated: But there is no file in appdata. Quote Link to comment
trurl Posted March 23 Share Posted March 23 You have to specify which server to send the syslog to. Put the IP address of your Unraid server in the Remote syslog server field. Quote Link to comment
yayitazale Posted March 23 Share Posted March 23 8 minutes ago, trurl said: You have to specify which server to send the syslog to. Put the IP address of your Unraid server in the Remote syslog server field. Thanks Quote Link to comment
Recommended Posts
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.