[syslog-ng] [EXTERNAL] Re: Failover/Hi Availability

Faine, Mark R. (MSFC-IS40)[NICS] mark.faine at nasa.gov
Fri Jan 15 15:51:08 UTC 2021

For now it's just an idea for an improved syslog-ng infrastructure to support Splunk.

Not on the same machine but multiple, at least two servers, each with their own syslog-ng instance, receiving data from dozens of hosts (the same hosts) and yes writing to a shared NFS file system.

The only substantial problem I have left in the (as of now) hypothetical scenario is that I need them all to write to the same location so that if one goes down we don't have to do any manual switching of any sort and none of the data fails to be indexed by Splunk.


From: syslog-ng <syslog-ng-bounces at lists.balabit.hu> On Behalf Of Attila Szakacs (aszakacs)
Sent: Friday, January 15, 2021 03:07
To: Syslog-ng users' and developers' mailing list <syslog-ng at lists.balabit.hu>
Subject: [EXTERNAL] Re: [syslog-ng] Failover/Hi Availability

Hi Mark,

Please elaborate a bit more about your architecture. Relevant config parts are also appreciated.

Are there two syslog-ng servers running on the same machine?
Or is it just one syslog-ng instance with two different log sources (on different ports for example), and there is a host which sends to both log sources?
Maybe there are 2 different machines running their own syslog-ng, but using a network shared file system?



From: syslog-ng <syslog-ng-bounces at lists.balabit.hu<mailto:syslog-ng-bounces at lists.balabit.hu>> on behalf of Faine, Mark R. (MSFC-IS40)[NICS] <mark.faine at nasa.gov<mailto:mark.faine at nasa.gov>>
Sent: Thursday, January 14, 2021 9:21 PM
To: Syslog-ng users' and developers' mailing list <syslog-ng at lists.balabit.hu<mailto:syslog-ng at lists.balabit.hu>>
Subject: [syslog-ng] Failover/Hi Availability

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

If I have two Syslog-ng servers receiving logs from the same source and writing to the exact same file system destination,  is there a way to do this without running into issues with the two instances clobbering the files or file locking issues?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20210115/270c38e8/attachment-0001.html>

More information about the syslog-ng mailing list