I need some help understanding how to control queue behaviour. The
goal is to write messages to a file locally and also forward the
messages to a remote rsyslog server. When the remote server is
unavailable I would like message to queue up and be processed when the
server is available again. I have a configuration that works this way
but has the unwanted side-effect that both local and forwarded
messages are being help until the remote server is available again. Here
is a configuration fragment.
*.debug action(type="omfile"
file="/var/log/messages"
template="FileFormat")
*.debug action(type="omfwd"
Target="logsink-dev.stanford.edu"
Port="10514"
Protocol="tcp"
queue.FileName="default_queue"
queue.size="4000000"
queue.HighWaterMark="100000"
queue.LowWaterMark="10000"
queue.MaxDiskSpace="2g"
queue.WorkerThreads="10"
queue.TimeoutEnqueue="120000"
action.ResumeRetryCount="-1"
template="ForwardFormat")
In this configuration there are three queues: the main queue, the
queue for the omfile action and the queue for the omfwd action.
Right? Why does the omfwd queue block the omfile queue? What am I
misunderstanding?
Bill
--
Bill MacAllister
Systems Programmer, Stanford University
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
