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 to throw them away, the fist time there is room in this buffer again (when you consume some from the socket leaving space in the queue) it will report how many have been lost since the last read. 

One way to cause this would be suspend fs_cli with ctl-z and bring it back to the foreground after some time.


On Thu, Dec 24, 2009 at 7:05 AM, Nicolas Brenner <nicolas@medularis.com> wrote:
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 critical to me, as I make and monitor
calls through the socket.


Thanks for your help!


Nicolas

_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:+19193869900