Asterisk core dump following apt update (debian12)

AllStarLink
1

Hi all,

I ran apt update, apt upgrade and asterisk core dumps following the updates. Any ideas where I should start with this one? Can I roll back the updates?

Cheers,
Robert

Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)
********** AllStarLink [ASL] Version Info **********

OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.1.0-48-amd64

Asterisk : 22.8.2+asl3-3.8.3-1.deb12
ASL [app_rpt] :

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.8.1-1.deb12
asl3 3.17-1.deb12
asl3-asterisk 2:22.8.2+asl3-3.8.3-1.deb12
asl3-asterisk-config 2:22.8.2+asl3-3.8.3-1.deb12
asl3-asterisk-modules 2:22.8.2+asl3-3.8.3-1.deb12
asl3-menu 1.18-1.deb12
asl-apt-repos 2.0-1.deb12
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-11.asl.deb12
dahdi-linux 1:3.4.0-11.asl.deb12
dahdi-source 1:3.4.0-11.asl.deb12

● asterisk.service - Asterisk PBX
Loaded: loaded (/lib/systemd/system/asterisk.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: core-dump) since Wed 2026-05-27 09:48:29 BST; 4s ago
Docs: man:asterisk(8)
Process: 447721 ExecStart=/usr/sbin/asterisk -g -f -p -U asterisk (code=dumped, signal=SEGV)
Main PID: 447721 (code=dumped, signal=SEGV)
CPU: 583ms

2

Is there anything useful in the log files?

3

Did it happen once? Or every time?

4

Which is the best command please? I'm a copy and paste type :melting_face:

5

It's every time - I have tried reboot etc.
Thanks

6

To gather the logs : ASL Manual : Basic Troubleshooting Tips : Gathering Logs

and my suspicion is that asterisk+app_rpt is not happy with one of your .conf files (in the /etc/asterisk directory). Can you tell us a bit more about how you have this server/node setup?

7

Just in case this is helpful to someone else in the future.

With a bit of help from gemini, I tracked down the route of the issue to be one of the modules.conf entries below. I was running a SIP connection but I've not used it for a while, so the simple fix was to comment them all out. I'm not sure which was the culprit, but after removing them it fixed the coredump.

;modules for pjsip
;
;noload = app_voicemail.so
;load = bridge_builtin_features.so
;load = bridge_builtin_interval_features.so
;load = bridge_holding.so
;load = bridge_native_rtp.so
;load = bridge_simple.so
;load = bridge_softmix.so
;load = chan_bridge_media.so
;load = chan_pjsip.so
;load = func_pjsip_endpoint.so
;load = func_sorcery.so
;load = func_devstate.so
;load = res_pjproject.so
;load = res_pjsip_acl.so
;load = res_pjsip_authenticator_digest.so
;load = res_pjsip_caller_id.so
;load = res_pjsip_dialog_info_body_generator.so
;load = res_pjsip_diversion.so
;load = res_pjsip_dtmf_info.so
;load = res_pjsip_endpoint_identifier_anonymous.so
;load = res_pjsip_endpoint_identifier_ip.so
;load = res_pjsip_endpoint_identifier_user.so
;load = res_pjsip_exten_state.so
;load = res_pjsip_header_funcs.so
;load = res_pjsip_logger.so
;load = res_pjsip_messaging.so
;load = res_pjsip_mwi_body_generator.so
;load = res_pjsip_mwi.so
;load = res_pjsip_nat.so
;load = res_pjsip_notify.so
;load = res_pjsip_one_touch_record_info.so
;load = res_pjsip_outbound_authenticator_digest.so
;load = res_pjsip_outbound_publish.so
;load = res_pjsip_outbound_registration.so
;load = res_pjsip_path.so
;load = res_pjsip_pidf_body_generator.so
;load = res_pjsip_pidf_digium_body_supplement.so
;load = res_pjsip_pidf_eyebeam_body_supplement.so
;load = res_pjsip_publish_asterisk.so
;load = res_pjsip_pubsub.so
;load = res_pjsip_refer.so
;load = res_pjsip_registrar.so
;load = res_pjsip_rfc3326.so
;load = res_pjsip_sdp_rtp.so
;load = res_pjsip_send_to_voicemail.so
;load = res_pjsip_session.so
;load = res_pjsip.so
;noload = res_pjsip_t38.so
;noload = res_pjsip_transport_websocket.so
;load = res_pjsip_xpidf_body_generator.so
;load = res_rtp_asterisk.so
;load = res_sorcery_astdb.so
;load = res_sorcery_config.so
;load = res_sorcery_memory.so
;load = res_sorcery_realtime.so

After I'd fixed that, I was getting apt_rpt.so crashing, and that was due to a line or two in rpt.conf that it didn't like!

Cheers