Am Di., 11. Juni 2019 um 19:26 Uhr schrieb Rainer Gerhards via rsyslog <[email protected]>: > > El mar., 11 jun. 2019 a las 19:23, Heaton, Tobias > (<[email protected]>) escribió: > > > > Rainer, > > > > I traced my steps and allowed rsyslog to run for 45 minutes without seeing > > a failure. > > > > The debug puts considerable strain on the system, so much so that the log > > timestamps started drifting. I was seeing logs stamped at 13:18 EST at > > 13:31EST actual time. > > > > Furthermore the debug log is nearly 70GB, closing in on the available disk > > space. > > > > Is there anything else I can try to help troubleshoot this problem? > > Not really. Maybe the first 12 GiB actually contain info that get's us > a bit closer. So if you could share that, it would be useful. We can > fine-tune the debug output, but as we have not the slightest idea of > what may be the root cause that's no option. >
If the problem is reliably reproducible (which seems to be on affected systems), maybe a git bisect would actually be the quickest way to find the commit causing this. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ 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.
