[Freeswitch-users] Virtual Migration Detected! Syncing Clock

Pedja Delic pedja at emazu.com
Mon Oct 25 15:42:53 PDT 2010


Hello,
I faced this problem 2 times during test up to 20 concurrent calls:
2010-10-24 23:20:31.552414 [CRIT] switch_time.c:755 Virtual Migration 
Detected! Syncing Clock
2010-10-24 23:20:47.988228 [CRIT] switch_time.c:755 Virtual Migration 
Detected! Syncing Clock
2010-10-24 23:20:52.744154 [CRIT] switch_time.c:755 Virtual Migration 
Detected! Syncing Clock
2010-10-24 23:20:56.027521 [CRIT] switch_time.c:755 Virtual Migration 
Detected! Syncing Clock
2010-10-24 23:20:59.964199 [CRIT] switch_time.c:755 Virtual Migration 
Detected! Syncing Clock
2010-10-24 23:21:05.092063 [CRIT] switch_time.c:755 Virtual Migration 
Detected! Syncing Clock
2010-10-24 23:21:10.620075 [WARNING] switch_scheduler.c:114 Task was 
executed late by 2 seconds 1 heartbeat (core)

The 1st time the whole server went into frozen state. I was able to  
ping network interface but couldn't get response from any service from 
the server. Reboot did the job and server worked fine until error 
occurred the 2nd time when only Freeswitch crashed.
Frequently, during the day, server is faced randomly with high load on 
memory and cpu with up to 20 concurrent calls. Is it possible that high 
cpu load and lack of resource i.e. memory can cause this problem?
Freeswitch consumes  up to 55% of RAM.

Here is box info:
OS: CentOS 5.5 64 bit
CPU: AMD Opteron 1216HE
RAM: 2GB
FreeSWITCH version: 1.0.head (git-8726104 2010-09-15 19-46-23 -0500)
Can anyone drop some light one this issue? Also i want to ask what is 
the recommended configuration for 1000 concurrent calls.

Pedja






More information about the FreeSWITCH-users mailing list