It was my fault at the end, my firewall was deleting the sessions after some time of inactivity (without sending the RST) and unfortunately with the tcp transport rsyslog didn't notice it was closed. I fixed the fw config and now works. I could also moved to udp, but this is better. I guess that the messages got disordered or discarded, but it seems to work now.
2016-07-14 14:25 GMT+02:00 Joan <[email protected]>: > I have set in the global rsyslog.conf these values, so the messages > doesn't get discarded in any case > -------------- > $SystemLogRateLimitInterval 0 > $SystemLogRateLimitBurst 0 > -------------- > > But when lines repeat I get this message. > -------------- > 8708.012812850:imfile.c : INOTIFY event: watch was MODIFID > 8708.012838408:imfile.c : strm 0x7f30c00057c0: file 7 read 12 bytes > 8708.012856623:imfile.c : msg repeated 1 times > 8708.012863356:imfile.c : message discarded by ratelimiting > 8708.012866960:imfile.c : strm 0x7f30c00057c0: file 7 read 0 bytes > 8708.012876321:imfile.c : stream checking for file change on > '/var/log/tomcat7/catalina.out', inode 158942/158942 > -------------- > > I am using 8.19.0-0adisconatrusty4, and the same behaviour doesn't seem to > be present on an older install that I have with 8.17.0-0adiscon2trusty1 > with basically the same config. > Are there any changes that might have affected this? > > _______________________________________________ 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.
