[syslog-ng] help- Problem with TCP Based Centralized Log Server using Syslog-ng

Balazs Scheidler bazsi at balabit.hu
Tue Oct 31 11:59:20 CET 2006

On Tue, 2006-10-31 at 14:52 +0530, Padmanabhan, Rajeesh (GE Healthcare)
>  Hi
> Im trying to setup a centralized, TCP Based Log Server using
> Syslog-ng. Syslog-ng server stops accepting logs from clients
> intermediatley.
> It works again, once i restart the syslog-ng server. Im getting
> following error messages from clients.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Oct 18 10:29:28 System1 syslog-ng[11745]: Connection broken;
> time_reopen='60'
> Oct 18 15:06:26 RADIUM syslog-ng[4999]: io.c: do_write: write() failed
> (errno 32), Broken pipe
> Oct 18 15:06:26 RADIUM syslog-ng[4999]: pkt_buffer::do_flush(): Error
> flushing data
> Oct 18 15:06:26 RADIUM syslog-ng[4999]: Connection broken to
> AF_INET(, reopening in 10 seconds
>  syslog-ng[13843]: Connection failed; error='Connection refused
> (111)', time_reopen='60
>  syslog-ng[302]: Error connecting to remote host
> AF_INET(, reattempting in 10 seconds
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Please help me...

I'm sorry but you need to give further details, like OS, architecture
syslog-ng version that you used.

When did you receive the messages above? after restarting syslog-ng or
was this the reason why you restarted syslog-ng in the first place?

Because restarting syslog-ng naturally breaks existing connections and
there's a small race of opportunity while the port is closed and clients
try to connect to it, in this case you get connection refused.

So all in all we'd need more information in order to help you.


More information about the syslog-ng mailing list