> -----Original Message-----
> From: [email protected] [mailto:rsyslog-
> [email protected]] On Behalf Of Christian Lete
> Sent: Wednesday, June 01, 2011 11:57 AM
> To: rsyslog-users
> Subject: Re: [rsyslog] High availability on rsyslog (cluster)
> 
> Hi David and Rainer,
> 
> I have just started playing around with corosync + pacemaker + drbd and so
> far have had a good impression of it. So the next week, I would like to
play
> around with some OCF scripts and see If I can create this for rsyslog and
> would be glad to submit it to the project if this works fine :)

Excellent. Just let me know if you need some help in form of a module or
such...

Rainer

> 
> Thanks a lot both for your help and hints on how to supervise this service.
> 
> Regards!
> 
> Christian
> 
> On 1 June 2011 10:06, Rainer Gerhards <[email protected]> wrote:
> > Hi David, Christian,
> >
> > I finally have found time to look into the provided links. This looks
> > indeed very simple from an rsyslog PoV. However, I get the feeling
> > that I myself may not be the best person to do the majority of work,
> > as to develop the actual OCF scripts access to a test cluster, and
> > experience with it (!), seems to be very beneficial. So I wonder if
> > anyone of you would be interested in helping to get this going (with
> > the scripts becoming part of the regular rsyslog release).
> >
> > As far as I understand, I would need to implement some facility inside
> > rsyslog that can be used to check its health by the monitor script. Or
> > would it even be an alternative for the monitor script to just check
> > if the rsyslog process to be monitored is in the process list?
> >
> > Any comments, advise, collaboration is deeply appreciated.
> >
> > Rainer
> > PS: just in case: tomorrow is a public holiday over here, and I may
> > leave for a long weekend. I still thought I get this effort kicked off...
> >
> >> -----Original Message-----
> >> From: [email protected] [mailto:rsyslog-
> >> [email protected]] On Behalf Of [email protected]
> >> Sent: Tuesday, May 24, 2011 8:13 AM
> >> To: rsyslog-users
> >> Subject: Re: [rsyslog] High availability on rsyslog (cluster)
> >>
> >> take a look at
> >>
> >> http://linux-ha.org/wiki/Resource_Agents
> >>
> >> and
> >>
> >> http://www.linux-ha.org/doc/dev-guides/ra-dev-guide.html
> >>
> >> David Lang
> >>
> >> On Tue, 24 May 2011, Rainer Gerhards wrote:
> >>
> >> > Date: Tue, 24 May 2011 08:09:28 +0200
> >> > From: Rainer Gerhards <[email protected]>
> >> > Reply-To: rsyslog-users <[email protected]>
> >> > To: rsyslog-users <[email protected]>
> >> > Subject: Re: [rsyslog] High availability on rsyslog (cluster)
> >> >
> >> > Thx -- sounds interesting and probably not too much work to do...
> >> >
> >> > Rainer
> >> >
> >> >> -----Original Message-----
> >> >> From: [email protected] [mailto:rsyslog-
> >> >> [email protected]] On Behalf Of [email protected]
> >> >> Sent: Tuesday, May 24, 2011 8:08 AM
> >> >> To: rsyslog-users
> >> >> Subject: Re: [rsyslog] High availability on rsyslog (cluster)
> >> >>
> >> >> take a look at linux-ha
> >> >>
> >> >> It's a framework to manage HA (including active/active load
> >> >> sharing, quorums, etc)
> >> >>
> >> >> it extends the traditional init.d startup scripts to also include
> >> >> a 'status' call to tell if the service is active or not. the
> >> >> framework calls this service periodically and if the service
> >> >> fails, it does a failover.
> >> >> With the correct configuration (and software), it can do
> >> >> sub-second failover.
> >> >>
> >> >> David Lang
> >> >>
> >> >>
> >> >>   On
> >> >> Tue, 24 May 2011, Rainer Gerhards wrote:
> >> >>
> >> >>> David and all,
> >> >>>
> >> >>> are you aware of any high availability APIs that would enable
> >> >>> rsyslog
> >> >> to do
> >> >>> some kind of automatic failover in a cluster environment? I have
> >> >> never
> >> >>> specifically programmed for that and wonder if there are any
options.
> >> >>>
> >> >>> Rainer
> >> >>>
> >> >>>> -----Original Message-----
> >> >>>> From: [email protected] [mailto:rsyslog-
> >> >>>> [email protected]] On Behalf Of [email protected]
> >> >>>> Sent: Tuesday, May 24, 2011 12:30 AM
> >> >>>> To: rsyslog-users
> >> >>>> Subject: Re: [rsyslog] High availability on rsyslog (cluster)
> >> >>>>
> >> >>>> depending on how active your logging is, you could watch the
> >> >>>> logs
> >> >> and
> >> >>>> say
> >> >>>> that if you don't receive any logs for 1 min (or whatever time
> >> >>>> is approprate), somthing is wrong.
> >> >>>>
> >> >>>> you could also generate known UDP logs to yourself and alert if
> >> >>>> they don't show up.
> >> >>>>
> >> >>>> David Lang
> >> >>>>
> >> >>>>   On Mon, 23 May 2011, Christian Lete wrote:
> >> >>>>
> >> >>>>> Hi,
> >> >>>>>
> >> >>>>> I have a small question,  I would need to setup an rsyslog
> >> >>>>> receiver/forwarder, listening on udp port, since some clients,
> >> >>>>> only support this option. I would need this service to be
> >> >>>>> highly available(I don't want to have two machines and having
> >> >>>>> duplicated information), but since this udp, I can't be for
> >> >>>>> sure if the
> >> >> service
> >> >>>>> is running fine. What I thought is to indirectly check it, by
> >> >> having
> >> >>>>> another port listening on tcp and checking the tcp service, if
> >> >>>>> the service is not running on tcp I would assume the whole
> >> >>>>> system is
> >> >> down
> >> >>>>> and would failover to the other instance of the cluster, that's
> >> >>>>> the only way I could think of, do you currently have another way?
> >> >>>>>
> >> >>>>>
> >> >>>>> thank you very much,
> >> >>>>>
> >> >>>>> Regards,
> >> >>>>>
> >> >>>>> Christian
> >> >>>>> _______________________________________________
> >> >>>>> 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
> >> >>>
> >> >> _______________________________________________
> >> >> 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
> > _______________________________________________
> > 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

Reply via email to