Asterisk 22.2.0 crash randomly while using MixMonitor for SIP

Hi,

recently I had an issue with Asterisk v18 that was crashing when I was using mixmonitor on some SIP streams.

As this version was quite old, I made the update to the latest 22 version : 22.2.0, and while the crash is less frequent (after a couple of days instead of an 1 hour), it still crash.

So far, I only have this logs from journalctl :

mars 05 11:23:22 localhost kernel: asterisk[992330]: segfault at 8 ip 0000564d32433020 sp 00007f6810dcf838 error 4 in asterisk[564d322c2000+1fe000] likely on CPU 3 (core 1, socket 1)
mars 05 11:23:22 localhost kernel: Code: 1f 84 00 00 00 00 00 0f 1f 00 48 8b 47 08 48 8b 17 48 8b 40 10 48 89 d7 48 8b 40 50 ff e0 66 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 8b 47 08 48 8b 17 48 8b 40 10>
m

I am using Asterisk v22.2.0 that I compiled myself from the sources, on a Debian 12 virtual machine.

Is there something I can do to provide more information that could be needed to find where is the issue ?

Best regards.

1 Like

Thank you, I will change how we start Asterisk to make it generate the core dump. And disable code optimization.

I have my first ast_coredumper output files, should I open a jira ticket or, can we see that here ?

Jira doesn’t exist anymore, so it would be GitHub. If it is an issue, then ultimately a GitHub issue should be filed regardless so you can provide it there if you want. Ideally with an accompanying console output, and configuration including how MixMonitor is invoked.

Ok, thank you very much for your support, I will do that.

I am so sorry for the bother, I saw you marked my bug report as a duplicate.

Thank you very much. I am not an expert on Asterisk, could you kindly guide me on how to enable timing module ?

Just loading the res_timing_pthread.so is enough ?

Yes, but res_timing_timerfd is the preferred one.

1 Like

Thank you so much.