Also do you have any warning messages like this in the fs log? Task was executed late by %d seconds (That should show up if the delay is in the scheduler, if the task runs >1s late). -Steve On 9 December 2010 11:27, Peter Olsson <peter.olsson@visionutveckling.se> wrote:
Hello everyone,
I have a question about the reliability of heartbeat events, it should be sent from FreeSWITCH every 20 seconds – right? If you look below in my log sample (from my own process), you can see that it comes 12:07:01, then 21, then 41, but after this it suddenly takes 31 seconds for it to show up (12:08:12). I’ve also done a Wireshark trace, and it shows the same thing – so it is really delayed from FS. The load at the time was zero calls, and the server itself was using maybe 5% CPU. After the delayed event it continues to show up every 20 seconds.
[2010-12-09 12:07:01] Received HEARTBEAT event - we're alive.
[2010-12-09 12:07:21] Received HEARTBEAT event - we're alive.
[2010-12-09 12:07:41] Received HEARTBEAT event - we're alive.
[2010-12-09 12:08:12] Received HEARTBEAT event - we're alive.
[2010-12-09 12:08:32] Received HEARTBEAT event - we're alive.
[2010-12-09 12:08:52] Received HEARTBEAT event - we're alive.
[2010-12-09 12:09:12] Received HEARTBEAT event - we're alive.
Should the HEARTBEAT event be 100% reliable, or could something cause a delay like this? This server is not on latest GIT, but it’s not more then one month old. I can debug this further myself, but I just want to know if it always should be triggered every 20 seconds, or if these events for some reasons might be delayed.
By the way – no clock skew or anything is detected on the machine, so that’s not causing it.
Thanks,
Peter
_______________________________________________ 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