[rsyslog-notify] Forum Thread: debug missing queue detail? - (Mode 'post')

[noreply at adiscon.com]

User: atticus 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=26690#p26690

Message: 
----------
I am running rsyslogd -dn (while rsyslog is already running, so maybe this
is flawed already) but looking at a v8 example from Rainer's note on
troubleshooting, he showed an example where you could clearly see the
system "took" the queuing parameters he had entered.
In my .conf, I have a ruleset with it's own queue, and some omfwd actions
with their own action queues.  However, I only see the main thread in my
debug outputs.  I would appreciate if there's something you all can glean
out of the debug listing below to give some ideas to go back to the .conf
file to fix.

Again, many thanks for your thoughts and comments.

Debug output of relating to four omfwd


9737.677675443:main thread    : ruleset 0xa89da0: ruleset fwdlocal assigned
parser list:
9737.677680395:main thread    : ruleset 0xa8d910: rsyslog ruleset fwd1:
9737.677685223:main thread    : ACTION 14
[builtin:omfwd:action(type="builtin:omfwd" ...)]
9737.677689579:main thread    : ACTION 15
[builtin:omfwd:action(type="builtin:omfwd" ...)]
9737.677694006:main thread    : ACTION 16
[builtin:omfwd:action(type="builtin:omfwd" ...)]
9737.677698376:main thread    : ACTION 17
[builtin:omfwd:action(type="builtin:omfwd" ...)]
9737.677702677:main thread    : ACTION 18
[builtin:omfile:action(type="builtin:omfile" ...)]
9737.677706793:main thread    : ruleset 0xa8d910: ruleset fwd1 assigned
parser list:

ruleset(name="ruleset1"
queue.type="LinkedList"
queue.filename="rulese1tq1"
queue.saveonshutdown="on"
queue.MaxDiskSpace="1g") {
action(type="omfwd"
target="hosta1.com"
protocol="tcp"
port="6514"
.
.
.
similar queue commands.