October 24, 201015 yr It appears my syslog is completely filled and unRAID is no longer logging messages to the log file. I am in the middle of preclearing 3 disks and it looked like a bad disk completely filled up the log with I/O errors. I just want to be able to see if the other two drives have any I/O errors. I saved a copy of the syslog using unMenu and it was 2 GB, which happens to be too unmanageable for notepad or wordpad in Windows. Is there a way to flush the syslog without bringing down the server so that new messages are logged?
October 25, 201015 yr Author Might want to read this thread for clues. Interesting read. It appeared something was implemented since then because my system did not crash, but the syslog stopped recording. So next time can I stop the syslog daemon, delete the log file, and restart the daemon so logging can continue?
Archived
This topic is now archived and is closed to further replies.