Earlier this week, I had to restart the rsyslog daemon (v7.4.5) on one of our rsyslog aggregators/archivers to put in some new configs, and it did not shut down cleanly; this corrupted the gzipped archive that the daemon writes logs out to, making it unreadable (without heroic measures, at least). Since we have redundant archives, this was not a horrific problem, but I'm wondering if there's some sort of action I can take to make sure this does not happen in the future. Any suggestions?
_______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
