[syslog-ng]syslog-ng 1.5.26 dies after remote logging host goes down

[Balazs Scheidler]

On Fri, Feb 28, 2003 at 09:48:28AM +0100, Peter Bieringer wrote:
> Hi,
> 
> looks like a bug, can't be a feature...
> 
> 
> I have defined a remote destination like:
> 
> destination d_remotelog { udp( "192.168.1.1" port(514) ) ;};
> 
> And use it like
> log {
>         source(s_local);
>         filter(f_emerg);
>         destination(d_all);
>         destination(d_remotelog);
> };
> 
> 
> Today, I've rebooted "remotelog" host, and detect, that the syslog-ng
> daemon on the other box dies without any "die now" notice.
> Last log entries:
> 
> Feb 28 09:12:38 host syslog-ng[28338]: STATS: dropped 0
> Feb 28 09:19:47 host syslog-ng[28338]: Connection broken to
> AF_INET(192.168.1.1.50:514), reopening in 60 seconds

can you show an strace of this? I've tried to reproduce the problem without
success:

io_iter(): POLLHUP on inactive fd!
Marking fd 4 for closing.
Connection broken to AF_INET(192.168.131.2:2001), reopening in 60 seconds
Closing fd 4.
Read EOF on fd 5.
Marking fd 5 for closing.
AF_INET client dropped connection from 127.0.0.1, port 56879
Closing fd 5.
....
io.c: connecting using fd 4
connecting fd 4 to inetaddr 192.168.131.2, port 2001
io.c: Preparing fd 4 for writing
io.c: do_write: write() failed (errno 111), Connection refused
pkt_buffer::do_flush(): Error flushing data
Marking fd 4 for closing.
Connection broken to AF_INET(192.168.131.2:2001), reopening in 60 seconds
Closing fd 4.

so it definitely reattempts connecting to the remote host. this was my configuration file:

source src { tcp(port(2000)); internal(); };

destination dst { udp("192.168.131.2" port(2001)); };

log { source(src); destination(dst); };


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