doron Posted September 9, 2013 Share Posted September 9, 2013 When I returned home today I found that my unRAID server (5.0) has restarted (unorderly). Since the syslog is maintained in RAM, I can't see what happened. Is there anything I can do to track back what caused it? (doesn't seem to be a power issue). What is considered to be the common wisdom to address this? Link /var/log/syslog to permanent storage? rsyslog? (wouldn't have helped for sudden crash or panic anyway). Something else? Thanks for any insight. Quote Link to comment
mace5805 Posted September 9, 2013 Share Posted September 9, 2013 My System too restarted for some reason. 5.0 since it restarted unable to do syslog. Quote Link to comment
Frank1940 Posted September 9, 2013 Share Posted September 9, 2013 Open the case and check the inside for dust/dirt, stalled fans and look to see the power supply fan is working. This can be caused by overheating. Quote Link to comment
mace5805 Posted September 9, 2013 Share Posted September 9, 2013 but wouldn't that be odd that two users that just upgraded to the new 5.0 both have a system reboot last night? Just saying Quote Link to comment
doorunrun Posted September 10, 2013 Share Posted September 10, 2013 Have you looked to see if the active log got copied to /boot/logs? Depending on the type of shutdown/restart the active log should get written there. Quote Link to comment
dgaschk Posted September 10, 2013 Share Posted September 10, 2013 Have you looked to see if the active log got copied to /boot/logs? Depending on the type of shutdown/restart the active log should get written there. This is not correct. An add-on might do this but not a stock system. Quote Link to comment
doron Posted September 10, 2013 Author Share Posted September 10, 2013 Have you looked to see if the active log got copied to /boot/logs? Depending on the type of shutdown/restart the active log should get written there. This is not correct. An add-on might do this but not a stock system. Indeed. I don't even have a /boot/log directory. That would be a good way to start though, for future mishaps. Which add-on does that? Is it 5.0-ready? Something like that would not address a k-panic type crash, and things like that, but may shed light in some cases. I guess I could simply fiddle with /etc/syslog.conf upon boot and direct it to some permanent storage. Quote Link to comment
doron Posted September 10, 2013 Author Share Posted September 10, 2013 but wouldn't that be odd that two users that just upgraded to the new 5.0 both have a system reboot last night? Just saying NSA testing their new hooks? Quote Link to comment
dgaschk Posted September 10, 2013 Share Posted September 10, 2013 The powerdown script in unMenu will copy the syslog to the flash when it's called. This works on version 5. 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.