On 17/06/2013, at 11:44 PM, Balazs Scheidler <bazsi77@gmail.com> wrote:

the peer has terminated the connection in which case syslog-ng automatically reconnects. these lines should contain more information :(

anyway, you can find out what happens by tcpdumping the network interface and looking for RST packets.

Thanks Bazsi! will do. The only connection is to another machine also running syslog-ng. Any hints on what might cause it to reset the connection. There is not a huge load being forwarded — order of tens of logs/sec. R

On Mon, Jun 17, 2013 at 1:33 AM, Russell Fulton <r.fulton@auckland.ac.nz> wrote: getting these errors at a rate of several per second but I can't figure out what is causing them:

Jun 16 03:45:01 s_self@itslogprd01.its.auckland.ac.nz syslog-ng[31159]: I/O error occurred while reading; fd='758', error='Connection reset by peer (104)' Jun 16 03:45:01 s_self@itslogprd01.its.auckland.ac.nz syslog-ng[31159]: I/O error occurred while reading; fd='808', error='Connection reset by peer (104)' Jun 16 03:45:01 s_self@itslogprd01.its.auckland.ac.nz syslog-ng[31159]: I/O error occurred while reading; fd='906',

we have one network destination which is a tcp connection and which appears to be fine. No errors on the other end and stats show now dropped packets.

Russell ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq

-- Bazsi ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq