[syslog-ng]syslog-ng TCP bug

[Nate Campi]

Balazs,

I've posted in the past about how my loghost that accepts logging only via
TCP is unstable while my loghosts that collect only via UDP are very
stable. Well I've collected some new data that may be helpful.

Every hour at exactly 30 minutes past the hour (7:30, 8:30, 9:30,
etc) syslog-ng dies with the error:

syslog-ng: io.c:172: io_iter: Assertion `i < nfds' failed.

Then at 31 minutes past the hour my "syslog-ng.check" script (running from
cron every minute) sees that syslog-ng isn't running and restarts
it. syslog-ng runs fine for another hour, then at 30 minutes past the next
hour it dies again, and the cycle continues.

I'm not a C coder so I have no idea where in the source to look, so I
thought I'd just post my findings here. 

Thanks for any help.

OBTW I'm running syslog-ng 1.4.5 with libol 0.2.18
--
Nate Campi
"If we knew what we were doing, it wouldn't be called research." - Einstein