all of those lines are telling rsyslog that if it matches the filter and
writes it to the file that it should stop processing that message.
As a result, anything that gets written to a local file will stop processing
before it gets down to your udp sending action
David Lang
On Thu, 17 Aug
Here it is:
module(load="imfile")
module(load="imuxsock")
module(load="imklog")
module(load="imjournal")
timezone(id="UTC")
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
$RepeatedMsgReduction on
$FileOwner syslog
$FileGroup adm
global(net.enableDNS="off"
By the way, that's a good case that shows why it really pays to use
new-style config for more complex things.
If new style would have been used, rsyslog would have emitted an error message.
Just to mention this. Glad it worked out.
Rainer
El jue, 17 ago 2023 a las 12:29, Roman Möller via
Hi all,
just wanted to give you a final update on the case.
There was no problem with rsyslog, it was a configuration error on my end.
The reason for the observed behavior was that there was another *.conf file
from a different user of the system stored in /etc/rsyslog.d/ with a different
4 matches
Mail list logo
