Quick tips, with debug packages installed,
mkdir /var/crash/asterisk
sysctl kern.nosuidcoredump=3
Start asterisk and trigger a crash
Use ports gdb ("egdb" binary) not gdb in base
Once you have a backtrace, you're likely to need help from upstream in
debugging, they'll probably want some clues about how you're using it too
--
Sent from a phone, apologies for poor formatting.
On 21 May 2021 08:30:28 Landry Breuil <[email protected]> wrote:
Le Fri, May 21, 2021 at 06:56:15AM +0000, Martin a écrit :
Hi Stuart,
I'm having trouble with asterisk 18.3.0 from packages. Sometimes it crashes
during runtime. Especially if SIP client reregisters from different
locations (subnet).
interestingly, i had asterisk 18.4.0 dying yesterday night, also on 6.9.
safe_asterisk[91037]: Asterisk ended with exit status 139
safe_asterisk[91037]: Asterisk exited on signal 11.
safe_asterisk[91037]: Automatically restarting Asterisk.
but at the same time influxdb was also badly crashing/spouting go debug
msgs in syslog, so maybe that's related to system load.
sadly i dunno if asterisk generated a coredump somewhere, and if so, where..
Could you recommend runtime debug procedure to find out what happened with it?
the port has DEBUG_PACKAGES set, so install the debug symbols with
pkg_add -d asterisk, restart the service, and when it crashes collect
the trace with gdb from ports.
also looking at its logs might help.. i dont have anything special in my
logs.
Landry
