It's a pretty old version. I think even one with quite some bugs in kafka components. I suggest to current 8.2002.0 and see if the issue persists. You have also quite large queues - if there resides e.g. 500,000 messages in the cee-json-parsed-ok queue, it takes a while to write them out to disk on shutdown ;-)
Rainer El mar., 10 mar. 2020 a las 16:49, pedro.m.reis via rsyslog (<[email protected]>) escribió: > > When I stopped it I get: > > Mar 10 15:36:03 log03 systemd[1]: Stopping System Logging Service... > Mar 10 15:41:03 log03 systemd[1]: rsyslog.service: State 'stop-sigterm' > timed out. Killing. > Mar 10 15:41:03 log03 systemd[1]: rsyslog.service: Killing process 7986 > (rsyslogd) with signal SIGKILL. > Mar 10 15:41:03 log03 systemd[1]: rsyslog.service: Main process exited, > code=killed, status=9/KILL > Mar 10 15:41:03 log03 systemd[1]: rsyslog.service: Failed with result > 'timeout'. > Mar 10 15:41:03 log03 systemd[1]: Stopped System Logging Service. > > > > -- > Sent from: http://rsyslog-users.1305293.n2.nabble.com/ > _______________________________________________ > 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.
