[Home]

Summary:ASTERISK-27832: Asterisk Segmentation faults
Reporter:IT Manager (it_manager)Labels:
Date Opened:2018-05-01 05:36:20Date Closed:2020-01-14 11:24:13.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/General
Versions:1.8.15.0 Frequency of
Occurrence		Occasional
Related
Issues:
Environment:CentOS release 5.6 (Final)Attachments:
Description:Could you please help me to understand why asterisk is crashing so often. Sometimes it can work normally for 1 week - but sometimes it can crash 3-4 times per day.

I tried to load core dumps with gdb - and this is what I received:

# gdb asterisk core.dump
…
Loaded symbols for /lib64/libnss_dns.so.2
Reading symbols from /lib64/libgcc_s.so.1…(no debugging symbols found)…done.
Loaded symbols for /lib64/libgcc_s.so.1

warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffffdff6000
Core was generated by `/usr/sbin/asterisk -f -vvvg -c'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000000000000000 in ?? ()

(gdb) bt

#0  0x0000000000000000 in ?? ()
#1  0x00000033736509a1 in ?? () from /usr/lib64/mysql/libmysqlclient.so.15
#2  0x0000003373650d19 in my_net_read () from /usr/lib64/mysql/libmysqlclient.so.15
#3  0x000000337364a7f2 in cli_safe_read () from /usr/lib64/mysql/libmysqlclient.so.15
#4  0x000000337364b6e9 in ?? () from /usr/lib64/mysql/libmysqlclient.so.15
#5  0x0000003373649fae in mysql_real_query () from /usr/lib64/mysql/libmysqlclient.so.15
#6  0x00002aaab674fe31 in aMYSQL_query (chan=0x2aaaadcc8608,
   data=0x40e688d0 "Query resultid 8096 select concat(first_name, ' ',  last_name) from table where .. at app_mysql.c:394
#7  MYSQL_exec (chan=0x2aaaadcc8608,
   data=0x40e688d0 "Query resultid 8096 select concat(first_name, ' ',  last_name) from table where .. at app_mysql.c:570
#8  0x00000000004ebe2f in pbx_exec (c=0x2aaaadcc8608, app=0x2aaac8c4cee0,
   data=0x40e688d0 "Query resultid 8096 select concat(first_name, ' ',  last_name) from table where .. at pbx.c:1446
#9  0x00000000004fb34c in pbx_extension_helper (c=0x2aaaadcc8608, con=<value optimized out>, context=0x2aaaadcc8b60 "macro-NumberLookup", exten=0x2aaaadcc8bb0 "s", priority=11, label=0x0,
   callerid=0x15ebbd30 "+XXXXXXXXXXX", action=E_SPAWN, found=0x40e6b85c, combined_find_spawn=1) at pbx.c:4266
#10 0x00000000004fb990 in ast_spawn_extension (c=0x150e6c40, context=0x2 <Address 0x2 out of bounds>, exten=0x0, priority=1195987744, callerid=<value optimized out>, found=<value optimized out>,
   combined_find_spawn=1) at pbx.c:4904
#11 0x00002aaab7d8c98b in _macro_exec (chan=0x2aaaadcc8608, data=0x2aaacc167a80 "\370z\026̪*", exclusive=0) at app_macro.c:413
#12 0x00000000004ebe2f in pbx_exec (c=0x2aaaadcc8608, app=0x2aaac8379bb0, data=0x40e6d990 "NumberLookup,IE-00540") at pbx.c:1446
#13 0x00000000004fb34c in pbx_extension_helper (c=0x2aaaadcc8608, con=<value optimized out>, context=0x2aaaadcc8b60 "macro-NumberLookup", exten=0x2aaaadcc8bb0 "s", priority=32, label=0x0,
   callerid=0x15ebbd30 "+XXXXXXXXXXX", action=E_SPAWN, found=0x40e7000c, combined_find_spawn=1) at pbx.c:4266
#14 0x00000000004fe32b in ast_spawn_extension (c=0x2aaaadcc8608, args=0x0) at pbx.c:4904
#15 __ast_pbx_run (c=0x2aaaadcc8608, args=0x0) at pbx.c:5004
#16 0x000000000050078b in pbx_thread (data=0x150e6c40) at pbx.c:5345
#17 0x000000000053826c in dummy_start (data=<value optimized out>) at utils.c:1008
#18 0x0000003e9c00673d in start_thread () from /lib64/libpthread.so.0
#19 0x0000003e9b8d40cd in clone () from /lib64/libc.so.6
Comments:By: Asterisk Team (asteriskteam) 2018-05-01 05:36:22.122-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Asterisk Team (asteriskteam) 2018-05-01 05:36:22.653-0500

Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions