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

[Evan Rempel]

This does NOT need to be done for every message, only when a TCP connection is
opened. Under normal operation, the TCP connection stays open and messages flow
without any hostname resolution. When the connection is dropped, the hostname
is resolved again and a new connection attempt is made. If you leave the
hostname resolution to the open socket call, rather than resolving the hostname
within syslog-ng, this would automatically happen as the AS system call to
open the socket would resolve the name again.

Evan.

Paul Robert Marino wrote:
> I don't realy see how this is a syslog-ng issue
> Quite simply the only way to fix this is to have syslog-ng resolve the 
> host name to an ip address for every message. This is an impractical 
> method to handle a rare occurence. This kind of change woul add a lot fo 
> needless overhaed to every message. Frankly if i change the ip address 
> of my syslog server i expect that I will have to restart syslog on all 
> of my hosts that relay to it.
> On Sat, 23 Feb 2008 1:11 am, bugzilla at bugzilla.balabit.com wrote:
> 
>>https://bugzilla.balabit.com/show_bug.cgi?id=19
>>
>>           Summary: syslog-ng 2.0.x can not follow a change of IP at 
>>target
>>                    syslog server
>>           Product: syslog-ng
>>           Version: 2.0.x
>>          Platform: PC
>>        OS/Version: Linux
>>            Status: NEW
>>          Severity: major
>>          Priority: unspecified
>>         Component: syslog-ng
>>        AssignedTo: bazsi at balabit.hu
>>        ReportedBy: erempel at uvic.ca
>>Type of the Report: enhancement
>>   Estimated Hours: 0.0
>>
>>
>>If the IP address of the destination for syslogging is changed, then 
>>all sending syslog-ng servers must be reloaded to
>>figure out that the address has changed, even if the IP name has not 
>>changed.
>>
>>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.
>>
>>The "reopen" logic should be changed to resolve the IP address of the 
>>hostname provided in the configuration file.
>>Hopefully the reopen process should be relatively rare, and no 
>>significant load will be placed on the DNS servers
>>during normal operation.
>>
>>
>>--
>>Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
>>------- You are receiving this mail because: -------
>>You are watching all bug changes.
>>_______________________________________________
>>syslog-ng maillist  -  syslog-ng at lists.balabit.hu
>>https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
> 
> ___________________________________________
> The average person does a lot of work in the name of laziness!
> Save youre self the effort by doing it right the first time.
> Do it with free speech software.
> _______________________________________________
> syslog-ng maillist  -  syslog-ng at lists.balabit.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
>