The one I gave you was set up to fail over.
I blocked port 110, so it should failover to 143. It's not. It's as if
it never gets to the rule, or it isn't parsing it. I watch my tcpdump
and it just keeps retrying on port 110. I gave you the debug log with
this setup and it never gets to the failover rule, which, is probably
the problem.
So, given that, what do I do?
On 6/16/11 11:09 PM, Rainer Gerhards wrote:
Thanks for the feedback. So I now need a debug log. Please make sure that it
includes both the startup as well as a sample message flow where the problem
occurs.
Rainer
-----Original Message-----
From: Rory Toma [mailto:[email protected]]
Sent: Friday, June 17, 2011 12:51 AM
To: Rainer Gerhards
Cc: rsyslog-users
Subject: Re: [rsyslog] Question on host failover
On 6/15/11 11:28 PM, Rainer Gerhards wrote:
-----Original Message-----
From: Rory Toma [mailto:[email protected]]
Sent: Wednesday, June 15, 2011 10:58 PM
To: Rainer Gerhards
Cc: rsyslog-users
Subject: Re: [rsyslog] Question on host failover
So, if I check out the bug, the syntax that you have marked as
"works"
is what does *not* work for me.
Wait until that bug is fixed and let's see if what you see is a side-
effect
or not. If it doesn't sole the issue, we can always look at the next
one...
Rainer
I tried out the two patches that you posted on the bug. No change for
me.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
