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

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Sat Feb 23 07:11:20 CET 2008


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.


More information about the syslog-ng mailing list