Set ulimit -c unlimited and see if you are dropping a core Also another thing you can do is use the freeswitch.redhat script in the source tree this is init.d compatible it has all the good ulimits set in it K On 1/10/12 7:52 PM, "John O'Brien" <john@whitesmiths.com> wrote:
Hi,
We have a reasonably recent version of FreeSWITCH running. FreeSWITCH version: 1.0.head (git-10df279 2011-10-15 07-59-23 -0500) We are running on CentOS 6
We start FreeSWITCH from a shell script.
ulimit -s 240 freeswitch -ncwait -u usrXXX -g grpXXX
The issue is that things seem to go along nicely for a day to two. Then without any apparent reason the freeswitch process dies. Usually there is nothing happening when this occurs, system is idle.
There appear to be no process remnants we can use for investigation.
We would appreciate some suggestions on how we might track the issue down. Is there some simple logging we can turn on etc?
Regards,
John O'Brien john@whitesmiths.com
_________________________________________________________________________ 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