jj_uk Posted August 11, 2021 Share Posted August 11, 2021 (edited) Server was unresponsive this morning. I couldn't ping the server IP address, no web gui and dockers didn't seem to be working. I've looked in the diagnostics (attached) that were generated once the server had restarted from a hard reset, but don't know what I'm looking for. Any help appreciated. Edited August 11, 2021 by jj_uk Quote Link to comment
trurl Posted August 11, 2021 Share Posted August 11, 2021 6 hours ago, jj_uk said: generated once the server had restarted from a hard reset https://wiki.unraid.net/Manual/Troubleshooting#Persistent_Logs_.28Syslog_server.29 Quote Link to comment
jj_uk Posted August 11, 2021 Author Share Posted August 11, 2021 Dang. I was logging to flash a while back but disabled it. I've now set up a syslog server to ssd. Thanks. Quote Link to comment
jj_uk Posted August 14, 2021 Author Share Posted August 14, 2021 (edited) I've just performed a hard reset as the server locked up earlier today. Edited August 14, 2021 by jj_uk Quote Link to comment
jj_uk Posted August 14, 2021 Author Share Posted August 14, 2021 (edited) Aug 14 13:39:48 tower1 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 That's interesting. Attached the syslog. syslog-192.168.1.230.log Edited August 14, 2021 by jj_uk Quote Link to comment
trurl Posted August 14, 2021 Share Posted August 14, 2021 Your attachment doesn't work for some reason. Quote Link to comment
jj_uk Posted August 14, 2021 Author Share Posted August 14, 2021 (edited) 1 hour ago, trurl said: Your attachment doesn't work for some reason. I used the drag and drop method on the forum. I've redone it now with the "select files" option. Seems that drag/drop doesn't work for me. Attached. syslog-192.168.1.230.log Edited August 14, 2021 by jj_uk Quote Link to comment
trurl Posted August 14, 2021 Share Posted August 14, 2021 Don't have your diagnostics anymore and you deleted them so I don't remember anything about your hardware. Have you done memtest? Quote Link to comment
jj_uk Posted August 14, 2021 Author Share Posted August 14, 2021 Attached are the diagnostics. I've not run a memtest. tower1-diagnostics-20210811-0911.zip Quote Link to comment
JorgeB Posted August 15, 2021 Share Posted August 15, 2021 Aug 13 18:20:28 tower1 kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Aug 13 18:20:28 tower1 kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 might fix it, or more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/ Quote Link to comment
jj_uk Posted August 15, 2021 Author Share Posted August 15, 2021 Ok thanks. I've updated to 6.10.0 rc1. Hopefully that'll fix it, but if not, I'll move pihole to a RPI, as the other methods of fixing this are beyond me. 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.