Hello,

Can you share your syslog-ng version, ivykis version, and a minimal syslog-ng configuration that we can use to reproduce the problem?

Now I just have general ideas. If you are using ivykis < 0.39, then it would be worth updating. There was a problem that timers registered with negative timeout could starve the ivykis loop.

If you are using old version of syslog-ng, it would worth updating that as well. Depending on your configuration, there may be fixes that can affect this (for example deadlock in patterndb).

If you are using "syslog-ng-ctl stats" for sake of healthcheck: you can try to use "syslog-ng-ctl show-license-info" (available sinse syslog-ng 3.18) instead, which uses less resource.

Br,

Antal

From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> on behalf of Faine, Mark R. (MSFC-IS40)[NICS] <mark.faine@nasa.gov>
Sent: Tuesday, April 21, 2020 16:32
To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu>
Subject: [syslog-ng] syslog-ng-ctl: EOF occurred while reading control socket

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

I am seeing the message "EOF occurred while reading control socket" intermittently when using the syslog-ng-ctl command. Is there something misconfigured or anything I can do to prevent this?

Thanks,

-Mark