mikesp18 Posted July 17, 2021 Share Posted July 17, 2021 I am starting to get frequent problems with Unraid. It always seems to happen in the middle of the night, or when I'm at work. It's frustrating when the wife and kids complain when I get out of work and I have to try to trouble shoot. So, help me with my marriage. I'm attaching dianostics, and syslog. The system was up and running around 03:00am local, and was problematic when I notices around 14:00 local. The screen GUI was up on the local box but unresponsive. SSH was not working. WebGui was not working. I did have a drive problem yesterday that was solved in another thread (xfs_repair), though I suspect unrelated since this current issue is an ongoing issue. This has happened repeatedly, and requires a hard reset, which unfortunately then starts a parity check which runs around 36 hours. Any ideas? orcrist-diagnostics-20210717-1558.zip orcrist-syslog-20210717-2207.zip Quote Link to comment
JorgeB Posted July 18, 2021 Share Posted July 18, 2021 Enable syslog mirror to flash then post that log after a crash. Quote Link to comment
mikesp18 Posted July 18, 2021 Author Share Posted July 18, 2021 (edited) Thanks, Jorge. I had another crash while I was at work. I'll upload it in the morning. I had enabled a system log but had it writing to a local file and backing it up every 10 minutes. I was worried that backing it up to the flash drive would write too much data. Is that really an issue? Do I need to take the file off of the flash drive before I restart unRAID? If I restart the system will it overwrite the existing log file? Just curious about the order that I should do things. Edited July 18, 2021 by mikesp18 Quote Link to comment
JorgeB Posted July 18, 2021 Share Posted July 18, 2021 57 minutes ago, mikesp18 said: Do I need to take the file off of the flash drive before I restart unRAID? No Quote Link to comment
mikesp18 Posted August 17, 2021 Author Share Posted August 17, 2021 (edited) syslog Well, just got a crash with syslog server running. I was watching a movie, so I know the server went down shortly before the restart. EDIT: looks like there is a filesize limit, and the errors spammed so hard to make the file 50mb. This is just the last 1mb ish of the file syslog1 Edited August 17, 2021 by mikesp18 Quote Link to comment
trurl Posted August 17, 2021 Share Posted August 17, 2021 1 hour ago, mikesp18 said: filesize limit syslog is text, which compresses very well. Zip it Quote Link to comment
mikesp18 Posted August 17, 2021 Author Share Posted August 17, 2021 syslog.zip Et voila! Good idea Quote Link to comment
mikesp18 Posted August 17, 2021 Author Share Posted August 17, 2021 (edited) And another crash around 23:00 8/16/2021.syslog (3).zip Edited August 17, 2021 by mikesp18 Quote Link to comment
JorgeB Posted August 17, 2021 Share Posted August 17, 2021 There's nothing logged about the crash: Aug 16 23:01:10 Orcrist rc.inet1: ip link set lo down Aug 17 08:06:25 Orcrist kernel: microcode: microcode updated early to revision 0xde, date = This usually indicates a hardware problem. Quote Link to comment
mikesp18 Posted August 19, 2021 Author Share Posted August 19, 2021 On 8/17/2021 at 8:42 AM, JorgeB said: There's nothing logged about the crash: Aug 16 23:01:10 Orcrist rc.inet1: ip link set lo down Aug 17 08:06:25 Orcrist kernel: microcode: microcode updated early to revision 0xde, date = This usually indicates a hardware problem. I think I figured it out. The UPS Daemon was triggering the shutdown I think. Unclear why, it is at full power. But, that's the least bad thing it could be. 1 Quote Link to comment
mikesp18 Posted August 22, 2021 Author Share Posted August 22, 2021 orcrist-diagnostics-20210821-2347.zipsyslog.zip I'm getting pretty frustrated. I'm crashing roughly once every other day at this point. I thought the problem was the UPS triggering shutdowns, but alas, it's no longer hooked up via UPS. No recent hardware changes. The only thing obvious in the syslog is this message spammed 1000 times (exageration). ANy ideas? Tonight looks like around Aug 21 23:21, system was still powered on, the webui wouldn't log in, and physical screen was crashed at the GUI login screen, and the keyboard was unresponsive. Does this mean anything useful? Aug 21 23:21:48 Orcrist rsyslogd: file '/var/log/syslog'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Aug 21 23:21:48 Orcrist rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Quote Link to comment
JorgeB Posted August 22, 2021 Share Posted August 22, 2021 1 hour ago, mikesp18 said: Does this mean anything useful? No, it just means the syslog server is not correctly configured, check config or set it to mirror to the flash drive instead. Quote Link to comment
trurl Posted August 22, 2021 Share Posted August 22, 2021 Don't know why you keep creating new threads for the same problem. I have merged them all. Isn't that better since we all now have some context about what has already been discussed? Quote Link to comment
Tristankin Posted August 23, 2021 Share Posted August 23, 2021 Try downgrading to 6.8.3 or upgrading to 6.10-RC1. I was getting hangs every 2 days or so, now I am back on 6.8.3 the system has been rock solid for the last 23 days 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.