On Mon, Aug 18, 2003 at 11:16:16AM -0400, Erik Ivanenko wrote:
I am running version 1.5.13. All but 2 of 60 remote devices FAILED to reconnect when the power returned in Ontario. The cental logging host did not go off-line, as it was on emergency power.
I use the standard /etc/init.d/syslog-ng start scripts for the remote devices. They are all Linux machines. After issuing HUP to the central host, 9 of 60 connections are working.
Running "snoop" shows that the remote daemons have stopped trying to connect. I thought that syslog-ng was supposed to reconnect after such events?
Can anyone tell me what I can do to make these remote devices reconnect? Must I manually restart syslog-ng on each remote client?
not necessarily, though they were such bugs fixed during 1.5.x, I think you should upgrade to 1.6.0rc3 which is more stable. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1