[Bug 169] New: Feature Request - reconnect network also resolve dns name
https://bugzilla.balabit.com/show_bug.cgi?id=169 Summary: Feature Request - reconnect network also resolve dns name Product: syslog-ng Version: 3.3.x Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: erempel@uvic.ca Type of the Report: --- Estimated Hours: 0.0 When a network connection is dropped the destination name should be resolved via DNS prior to the reconnect. Every couple of years to renew the hardware supporting our core syslog service we move the IP name to a new host. The desired process is; 1. Build a new host and ensure that syslog-ng is running correctly. 2. Change the DNS for our central syslog server to the address of the new server. 3. Restart the syslog-ng service on the old syslog server. 4. All of the clients will loose the connection to the old syslog server. 5. All of the clients will reconnect to the *IP Name* in their configuration files. 6. Monitor the old syslog server to determine any hosts that have not made the transition. What really happened in step 5 was that all of the client reconnected to the old syslog server :-( To accomplish the switch over I had to visit 450 servers and manually restart the syslog service on the client. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=169 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |algernon@balabit.hu AssignedTo|bazsi@balabit.hu |algernon@balabit.hu --- Comment #1 from Gergely Nagy <algernon@balabit.hu> 2012-03-30 13:40:05 --- I have a patch that corrects another issue, that might help here too, although it's not a complete solution (yet): with the patch, when reconnecting, syslog-ng will try to resolve the hostname again if a previous connect failed. So, if the clients would have the patched syslog-ng, and you changed the IP of the loghost, and shut down syslog-ng on the server, the clients would loose connection, try to reconnect, fail, then try again, this time resolving the name again, and find the new server. It's reasonably easy to extend this patch to work as you described, too, but it might have unwanted side-effects, which I want to uncover first. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=169 Patrick <bugzilla.syslogng@feystorm.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla.syslogng@feystorm.n | |et --- Comment #2 from Patrick <bugzilla.syslogng@feystorm.net> 2013-04-16 19:31:05 --- Is this issue still present in current versions of syslog-ng? The last comment over a year ago made allusions that a fix was in progress, but I can't find anything indicating if it was completed or not. Right now this issue is biting me hard as I have syslog-ng logging to some servers sitting behind Amazon's EC2 load balancers (ELB). Amazon's ELB can change IP addresses at any time, so I need to have syslog-ng capable of handling this. Currently I'm running on 3.3.4, the version in ubuntu 12.04, but can upgrade to a later version if this is fixed. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=169 --- Comment #3 from Gergely Nagy <algernon@balabit.hu> 2013-04-17 09:57:42 --- Nope, this is not done yet, unfortunately. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=169 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bazsi@balabit.hu --- Comment #4 from Balazs Scheidler <bazsi@balabit.hu> 2013-04-23 19:43:33 --- Hmm... I think this should work with 3.4 at least this change should do it: commit 775af1b8ead493198c1e3cea1edf64909d8a72b2 Author: Balazs Scheidler <bazsi@balabit.hu> Date: Sat Oct 29 20:15:35 2011 +0200 afsocket: handle DNS failures as if it was a connection failure Instead of preventing the startup completely. Reported-By: Heiko Gerstung <heiko@am-anger-1.de> Signed-off-by: Balazs Scheidler <bazsi@balabit.hu> -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=169 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #5 from Gergely Nagy <algernon@balabit.hu> 2013-10-10 12:05:59 --- This is apparently still an issue, and there's a growing interest in making this happen. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
bugzilla＠bugzilla.balabit.com