Smoetzak Posted January 15, 2021 Share Posted January 15, 2021 (edited) Hello people I'm using unraid for some months now but I still can't seem to fix why my server crashes on random times. It's allways at night, never have I seen it during the day. So I think it must have something to do with scheduled stuff. This also happens mostly in the weekends (but not exclusively and also at night). This also happens every week. Memory and cpu seem allright, no spikes or anything. I've attached my diagnostics, along with the syslog on the flash from the start of today (because the syslog from the diagnostics start from after the reboot). I've reset my server at 8:14 this morning. I really hope someone sees something that I can't. Thanks in advance for looking into this! smoetraid-diagnostics-20210115-1326.zip syslog 15-01-2021.txt Edited January 28, 2021 by Smoetzak Quote Link to comment
JorgeB Posted January 15, 2021 Share Posted January 15, 2021 Macvlan call traces are usually the result of having dockers with a custom IP address, more info below: Quote Link to comment
Smoetzak Posted January 15, 2021 Author Share Posted January 15, 2021 I definitely have a docker on br0 with another ip address in my subnet. I'll try your fix. Thanks for the fast response! Quote Link to comment
Smoetzak Posted January 16, 2021 Author Share Posted January 16, 2021 I've created a vlan for my dockers last evening: But it I still have the macvlan broadcast messages in the syslog. The fixed ip address is different from the ip address of the unraid server in that vlan. Is that the problem? syslog 16-01-2021.txt Quote Link to comment
JorgeB Posted January 16, 2021 Share Posted January 16, 2021 Sorry, outside my wheelhouse, someone else might help, if notask in the thread linked above. Quote Link to comment
Smoetzak Posted January 16, 2021 Author Share Posted January 16, 2021 I will try the fixes posted by other members in that threat first. Thanks anyway for steering me in the right direction! Quote Link to comment
Smoetzak Posted January 28, 2021 Author Share Posted January 28, 2021 This is solved. I've first tried making a different vlan on my eth0 interface, but the problem remained the same. I had to use the eth1 interface (different nic on my microserver) and used the vlan on that. Haven't got a crach since. 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.