Asterisk crash problem

Asterisk Asterisk Support
1

Hi,
I am using 20.8.1, Centos 8

pls suggest for following error, is it related to dialplan or what ?

[New LWP 42789]
[New LWP 30619]
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/lib64/libthread_db.so.1”.
Core was generated by `/usr/sbin/asterisk -f -vvvg -c’.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f0e2bca98f9 in __memmove_avx_unaligned_erms () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f0dc0546700 (LWP 49837))]
Missing separate debuginfos, use: yum debuginfo-install cyrus-sasl-lib-2.1.27-5.el8.x86_64 glibc-2.28-164.el8.x86_64 keyutils-libs-1.5.10-9.el8.x86_64 krb5-libs-1.18.2-14.el8.x86_64 libcom_err-1.45.6-2.el8.x86_64 libedit-3.1-23.20170329cvs.el8.x86_64 libgcc-8.5.0-4.el8_5.x86_64 libselinux-2.9-5.el8.x86_64 libstdc+±8.5.0-4.el8_5.x86_64 libuuid-2.32.1-43.el8.x86_64 libxcrypt-4.1.1-6.el8.x86_64 libxml2-2.9.7-9.el8_4.2.x86_64 ncurses-libs-6.1-9.20180224.el8.x86_64 openldap-2.4.46-18.el8.x86_64 openssl-libs-1.1.1k-5.el8_5.x86_64 pcre2-10.32-2.el8.x86_64 sqlite-libs-3.26.0-15.el8.x86_64 sssd-client-2.5.2-2.el8_5.3.x86_64 xz-libs-5.2.4-3.el8.x86_64 zlib-1.2.11-17.el8.x86_64
(gdb) bt
#0 0x00007f0e2bca98f9 in __memmove_avx_unaligned_erms () from /lib64/libc.so.6
#1 0x00007f0dc3ac7ce8 in vosk_recog_write () from /usr/lib/asterisk/modules/res_speech_vosk.so
#2 0x00007f0dc2eada08 in speech_background (chan=0x7f0d64147630, data=) at app_speech_utils.c:859
#3 0x0000000000528d1a in pbx_exec (c=c@entry=0x7f0d64147630, app=app@entry=0x1e62630, data=data@entry=0x7f0dc0543c00 “quizivr/2024/Feb-24/Hindi/5001,0”)
at /root/Downloads/asterisk-20.8.0-rc1/include/asterisk/strings.h:67
#4 0x000000000051dbcb in pbx_extension_helper (c=c@entry=0x7f0d64147630, context=0x7f0d64147ff0 “SelectMenuEng”, exten=exten@entry=0x7f0d64148040 “s”,
priority=priority@entry=10, label=label@entry=0x0, callerid=callerid@entry=0x7f0d6492a550 “+919617548743”, action=E_SPAWN, found=0x7f0dc0545c84,
combined_find_spawn=1, con=0x0) at pbx.c:2948
#5 0x000000000051f68b in ast_spawn_extension (combined_find_spawn=1, found=0x7f0dc0545c84, callerid=0x7f0d6492a550 “+919617548743”, priority=10,
exten=0x7f0d64148040 “s”, context=, c=0x7f0d64147630) at pbx.c:4203
#6 __ast_pbx_run (c=c@entry=0x7f0d64147630, args=args@entry=0x0) at pbx.c:4377
#7 0x0000000000520c7b in pbx_thread (data=data@entry=0x7f0d64147630) at pbx.c:4701
#8 0x00000000005a0c59 in dummy_start (data=) at utils.c:1607
#9 0x00007f0e2da3617a in start_thread () from /lib64/libpthread.so.0
#10 0x00007f0e2bc45dc3 in clone () from /lib64/libc.so.6

2

The actual crash is in the VOSK speech recognition interface module, but segmentation violations are often the delayed result of memory corruption, possibly even by a different thread.

Unless they cause catastrophic resource depletion, dialplan errors should not cause segmentation faults. They are normally the results of bugs in the Asterisk code or libraries it uses, although hardware faults can also cause them. Invalid input from the dialplan should be validated and detected before it causes a crash.

3

Thanks David , You shared valuable information.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.