It is generally a good idea to enable impstats to check where exactly queues build up (and how large they grow). Based on that information, we can evaluate if it just is a config issue or indeed a memory leak (as david said, none is currently known).
Rainer 2017-04-07 18:20 GMT+02:00 David Lang <[email protected]>: > the first thing is to check to see if you have delivery problems and queues > building up. configure impstats to output information on queue sizes. > > There are not any known problems causing this. > > David Lang > > On Sat, 8 Apr 2017, Tomasz Chmielewski via rsyslog wrote: > >> After a recent update to rsyslog 8.26, rsyslogd process is using gigabytes >> of RAM on a few of my servers. >> >> Restarting rsyslogd helps, but RAM usage is slowly growing and growing. >> >> Is it a known issue? If not - how can I debug it? > > _______________________________________________ > 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. _______________________________________________ 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.
