I actually recommend not managing rsyslog through pacemaker, just have it running all the time on both machines.

This will protect you against machine failure, but not a rsyslog crash, monitoring that rsyslog is healthy is an 'interesting' task (what is rsyslog _supposed_ to be doing with your configuration, how can you tell if it's really working or not, especially when delivering to remote machines, etc)

Now, I've been running HA pairs of syslog servers since ~2000, with 21 rsyslog pairs since ~2006 and I think I've had less than a half dozen cases where rsyslog has stopped on my, and that's with my running bleeding edge rsyslog (compiled from git because there wasn't even a dev release for much of the time)

So I don't consider monitoring rsyslog as such that high a priority :-)

so for your pacemaker config, just have it manage an IP address between the systems and point all the clients at that IP

David Lang


On Thu, 24 Oct 2013, robert s wrote:

Hello Everyone,

So after a little trial and error, I managed to install pacemaker to
my rsyslog servers. I am obviously not familiar with it, but I have
been doing some research into configuring it. I am not sure this is
the forum where I need to post this question and if its not I
apologize, but I was curious if there was a resource for rsyslog to be
managed through pacemaker, and also David I think you suggested
pacemaker and clusterip to manage the vip on these servers, could you
possibly elaborate on your suggestion if you don't mind?

Thanks for the help

Robert


On Mon, Oct 21, 2013 at 2:16 PM, Pavel Levshin <[email protected]> wrote:

It hardly ever existed. It is fairly trivial if you are familiar with
keepalived or any other clustering suite. But you need to arrange checks
around your rsyslogs to detect every possible failure. Those checks will
strongly depend on your setup.

If the only failure to be considered is full shutdown or disconnection of a
server, then you do not need to configure anything special for rsyslog in
keepalived. Then, you can use any howto on keepalived.


--
Pavel Levshin

21.10.2013 19:44, robert s:

Hello all,

I was curious if you happen to know of any documentation to configure
keepalived with rsyslog?

Robert


On Tue, Oct 15, 2013 at 1:14 AM, David Lang <[email protected]> wrote:

On Mon, 14 Oct 2013, robert s wrote:

Is there a way rsyslog can prefix the host name how you mentioned, I
was reading about the DynaFile, woudl I need to create a template and
append below text to it?

/var/log/%HOSTNAME%/%programname%.log


if you are already using Dynafile you can do:

/var/log/%hostname%/%$myhostname%-%programename%.log

this way the two servers writing to disk will write to different files.

David Lang


Robert


On Sat, Oct 12, 2013 at 12:18 AM, David Lang <[email protected]> wrote:

yes.

note that if you have two programs writing to the same file on NFS, you
will
have headaches, so do something like prefixing the filename with the
hostname of the server writing them.


David Lang

On Fri, 11 Oct 2013, robert s wrote:

Date: Fri, 11 Oct 2013 13:44:01 -0400
From: robert s <[email protected]>
Reply-To: rsyslog-users <[email protected]>
To: rsyslog-users <[email protected]>
Subject: Re: [rsyslog] redundant rsyslog


Oh ok, and just set up the same rsyslog configuration on both servers
right?

Robert


On Fri, Oct 11, 2013 at 1:03 PM, David Lang <[email protected]> wrote:


you would setup rsyslog on both machines, then install something like
pacemaker or keepalived and assign the cluster a third IP address
that
pacemaker or keepalived would move from one machine to the other when
one
fails.

David Lang


  On Fri, 11 Oct 2013, robert s wrote:

Hello Everyone,

I wanted to ask your input in what would be the best way to have
redundancy/failover for rsyslog,

I have two available servers that rsyslog can be installed into
them.
I would like to be able to have both servers listening to messages
coming in from either a single ip or a pool of ips.

I would like them to be configured in an active/passive
configuration
where if one server malfunctions the second server will take over
and
keep logging.

Does rsyslog have the capability to do fail over?

Robert
_______________________________________________


_______________________________________________
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.

Reply via email to