[rsyslog] using 2 different ActionOMProgBinary

2020-05-05 Thread Fourhundred Thecat via rsyslog
Hello, I am using "ActionOMProgBinary" in my /etc/rsyslog.conf ... $ActionOMProgBinary /usr/local/sbin/blacklist.py ... mail.* :omprog: ... Now I actually need to define 2 different binaries, and call one for mail.* and the other for auth.* How could I do this ? I am using rsyslog 8.

Re: [rsyslog] OBS builds stuck at 8.2001

2020-05-05 Thread David Lang via rsyslog
On Tue, 5 May 2020, Rainer Gerhards wrote: also, could you take a look at the pull requests for liblognorm? there are a bunch of contributions that have been sitting for a long time. I will and have done, but IIR a lot could not easily be merged. Will have a new look again. thanks, could you

Re: [rsyslog] omfile thread terminated too quick

2020-05-05 Thread Peter Viskup via rsyslog
It was related to size of dynaFileCache. Strange is that the omfile thread was stopped. Might make sense to update documentation in a way that the consequences of invalidating cache entry to omfile threading will be more clear. It is not mentioned at all. Peter On Tue, May 5, 2020 at 10:33 AM Pe

Re: [rsyslog] OBS builds stuck at 8.2001

2020-05-05 Thread Rainer Gerhards via rsyslog
El mar., 5 may. 2020 a las 12:44, David Lang via rsyslog () escribió: > > 8.2002 and 8.2004 are not showing up on OBS There seem to be some tech problems with OBS. I just tried yesterday to update it, but for now, I receive unexpected errors trying to upload the new releases. Working on it. > > a

[rsyslog] OBS builds stuck at 8.2001

2020-05-05 Thread David Lang via rsyslog
8.2002 and 8.2004 are not showing up on OBS also, could you take a look at the pull requests for liblognorm? there are a bunch of contributions that have been sitting for a long time. David Lang ___ rsyslog mailing list https://lists.adiscon.net/mail

Re: [rsyslog] Antwort: Re: oversizemsg.input.mode is invalid/unknown config option

2020-05-05 Thread Rainer Gerhards via rsyslog
Just a tipp: if you search for the old-style construct inside the rsyslog documentation, it's context and relation to the new style should show up, often together with a sample. See here: https://www.rsyslog.com/doc/master/rainerscript/queue_parameters.html?highlight=actionqueuediscardseverity HT

Re: [rsyslog] omfile thread terminated too quick

2020-05-05 Thread Peter Viskup via rsyslog
Reported bug for Debian package https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959774 Following is the evidence of the rotated thread PIDs: root@fwd01:~# date; pstree -t -sap 9276 Tue 05 May 2020 08:05:27 AM UTC systemd,1 └─rsyslogd-local,9276 -n -f /etc/rsyslog.d/rsyslog-local.conf ├─{

[rsyslog] Antwort: Re: oversizemsg.input.mode is invalid/unknown config option

2020-05-05 Thread Cyril Stoll via rsyslog
Hi David Thanks for looking into this. I didn't have a global section enclosed in brackets "()". I had a couple of global config options like the following and just added a new line with the oversizemsg.input.mode option. $WorkDirectory /var/lib/rsyslog $IncludeConfig /etc/rsyslog.d/*.conf $IMJo