most likely cause would be connecting a socket then not regularly reading
from it causing the buffer to fill up.
any event socket connection must select on the socket and do regular read
attempts or all the events will accumulate on the server side until some
sanity check is reached and it begins
Anthony, thank you very much for your response. The daemon that was
reading the events froze, so apparently that was the source of the
problem and your explanation fits perfectly.
On Mon, Dec 28, 2009 at 12:47 PM, Anthony Minessale
anthony.miness...@gmail.com wrote:
most likely cause would be
I just got into the fs cli and when I ran a 'show calls' I got the
following message:
2009-12-24 09:58:20.058365 [CRIT] mod_event_socket.c:337 Lost 8456 events!
What does this mean? does it mean the event_socket did not report 8456
events? Why could this happen?
The answer to this is pretty
