Check dmesg for any errors. In particular look for disk I/O errors and use smartctl (smartmontools) to check for bad disk sectors. I've seen servers freeze entirely for a minute or more when trying to access a bad sector. That could lead to a big jump in the clock time for anything that was blocking on the disk I/O. Also check for any swapping to disk happening. -Steve On 16 July 2013 10:46, Yehavi Bourvine <yehavi.bourvine@gmail.com> wrote:
Hello,
I am running FS on a physical server (16 core Xeon) and got the above error. The server runs entOS 5.9, and one of the latest FS gits. When I had this message FS was freezing for a while, and active calls lost the voice (I think, can't correlate exactly).
1.What does this message means on a non-virtualized server? 2. Can it explain the freeze? 3. What can I do to overcome it?
Thanks! __Yehavi:
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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