Server not responding to ping. Syslog attached

[the1poet]

I noticed a while back that my server would sometimes stop responding. This prompted me to dump my syslog's to another server so I could access them the next time it happened.

Can anyone explain what this log means and why the server has stopped responding?

Currently running 6.10.0-rc2

 

Thanks

syslog.txt

[trurl]

attach diagnostics to your NEXT post in this thread.

[the1poet]

7 minutes ago, trurl said:

attach diagnostics to your NEXT post in this thread.

I've pressed the power button which has gone back to the terminal and it's currently at:

Starting diagnostics collection...

How long does this usually take?

[trurl]

23 minutes ago, the1poet said:

syslog's to another server

Is that all the syslog you got?

[the1poet]

hi @trurl, i just grabbed from the top of where it started showing that error, down. Did you want before that?

The "Starting diagnostics collection..." didn't complete so I had to force power down, then ran diagnostics after it powered back on.

homenas-diagnostics-20211113-1254.zip

[trurl]

1 hour ago, the1poet said:

Did you want before that?

yes

[the1poet]

Attached complete syslog

syslog-192.168.1.12.log.zip

[trurl]

Nov 13 10:33:06 HomeNAS kernel: Workqueue: events macvlan_process_broadcast [macvlan]

https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6100-rc1-available-r1514/

Quote

Docker custom networks

A new setting for custom networks is available. Originally custom networks are created using the macvlan mode, and this mode is kept when upgrading to version 6.10

The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require to reconfigure anything on Docker level, internally everything is being taken care off.

 

[the1poet]

@trurl I've changed over to ipvlan. will monitor and see how it goes. thanks for the help.