I don't see a loglevel setting for Freeswitch, sipXivr, or conference.
Do they go by other names? Am I looking in the wrong place?
On 2/5/2010 6:58 PM, Scott Lawrence wrote:
I would set the logging on DEBUG for Freeswitch, INFO for the proxy,
registrar, sipXivr and the conference system, and NOTICE for everything
else (making that change effective requires restarting things).
Once the problem is detected, log in as root. Find the runaway process
pid; check to see if it's the same as the process id in the
file /var/run/sipxecs/freeswitch.pid (interesting if not), and then cill
the process and note the time locally and in UTC:
kill -6 <pid> ; date -u +%R ; date +%U
You don't need to do anything to restart freeswitch - the supervisor
will do that on its own when it sees that the process has died.
cd to the logs directory - that's where the core file should be:
cd /var/log/sipxpbx
ls -l core*
find the one created at the time you killed the process.
Then include that in the snapshot:
sipx-snapshot --core <core-file-name>
If you can identify the time that the problem started, you can (possibly
greatly) reduce the size of the snapshot by adding time qualifiers:
--start-time <utc-time> --stop-time <time-from-date-dash-u-above>
where <utc-time> is a universal (aka GMT) time a little while (10
minutes?) before the problem was started - err on the side of early
rather than late, but let's try to avoid Gigabyte snapshot files. Use
the difference between the two times above to calculate the time offset.
|
_______________________________________________
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/
