the problem was that you had only defined one queue. you needed to define a
separate queue for each action.
David Lang
On Thu, 10 Oct 2013, Lucas Tobey wrote:
Date: Thu, 10 Oct 2013 14:18:46 -0500
From: Lucas Tobey <[email protected]>
Reply-To: rsyslog-users <[email protected]>
To: rsyslog-users <[email protected]>
Subject: Re: [rsyslog] OMRELP hangs when 2nd destination is down
Hi,
Thanks David! That worked. I'm not sure what I was missing in my action
queues.
Thanks again for the help!
-Lucas
On 10/01/2013 03:52 PM, David Lang wrote:
dealing with queues is MUCH easier if you are running 7.x than if you
are running earlier version.
with earlier versions, you need to add a number of queue related config
parameters before each output
$actionqueuetype= fixedarray
$actionqueuesize= 10000 (the number of messages to queue)
$actionqueuefilename = filename (if you want to spill to disk when the
memory queue is full)
so you would end up with something like:
$workdirectory /path/to/scratch/dir
$ModLoad omrelp
$actionqueuetype fixedarray
$actionqueuesize 10000
$actionqueuefilename filename1
*.* :omrelp:x.x.x.x:20514;RSYSLOG_ForwardFormat
$actionqueuetype fixedarray
$actionqueuesize 10000
$actionqueuefilename filename2
*.* :omrelp:y.y.y.y:20514;RSYSLOG_ForwardFormat
David Lang
On Tue, 1 Oct 2013, Lucas Tobey wrote:
Hey,
Can someone please give me a very simple/basic sample action queue
snippet? I've tried all sorts of options which 'should' be working, but
maybe I'm missing something when it comes to completing the action
queue. I want to rule out this being a bug or problem with the version.
I'm pretty sure I'm making correct action queues and still noticing this
problem.
Thanks!
-Lucas
On 09/19/2013 02:46 PM, David Lang wrote:
On Thu, 19 Sep 2013, Lucas Tobey wrote:
Hi,
I'm having a strange issue with Rsyslog. I have two destinations
configured for omrelp:
rsyslogd 5.8.11
$ModLoad omrelp
*.* :omrelp:x.x.x.x:20514;RSYSLOG_ForwardFormat
*.* :omrelp:y.y.y.y:20514;RSYSLOG_ForwardFormat
The problem is that when when one of the destinations is not reachable
like y.y.y.y, the other destination, x.x.x.x, does not receive any logs
as well. I'm thinking this might have something to do with the way RELP
works, but after waiting for quite some time for messages to show up on
x.x.x.x due to a timeout or other function I never did receive the
logs.
Is this something I can control? Is it a bug?
Yes, you have told rsyslog to deliver these messages in a reliable way,
and it will not complete delivering one message and go on to the next if
one of the boxes is down.
To decouple delivery of messages to the two destinations, you need to
create an action queue for each destination. When you do so, you can set
a bunch of parameters for the queue, including thresholds for discarding
messages and if you want the queue to include the ability to write to
disk.
David Lang
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.
