[syslog-ng] Regular occurrences of Error writing control channel; error='Broken pipe (32)'

[Balazs Scheidler]

Hi,

this means that the client connecting to the control socket
/var/run/syslog-ng/syslog-ng.ctl (or similar, depending on your platform),
so this client disconnected while syslog-ng was still writing its result.

syslog-ng-ctl uses blocking I/O to query this socket, so it shouldn't do
this (unless it is killed by something on your system). is there anything
else that polls the control socket?

Bazis

On Tue, Mar 31, 2020 at 3:58 PM Ahmed Soyef <Soyef.Ahmed34 at homeoffice.gov.uk>
wrote:

> Hi All,
>
>
>
> We’ve been running syslog-ng and have recently started to see the above
> message in our logs. Sometimes running syslog-ng-ctl stats takes very long
> and results in similar error messages. Does anyone know why this may be the
> case? Do these errors cause any issues with log flows through the syslog-ng
> service? Do they cause issues with recording of stats?
>
>
>
> Kind regards,
>
>
>
> Soyef
> **********************************************************************
> This email and any files transmitted with it are private and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please return it to the address
> it came from telling them it is not for you and then delete it from your
> system.
> This email message has been swept for computer viruses.
> **********************************************************************
>
> ______________________________________________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20200331/a973725f/attachment.html>