Arcau Posted July 14, 2022 Share Posted July 14, 2022 The past couple of weeks my server has just been randomly crashing every few days. The Dockers all shut down and are unaccassible and the webgui is unresponsive. I have to power cycle the server and then of course the array wants to do a parity check so it finishes a parity check and then the next day seems to die and do it all over again. Have attached logs from reboot after last crash honestly no idea where to even start to diagnose this one blastoise-diagnostics-20220714-1055.zip Quote Link to comment
JorgeB Posted July 14, 2022 Share Posted July 14, 2022 Enable the syslog server and post that after a crash. 1 Quote Link to comment
Arcau Posted July 18, 2022 Author Share Posted July 18, 2022 ok I have set it up now, I did have a crash between the reply and me actually setting it up so fingers crossed it can help. Thank you @JorgeB hoping it can shed some light on things as it is getting a bit annoying. Quote Link to comment
Arcau Posted July 29, 2022 Author Share Posted July 29, 2022 Have not had a crash since the last update, apparently turning on the loggin was enough to scare it into behaving it seems...... 2 Quote Link to comment
ChatNoir Posted July 29, 2022 Share Posted July 29, 2022 2 hours ago, Arcau said: Have not had a crash since the last update, apparently turning on the loggin was enough to scare it into behaving it seems...... Have you changed anything else in the mean time ? Quote Link to comment
Squid Posted July 29, 2022 Share Posted July 29, 2022 You should also stop overclocking your RAM. You're running your ram at 3000MT/s (XMP profile) while you bought and paid for 2133MT/s memory. All overclocks introduce stability problems. Quote Link to comment
Arcau Posted July 29, 2022 Author Share Posted July 29, 2022 4 hours ago, ChatNoir said: Have you changed anything else in the mean time ? Nope, just updated dockers and plugins as they came about. Nothing else changed Quote Link to comment
Arcau Posted August 7, 2022 Author Share Posted August 7, 2022 On 7/29/2022 at 9:37 PM, ChatNoir said: Have you changed anything else in the mean time ? Ok after some time of being stable it has managed to crash twice in as many days. I am attaching the syslog file for any further insight. I think its having a Cstate issue from that maybe very unsure though sorry syslog-10.100.10.80.log Quote Link to comment
Solution JorgeB Posted August 7, 2022 Solution Share Posted August 7, 2022 Aug 6 22:50:16 Blastoise kernel: macvlan_broadcast+0x116/0x144 [macvlan] Aug 6 22:50:16 Blastoise kernel: macvlan_process_broadcast+0xc7/0x110 [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 enable, top right)), or see below for more info. 1 Quote Link to comment
Arcau Posted August 8, 2022 Author Share Posted August 8, 2022 15 hours ago, JorgeB said: Aug 6 22:50:16 Blastoise kernel: macvlan_broadcast+0x116/0x144 [macvlan] Aug 6 22:50:16 Blastoise kernel: macvlan_process_broadcast+0xc7/0x110 [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 enable, top right)), or see below for more info. Fantastic I have now changed that from the macvlan to ipvlan Fingers crossed it solves the issue <3 Quote Link to comment
Arcau Posted August 23, 2022 Author Share Posted August 23, 2022 Has been rock solid since this change THANK YOU @JorgeB 1 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.