[syslog-ng]time_reopen, continuous reconnects, and syslog-ng 1.4.10 - 1.4.12.

[Balazs Scheidler]

On Wed, Aug 15, 2001 at 03:44:56PM +0000, matthew.copeland@honeywell.com wrote:
> 
> I have been using syslog-ng 1.4.10 for some stuff at work for a while.  
> Now that we actually have our remote system up and running over
> frame-relay, our remote logging has got real important.  I have set the
> time_reopen option in my options field to 30 seconds, and I think that it
> tries to connect in 30 seconds when there is a network failue, but it
> doesn't continue to try reconnecting, or at least if it does connect, it
> won't spit any more data to the server until I HUP the client syslog-ng
> process.  Is there another option for making syslog continue trying to
> reconnect?  If not, do I just need to modify the io_callout stuff to make
> it do so, or do I have to play something else?  Is this just a bug or is
> the current behavior the expected behavior? 
> 
> I just don't like the idea of having to login to 250 systems just to HUP
> the syslog-ng process.  Even if I can script it.

This is a bug I didn't have time to track down. As it seems syslog-ng tries
to reconnect after connection failure, and sometimes after a successful
connection establishment just stops sending data, and also stops trying to
reconnect. Reading the source didn't reveal any information, and I couldn't
reproduce the problem myself.

-- 
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1