| Summary: | ASTERISK-29424: stasis: Crash on publishing with no topic | ||
| Reporter: | Balf PBX (balfpbx) | Labels: | |
| Date Opened: | 2021-05-11 04:43:45 | Date Closed: | 2021-05-31 10:14:10 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_stasis |
| Versions: | 18.3.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | After upgrade asterisk to “Asterisk 18.3.0”, system crashed very often. System messages show the same error:
[12374.018980] asterisk[15815]: segfault at 10 ip 000000000058e445 sp 00007f2fed2d1f30 error 4 in asterisk[400000+2f0000] Core crash event file read #0 0x000000000058e445 in stasis_topic_subscribers (topic=0x0) at stasis.c:645 #1 0x000000000058fe2b in publish_msg (topic=0x0, message=0x7f2fa40058b8, sync_sub=0x0) at stasis.c:1465 #2 0x000000000058ff57 in stasis_publish (topic=0x0, message=0x7f2fa40058b8) at stasis.c:1512 #3 0x000000000059e7c3 in ast_channel_publish_blob (chan=0x7f2fc0005370, type=0x2059248, blob=0x7f2fa4004b60) at stasis_channels.c:1145 #4 0x000000000059e88f in ast_channel_publish_varset (chan=0x7f2fc0005370, name=0x7f2ff849e134 "AGISTATUS", value=0x7f2ff849d2f3 "SUCCESS") at stasis_channels.c:1171 #5 0x000000000054c663 in pbx_builtin_setvar_helper (chan=0x7f2fc0005370, name=0x7f2ff849e134 "AGISTATUS", value=0x7f2ff849d2f3 "SUCCESS") at pbx_variables.c:1116 #6 0x00007f2ff849befb in agi_exec_full (chan=0x7f2fc0005370, data=0x7f2fed2d2700 "agi://127.0.0.1/sangomacrm.agi", enhanced=0, dead=1) at res_agi.c:4545 #7 0x00007f2ff849bfc0 in agi_exec (chan=0x7f2fc0005370, data=0x7f2fed2d2700 "agi://127.0.0.1/sangomacrm.agi") at res_agi.c:4566 #8 0x00000000005422f0 in pbx_exec (c=0x7f2fc0005370, app=0x27b7f90, data=0x7f2fed2d2700 "agi://127.0.0.1/sangomacrm.agi") at pbx_app.c:492 #9 0x000000000052dcd0 in pbx_extension_helper (c=0x7f2fc0005370, con=0x0, context=0x7f2fc0005d30 "crm-hangup", exten=0x7f2fc0005d80 "s", priority=7, label=0x0, callerid=0x7f2fa40056e0 "\330\001", action=E_SPAWN, found=0x7f2fed2d58d4, combined_find_spawn=1) at pbx.c:2947 #10 0x0000000000531adc in ast_spawn_extension (c=0x7f2fc0005370, context=0x7f2fc0005d30 "crm-hangup", exten=0x7f2fc0005d80 "s", priority=7, callerid=0x7f2fa40056e0 "\330\001", found=0x7f2fed2d58d4, combined_find_spawn=1) at pbx.c:4206 #11 0x00007f302234c429 in gosub_run (chan=0x7f2fc0005370, sub_args=0x7f2fa4004ff8 "crm-hangup,s,1", ignore_hangup=1) at app_stack.c:1056 #12 0x0000000000443737 in ast_app_exec_sub (autoservice_chan=0x0, sub_chan=0x7f2fc0005370, sub_args=0x7f2fa4004ff8 "crm-hangup,s,1", ignore_hangup=1) at app.c:387 #13 0x0000000000547ae1 in ast_pbx_hangup_handler_run (chan=0x7f2fc0005370) at pbx_hangup_handler.c:86 #14 0x0000000000533acf in __ast_pbx_run (c=0x7f2fc0005370, args=0x0) at pbx.c:4599 #15 0x0000000000533f6d in pbx_thread (data=0x7f2fc0005370) at pbx.c:4704 #16 0x00000000005c7aaa in dummy_start (data=0x7f2f3c0026c0) at utils.c:1299 #17 0x00007f30729dcea5 in start_thread () from /lib64/libpthread.so.0 #18 0x00007f3071a7b8dd in clone () from /lib64/libc.so.6 | ||
| Comments: | By: Asterisk Team (asteriskteam) 2021-05-11 04:43:46.117-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Benjamin Keith Ford (bford) 2021-05-11 09:45:07.745-0500 Looks like a NULL topic is getting passed up the chain. Is there any additional information you can provide for this? What version did you upgrade from? By: Balf PBX (balfpbx) 2021-05-11 10:49:12.375-0500 The first asterisk was version 13 LTS, for some reasons I upgrade to 15 and after to 18...But the crash event started after first upgrade (13 to 15) By: Benjamin Keith Ford (bford) 2021-05-11 12:24:08.331-0500 Thanks for the additional info. I've opened up an issue to look into this further. By: Balf PBX (balfpbx) 2021-05-17 02:26:12.273-0500 Hello, Can I run asterisk in safe mode, till the bug solution ? ( If it make sense, sure ) Regards By: Balf PBX (balfpbx) 2021-05-31 10:13:35.941-0500 Hello, The issue has been solved by uninstalling "FreePbx Commercial Modules" Regards By: Balf PBX (balfpbx) 2021-05-31 10:14:10.891-0500 Hello, The issue has been solved by uninstalling "FreePBX Commercial Modules" Regards | ||