2016-11-23 16:40 GMT+01:00 David Lang <[email protected]>: > On Wed, 23 Nov 2016, Michael Biebl wrote: > >> 2016-11-22 16:35 GMT+01:00 David Lang <[email protected]>: >>> >>> As per a discussion here a couple months ago, adding imjournal more than >>> doubles the memory footprint of a running rsyslog instance, even if it's >>> not >>> used. >> >> >> Do you have reference to that discussion. >> I can't imagine that simply compiling in support for imjournal doubles >> the memory footprint of rsyslog and you will actually have to load the >> module. > > > I'll have to go hunting for it. IIRC it's within the last 3-6 months and > started with someone complaining about rsyslog becoming bloated. I don't > remember if it was on the mailing list, the forum, or the git issue tracker. > > David Lang
I think I have seen a similar thing just recently. IIRC, it wasn't loading of imjournal that brought the memory footprint but rather it occured while walking the journal. My guess is that there is a memory leak somewhere in (some version) of libsystemd-journal. This is the issue tracker: https://github.com/rsyslog/rsyslog/issues/1127 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.
