> -----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 > > On 6/15/11 8:16 AM, Rainer Gerhards wrote: > >> -----Original Message----- > >> From: Rory Toma [mailto:[email protected]] > >> Sent: Wednesday, June 15, 2011 4:10 PM > >> To: Rainer Gerhards > >> Cc: rsyslog-users > >> Subject: Re: [rsyslog] Question on host failover > >> > >> So, how do I make such a log? > > http://www.rsyslog.com/doc/troubleshoot.html > > > >> I turned on the debug option and generated > >> messages. What else do I need to do? > > Just make sure that failover kicks in. But the good news is that I am > > probably able to reproduce it myself. I guess this is the bug: > > > > http://bugzilla.adiscon.com/show_bug.cgi?id=270 > > > > So I do not need anything at this moment. I suggest to subscribe > yourself to > > the bug tracker. > > > > Rainer > >> On 6/14/11 11:42 PM, Rainer Gerhards wrote: > >>> The "upness" is determined by connecting. But I really can't say > much > >>> more until I get a log that was recorded while the problem > happened. > >>> The log you provided contains just the startup but no message flow > at > > all. > >>> Rainer > >>> > >>>> -----Original Message----- > >>>> From: Rory Toma [mailto:[email protected]] > >>>> Sent: Wednesday, June 15, 2011 12:49 AM > >>>> To: rsyslog-users > >>>> Cc: Rainer Gerhards > >>>> Subject: Re: [rsyslog] Question on host failover > >>>> > >>>> 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
