Thanks for the response. Yes. I think it could be logrotate causing the issue. Are there any best practices to avoid duplicate logs? I open to an alternative option for rolling the logs.
As far as $InputFilePersistStateInterval is concerned, I'm aware it's by lines. I've sent over 20k lines to my log and the state file has not been modified. On Tue, Nov 1, 2011 at 5:43 PM, Andreas Piesk <[email protected]> wrote: > On 01.11.2011 21:06, Bob Corsaro wrote: > > > > Nov 1 04:27:16 balancer01 rsyslogd: [origin software="rsyslogd" > > swVersion="4.2.0" x-pid="14143" x-info="http://www.rsyslog.com";] > rsyslogd > > was HUPed, type 'lightweight'. > > do you use logrotate? i guess rsyslogd got SIGHUP from logrotate. > > > Anyway, I tried upgrading to 4.8.0, which does leave a state file in > > $WorkDirectory right away, instead of waiting for rsyslog to exit, but it > > doesn't seem to respect the $InputFilePersistStateInterval . I've > received > > well over 20k logs since starting it, but the state file remains > unchanged. > > you know that $InputFilePersistStateInterval is given in lines not bytes, > right? > > regards, > -ap > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
