anexcreed Posted September 21, 2023 Share Posted September 21, 2023 About a month ago my system would crash after less than 24 hours almost daily. I've tried rolling back versions, uninstalling plugins, updated bios, memtest results with no errors. Now the crashes are happening days in between but still no real rhyme or reason. Can anyone gleam anything from my logs? I really appreciate any time spent on this, thank you! blade2.0-diagnostics-20230921-0911.zip Quote Link to comment
trurl Posted September 21, 2023 Share Posted September 21, 2023 setup syslog server Quote Link to comment
Mlatx Posted September 21, 2023 Share Posted September 21, 2023 I'm having the same issue the last couple of days. I have syslog server running, and there are no visible errors. It runs fine during the day. When the dockers update at midnight, the UI is unavailable as well as all docker apps. Today, I downgraded to 6.12.3, and now it won't boot up. I believe I have a backup from when I moved to 6.12 or really hope I do. I had no issues with 6.12.3. Here are my syslog events since it became unresponsive. Sep 21 00:00:01 server Docker Auto Update: Community Applications Docker Autoupdate running Sep 21 00:00:01 server Docker Auto Update: Checking for available updates Sep 21 00:00:36 server Docker Auto Update: Found update for AdGuard-Home. Not set to autoupdate Sep 21 00:00:36 server Docker Auto Update: Stopping postgresql14 Sep 21 00:00:36 server kernel: veth5f54955: renamed from eth0 Sep 21 00:00:36 server Docker Auto Update: Stopping sabnzbd Sep 21 00:00:41 server Docker Auto Update: Installing Updates for postgresql14 adminer sabnzbd Sep 21 00:00:51 server Docker Auto Update: Restarting postgresql14 Sep 21 00:00:52 server kernel: eth0: renamed from veth0d401ff Sep 21 00:00:52 server Docker Auto Update: Restarting sabnzbd Sep 21 00:00:52 server sSMTP[10781]: Creating SSL connection to host Sep 21 00:00:52 server sSMTP[10781]: SSL connection using TLS_AES_256_GCM_SHA384 Sep 21 00:00:55 server sSMTP[10781]: Sent mail for "my email" (221 2.0.0 Service closing transmission channel) uid=0 username=root outbytes=661 Sep 21 00:00:55 server Docker Auto Update: Community Applications Docker Autoupdate finished Sep 21 00:01:34 server root: /etc/libvirt: 920 MiB (964665344 bytes) trimmed on /dev/loop3 Sep 21 00:01:34 server root: /var/lib/docker: 34.7 GiB (37309169664 bytes) trimmed on /dev/loop2 Sep 21 00:01:34 server root: /mnt/cache: 1.6 TiB (1781115658240 bytes) trimmed on /dev/sdc1 Quote Link to comment
anexcreed Posted September 21, 2023 Author Share Posted September 21, 2023 2 hours ago, trurl said: setup syslog server I thought i had this setup, i have both the syslog server enabled and mirror to flash checked but maybe you cant do both at the same time. Anyways, i think the syslog to flash is working now, just had another crash during parity check and now it wont boot at all, so i pulled the syslog off the flash drive for your viewing. I dont see anything obvious. syslog Quote Link to comment
JorgeB Posted September 21, 2023 Share Posted September 21, 2023 There are multiple call traces, most mention zfs, I would start by running memtest, if no errors are found remove one of the RAM sticks and try again, if the same try the other stick alone, that will basically rule out bad RAM. Quote Link to comment
Solution anexcreed Posted October 5, 2023 Author Solution Share Posted October 5, 2023 After a crash, my system wouldn't boot and was flashing an error code. Ended up leading me to reseating the CPU (havnt touched it since i installed it 3 years ago) and since then, things are nice and stable again. Thanks to everyone who took a look at this! 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.