Thanks David, I was unaware of the -N1 switch.
So that did lead me to find a missing ‘s’ on one of the rulesets for
queue.workerThreadMinimumMessages
Along with a couple other, smaller issues. Thanks!
From: David Lang
Date: Saturday, August 27, 2022 at 7:24 PM
To: Ben Hart via rsyslog
Cc: Ben
I’m getting the following error trying to test using Disk-Assisted in memory
queues. So the error is:
root@splunk:/var/spool/rsyslog# rsyslogd -N1
rsyslogd: version 8.2112.0, config validation run (level 1), master config
/etc/rsyslog.conf
rsyslogd: error during parsing file /etc/rsyslog.d/10-re
```
: 7479 7065 3d22 6f6d 6669 6c65 2220 4669 type="omfile" Fi
0010: 6c65 4372 6561 7465 4d6f 6465 3de2 809c leCreateMode=...
0020: 3036 3434 e280 9d0a 0644
```
seem to me like unicode quotes are used instead of ascii ones
bodik
On 8/29/22 9:25 PM, Ben
that sort of error typically means that somewhere prior to this line there are
mismatched quotes, sometimes far before.
David Lang
___
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
Yup, encountered that problem before which is why I included what I hoped would
be enough char/lines before the indicated one. I’ve stared at this in Nano so
long I’m going cross-eyed.
I don’t have anyone else who knows the format to even ask for their eyes..
From: David Lang
Date: Monday, Augu
when I have this problem, I just start at the beginning, search for double
quotes and step through the entire file (don't forget included files) and then I
do it again for single quotes.
I've had the actual error be 20+ lines earlier than the first reported issue.
David Lang
On Mon, 29 Aug 20
Generally we don’t use disk queues for omfile destinations.
Then, make sure you didn’t get “Microsofted” by curly quotes as opposed to
straight quotes. Can’t tell you how many times an M$ text editor has effed-up
a copied configuration by “prettying” up the quotes and dashes.
Regards,
> On Au
I’ve never had one (that I’ve found) quite that far ahead but good to know. So
why is it like this? Is there no way to programmatically lint these files?
*I think my issue earlier, and from yesterday were related to copy/paste from
outside applications. *sigh* I knew better than that.. I swear!
MacOS’s “Notes” app, but yeah, I did. ☹
From: John Chivian
Date: Monday, August 29, 2022 at 3:48 PM
To: rsyslog-users
Cc: David Lang , Ben Hart
Subject: Re: [rsyslog] Error with omfile and queue.filename syntax?
Generally we don’t use disk queues for omfile destinations.
Then, make sure you di
by the way, async writes on omfile are almost never a good idea, it adds an
extra queue between the omfile module and the write, and the locking on that
queue adds more overhead than the write would. The place it has some use is
where your output has a significant amount of processing (compresse
I've seen cases where run-on quotes or braces have fooled the parser quite
badly.
also, you should be aware that if you start rsyslog with rsyslogd -o
/path/to/file then file will contain the result of all the includes (i.e. the
way that rsyslog sees the configs) which can be very helpful in t
(Was reading through your article from 2014 on Syslog Perf)
No thank you for the advice.. that’s one reason I’m in the list! These rsyslog
servers are going to receive lots of messages from up two a couple dozen
sources each so I’m really wanting the best initial config I can scope. I know
twe
12 matches
Mail list logo
