[syslog-ng] [Bug 19] New: syslog-ng 2.0. x can not follow a change of IP at target syslog server

[Evan Rempel]

On Sun, 24 Feb 2008, Ed Wildgoose wrote:

> Date: Sun, 24 Feb 2008 00:04:27 +0000
> From: Ed Wildgoose <lists at wildgooses.com>
> Reply-To: Syslog-ng users' and developers' mailing list
>     <syslog-ng at lists.balabit.hu>
> To: Syslog-ng users' and developers' mailing list <syslog-ng at lists.balabit.hu>
> Subject: Re: [syslog-ng] [Bug 19] New: syslog-ng 2.0. x can not follow a
>     change of IP at target syslog server
> 
>
>> We recently moved one of our centralized syslog servers to a different building, resulting in a different network address.
>> We took great pains (it was actually easy, but required planning) to maintain the IP name of the syslog server, but
>> all of the sending hosts required a syslog-ng reload to resolve the IP name in the configuration file
>> to the new IP address.
>>
>
> Standard procedure here is to setup the old machine to forward to the
> new machine (netfilter rules, etc).  Then you can go around restarting
> your other servers at your leisure.
>
> Works the same for any service - smtp, web, etc, etc

That's great but what if you have 4,000 or more machines?
If the product can handle this move easily, then I would classify it
amoung the few "enterprize" applications that exist.

Products that we use that handle this gracefully are
- our enterprise backup solution
- Corporate database applications
- Identity management
- Web clustering

I would like to have log collecting in the enterprise class.

Evan.