sounds like the core.db was corrupted in a way that caused the segfault... it is safe to delete that file at any time... if you have core dumps where you can get a back trace, do so and as per the bug reporting guide lines on the wiki and open a jura especially if they are all segueing int he same spot K On Tue, Feb 14, 2012 at 10:05 AM, Darcy <darcy@primrose.ws> wrote:
I have three freeswitches running on public IPs, not behind a router. There was a power hit on site and all servers were restarted but none of the freeswitches started, when I tried to manually start them, I got a segmentation fault. I had to rename core.db on each system to get them to restart. Is this a known issue. One of these switches had a git update 1 week ago, the other two are various vintages but run flawless, until last night of course. The longest running one is about 14 months.
Any input or thoughts would be appreciated.
Darcy
_________________________________________________________________________ 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