The rules should have been triggered. I blocked (via firewall) the
primary syslog server, and tcpdumps shows that it just keeps sending to
it, even though it could not connect. The fact that the rules are not
being triggered means that either somehow the config is wrong, or there
is a bug. How does rsyslog determine the "upness" of the server it tries
to connect to?
On 6/14/11 6:05 AM, Rainer Gerhards wrote:
Sorry, I have been swamped with another issue, which took up all my time. I
have now reviewed the log but it looks like it does not contain any instance
where the rules are actually triggered. Could you create such a one?
Thanks,
Rainer
-----Original Message-----
From: [email protected] [mailto:rsyslog-
[email protected]] On Behalf Of Rory Toma
Sent: Wednesday, June 08, 2011 10:17 PM
To: rsyslog-users
Subject: Re: [rsyslog] Question on host failover
On 6/2/11 2:19 PM, Rory Toma wrote:
On 6/2/11 3:32 AM, Rainer Gerhards wrote:
Mmhhh.. can you post a complete debug log (maybe via a website like
filebin)?
Thx,
Rainer
Let me know when you've downloaded this file and I'll reset the ACL, thx.
http://www.colinburns.com/downloads/darwin0.bz2
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
Any update on this?
thx
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
