Hi All,

 

The past few days something very weird is happening, this is the second time I find my network down because somehow when the server has a kernel panic it takes the whole network down (maybe because of link aggregation protocol?)

 

This is the screenshot:

 

 

And the logs are in the attachments, I added one before I started array and one after because i'm not sure if that matters or not. Does anyone know what it might be? The last one happened in the weekend and now its today at around 14:30 CET.

unraidserver-diagnostics-20211129-1804.zip

unraidserver-diagnostics-20211129-1811.zip

Edited November 29, 20214 yr by Inenting

Did anyone maybe have the same problem recently?

Edited December 1, 20214 yr by Inenting

Sorry, we collectively missed your post.  

It looks like an issue with specific IPs attributed to docker containers.

 

If if this something you are using, I would suggest trying 6.10 RC2 and switch the docker network type from MacVLAN to IPVLAN.

Hey,

 

Don't worry about it! I'm just glad that that there is someone to reply unlike other forums

 

I'd rather not update to a rc build but if there is no choice I will have to do it. At the moment the server hasn't crashed yet since the last one. I will update the next time it happens.

 

Thank you for the tip and hopefully this'll be my last message in this topic  

Unfortunately I still have this problem even when updating to 6.10 RC2 and changing to IPVLAN. However my whole network doesn't go down with it anymore so that's an added bonus

 

I have a second unraid server, is there something I can do with that to diagnose this problem further?

The kernel panic happened again today, I restarted server around 18:35

 

Could it maybe be a plugin? Would it help to delete every plugin and docker and start over? 

 

Is there a way to keep my data and cache pool when making a new usb with unraid?

unraidserver-diagnostics-20220107-1946.zip

I've been thinking but could I get a kernel panic if the hardware is maybe defect? Like if a ram stick or cpu is not good?

Enable the syslog server and post that after a crash.

Hey, see the attachment for the syslogsyslog-127.0.0.1.log .

 

I've had the syslog on for a while so it should have all the crashes (if it registers that) 

 

Edit: I just noticed that it didn't update the syslog for a very long time... I disabled and enabled it but I also enabled remote syslog as well and point it now to my other unraid server (it wrote something so it should work). I'll wait for a crash now I guess...

Edited January 10, 20224 yr by Inenting