CaptainCopSuey Posted March 14 Share Posted March 14 Hello all. I've got a problem with my server that is utterly bewildering me. A couple weeks ago, and without making any changes to my server, it keeps crashing all of the time, and without any reproducible source. Genuinely, I have no idea what is going on here, and would appreciate any help anyone can offer. I've tried the following troubleshooting to no avail: Separated the main server IP from all docker vlan's to separate NIC's. Removed several docker containers that constantly seemed to be crashing the server. Disassembled and reassembled server to ensure no components have apparent physical damage. I'm sure I'm missing a lot here, so I've also attached my syslog here. Thanks. syslog-10.216.18.3.log Quote Link to comment
JorgeB Posted March 14 Share Posted March 14 There are multiple call traces, suggesting more a hardware issue, I would start by running memtest. Quote Link to comment
CaptainCopSuey Posted March 14 Author Share Posted March 14 Memtest completed with a Pass. Quote Link to comment
CaptainCopSuey Posted March 14 Author Share Posted March 14 Digging a little bit more into this issue, I seem to be having an error similar to the one here: https://forums.unraid.net/topic/157879-unraid-crashes-randomly-takes-a-few-restarts-to-come-back-up/ Quote Link to comment
JorgeB Posted March 15 Share Posted March 15 Memtest is only definitive if it finds an error, one other thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. Quote Link to comment
CaptainCopSuey Posted March 17 Author Share Posted March 17 Ok. I let it run for two days without docker enabled. Enabling docker, I've started slowly re-enabling containers, and it crashed on my immich. I restarted the process of enabling containers, got to jellyfin, which worked fine before, and now it crashed there. Immich still won't start without bringing my server to it's knees. Frustratingly, my syslog file, which is being saved to a separate location, shows call traces, but seems to offer no hint as to what is actually happening. I have no clue what is going, so have attached my newer syslog file here. syslog-10.216.18.3.log Quote Link to comment
CaptainCopSuey Posted March 17 Author Share Posted March 17 If it helps, I have my docker containers appdata stored on a cache, in a RAID 1 configuration. I have run the extended SMART testing on both, with both returning 0 errors. I can upload their reports if needed. Quote Link to comment
JorgeB Posted March 17 Share Posted March 17 Cannot say if it's software or hardware based on the call traces, but if it only crashes with those two containers maybe something in how they are configured. Quote Link to comment
Solution CaptainCopSuey Posted April 16 Author Solution Share Posted April 16 On 3/17/2024 at 1:50 PM, JorgeB said: Cannot say if it's software or hardware based on the call traces, but if it only crashes with those two containers maybe something in how they are configured. Replacing my CPU seems to have alleviated this particular call trace, but I've since seen a new kind of error arise. I've created a new topic for it here: 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.