[rsyslog] Redundant rsyslogs and satabase interaction
david at lang.hm
Fri Jan 25 01:03:51 CET 2013
I use heartbeat to manage an IP address that moves from one machine to the
other. That way only one box at a time is recieving logs (and inserting them
into the database), but if a box fails, the other box will take over (you can
configure the failover time down to subsecond if you need to, but it takes good
network infrastructure to support that)
On Thu, 24 Jan 2013, Jacob Steinberger wrote:
> Date: Thu, 24 Jan 2013 14:46:24 -0600
> From: Jacob Steinberger <trefalgar at realitybytes.net>
> Reply-To: rsyslog-users <rsyslog at lists.adiscon.com>
> To: rsyslog-users <rsyslog at lists.adiscon.com>
> Subject: [rsyslog] Redundant rsyslogs and satabase interaction
> Before I reinvent the wheel ...
> Has anyone worked out a method to configure two rsyslog agents on different
> servers, writing to the same database at the same time?
> In other words, if you have two rsyslog agents on two servers with all your
> devices reporting to both (in case one fails), you don't want to end up with
> duplicate entries in your database for everything.
> A cold stand-by, with the second rsyslog process not running seems like a
> poor (but possible) solution.
> Using database features, like UPDATE ON DUPLICATE KEY might work, depending
> on what you're inserting and if you can generate a unique key per insert and
> aren't relying on an incremental value.
> A feature that would be interesting is if rsyslog-backup would ping
> rsyslog-primary and if it's not available, to start logging at that point
> (otherwise, remain idle).
> Just curious if others are doing this, and if you found a sharable solution.
> rsyslog mailing list
> 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.
More information about the rsyslog