lelouch420 Posted April 4, 2023 Share Posted April 4, 2023 Basically the title. Everything has been running great for months, I actually recently re-installed docker. It seems to happen regardless of if the server is doing anything or idle. joesserver-diagnostics-20230404-1920.zip I was wondering if my logs reveal anything? If not, i will set up a syslog server on my main pc. Quote Link to comment
JorgeB Posted April 5, 2023 Share Posted April 5, 2023 Enable the syslog server and post that after a crash. Quote Link to comment
lelouch420 Posted April 5, 2023 Author Share Posted April 5, 2023 do you have any suggestions for a client i can install on my windows pc ? Quote Link to comment
JorgeB Posted April 5, 2023 Share Posted April 5, 2023 Client for the syslog server? You can just enable the mirror to flash drive option. Quote Link to comment
lelouch420 Posted April 8, 2023 Author Share Posted April 8, 2023 joesserver-diagnostics-20230407-1117.zipsyslog anything? I think one of my new disks is failing, but this issue has been happening before i installed that disk . Quote Link to comment
JorgeB Posted April 8, 2023 Share Posted April 8, 2023 Apr 7 21:01:18 JoesServer kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Apr 7 21:01:18 JoesServer kernel: ? _raw_spin_unlock+0x14/0x29 Apr 7 21:01:18 JoesServer kernel: macvlan_process_broadcast+0xbc/0x12f [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 enabled, top right)) Quote Link to comment
lelouch420 Posted April 8, 2023 Author Share Posted April 8, 2023 thanks ive made the changes 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.