[rsyslog] correct way to redirect log messages to STDOUT

working in a container env, the ask is to have a single rsyslog process "concentrate" logs from disparate processes and spit them out to STDOUT. what's the *right way* to do this? ___ rsyslog mailing list

Re: [rsyslog] Static and dynamic configuration of rsyslog - problem with error "STOP is followed by unreachable statements!"

check here: https://github.com/rsyslog/rsyslog/pull/4391 Rainer El mié., 26 ago. 2020 a las 13:15, Rainer Gerhards () escribió: > > I hadn't thought there was a legit use case for this, but you have a > point. Looking at the quoted thread, I would also tend to say the > message should be a

Re: [rsyslog] Static and dynamic configuration of rsyslog - problem with error "STOP is followed by unreachable statements!"

I hadn't thought there was a legit use case for this, but you have a point. Looking at the quoted thread, I would also tend to say the message should be a warning: https://github.com/rsyslog/rsyslog/issues/3668#issuecomment-493107691 Rainer El mié., 26 ago. 2020 a las 12:32, Thomas Spitz via

[rsyslog] queue files handling question

Running rsyslog 8.2001 on Debian 10 we do monitor file changes with use of iWatch [1]. Within monitoring we occasionally see a lot of messages Aug 26 00:01:10 loco iWatch[3575]: * /chroot/net/var/spool/rsyslog/mainq.qi.tmp is moved to /chroot/net/var/spool/rsyslog/mainq.qi Aug 26 00:01:10 loco

[rsyslog] Static and dynamic configuration of rsyslog - problem with error "STOP is followed by unreachable statements!"

Hello everyone, I have noticed that it is not possible to put commands after a "stop" anymore. In such a case we have the following error : "STOP is followed by unreachable statements". It has been confirmed severa times namely through this post : https://github.com/rsyslog/rsyslog/issues/3668