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