geeksheikh Posted September 3 Share Posted September 3 Hi, the last two nights I've noticed my server locking up. I cannot even ssh in or log into root local. Since the logs disappear after the reboot, I can't even see what led up to it. I've tried to find a way to spool the sys logs to somewhere else but I can't seem to get it to work. Any ideas what might be causing these kernel panics or what to do to get the logs that will help me diagnose? It started happening two nights ago. The only changes were * Added vaultwarden docker container * Added nginxProxyManager (NPM) -- Used to use swag, disabled that container and switched to NPM Attached is a screenshot of the kernel panic vomit from the console and the diagnostics bundle. Any help would be much appreciated. Thank you pumbaa-diagnostics-20240903-0923.zip Quote Link to comment
geeksheikh Posted September 3 Author Share Posted September 3 I do see ZFS is at 100% but I don't know what this metric stands for on the Dashboard page Quote Link to comment
Woodpusherghd Posted September 3 Share Posted September 3 Enable the Syslog server under network services and the log will be written to the chosen location which will survive a reboot. Quote Link to comment
Solution JorgeB Posted September 3 Solution Share Posted September 3 That call trace is not complete, but looks like it may be macvlan related, upgrade to latest stable, since macvaln with bridging is no longer an issue there. Quote Link to comment
geeksheikh Posted September 3 Author Share Posted September 3 57 minutes ago, Woodpusherghd said: Enable the Syslog server under network services and the log will be written to the chosen location which will survive a reboot. Thanks @Woodpusherghd -- I do have it enabled but I'm still not getting any syslog replication to the target share (on cache drive) Quote Link to comment
geeksheikh Posted September 3 Author Share Posted September 3 I completed the upgrade to 6.12.13, we'll see if that resolves the issue. Still cannot get syslog server to push logs to the cache share Quote Link to comment
itimpi Posted September 3 Share Posted September 3 2 hours ago, geeksheikh said: Thanks @Woodpusherghd -- I do have it enabled but I'm still not getting any syslog replication to the target share (on cache drive) The settings you have mean it is only listening for other servers. As mentioned in the syslog server link to get your server to record its own entries you need to set either the Mirror to Flash option OR the Remote Syslog server field to the address of your Unraid server. Quote Link to comment
geeksheikh Posted September 4 Author Share Posted September 4 lol oops. Seems obvious now. Thanks Quote Link to comment
geeksheikh Posted September 5 Author Share Posted September 5 (edited) It seems that the upgrade has resolved the issue. No crashes for the past two evenings. Thanks all Edited September 5 by geeksheikh 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.