On Thu, Sep 12, 2013 at 2:40 PM, Rainer Gerhards <[email protected]>wrote:
> On Thu, Sep 12, 2013 at 2:39 PM, Rainer Gerhards <[email protected] > > wrote: > >> >> On Thu, Sep 12, 2013 at 2:31 PM, Erik van Dam <[email protected]> wrote: >> >>> Sure! >>> >>> http://pastebin.com/tBb2NWUR >>> >>> >> Do you restart rsyslog every hour? From the stats, it looks so... >> >> > I guess I can answer that myself: of course you do, trying to circumvent > the problem ;) Sorry for the noise... > > > mhhh... unfortunately, this means we do never see the error, and so we cannot see what triggered it. The stats I got look fine and provide no indication of a problem. Do I guess right that there was no problem in that timeframe? If it was, could you point me to the time the problem occured. If there was no problem, you need to re-run impstats, but this time let rsyslog run into trouble. Then we can see if s/t fills up. For best resuts, I suggest to use a stats reporting interval of 1 minute. Rainer _______________________________________________ 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.
