FYI: I guess this thread here is a duplicate of https://github.com/rsyslog/rsyslog/issues/3686
Knowing the full config would be useful. Can be created via $ rsyslogd -f /etc/rsyslog.conf -o /tmp/full_rsyslog_conf where -f should point to the main config file and the file pointed to by -o contains the full config. Post the latter. Rainer El mié., 12 jun. 2019 a las 10:48, Rainer Gerhards (<[email protected]>) escribió: > > El mar., 11 jun. 2019 a las 20:16, Michael Biebl (<[email protected]>) > escribió: > > If the problem is reliably reproducible (which seems to be on affected > > systems), maybe a git bisect would actually be the quickest way to > > find the commit causing this. > > Good point! > > @tobias: can you build from source? > > If not, we could work with git bisect and custom packages, but that > looks very time-consuming. > > 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.
