On 2/5/2010 4:32 PM, Scott Lawrence wrote: > Agreed, but so far the only information we could put in an issue is > "sometimes freeswitch sucks up the entire cpu". We don't know what > configurations those systems have, or what event triggers it. As one of > the people that screens New issues, I can promise that that report would > just be returned with a request for more information. > > If someone can get a core file while this is happening, and take a > snapshot that includes the symbol data (this must be done from the > command line: see sipx-snapshot --help) and attach that too an issue, > then we'd have a starting point. > > I will be more than happy to. I want to make sure I get the steps right, because I would prefer to get my server out of this state as soon as possible when it does happen.
1) kill -6 <pid> (get core file) 2) sipx-snapshot On the snapshot, sipx-snapshot --help does not contain the word 'symbol'. Is there a certain switch that needs to be used? Thanks, Matthew _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
