| Summary: | ASTERISK-25962: Asterisk crashes, potential cause: realtime musiconhold | ||
| Reporter: | Richard Mourits (onliyme) | Labels: | |
| Date Opened: | 2016-04-26 08:12:09 | Date Closed: | 2016-04-29 04:57:24 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Addons/res_config_mysql |
| Versions: | 11.5.1 | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | Debian 6.0.7 Kernel 2.6.32-5-686 | Attachments: | ( 0) backtrace.txt |
| Description: | Every once in a while, the asterisk (11.5.1) crashes. The cause could be musiconhold in combination with RealTime. The application makes lots of dials using moh and, if no dial is made, moh is startet by agi.
When we use RealTime, every so often a warning appears: [2016-04-26 10:38:16.295] WARNING[20209][C-000054f1] file.c: File ā7Lāā does not exist in any format [2016-04-26 10:38:16.295] WARNING[20209][C-000054f1] res_musiconhold.c: Unable to open file '/usr/opensips/sounds/voipacd/6/Warteschleife/Warteschleife': No such file or directory These warnings do not appear when not using RealTime engine for musiconhold. The debug log does not show any message before the asterisk crashes: [2016-04-26 10:57:52.714] VERBOSE[3406][C-00005598] pbx.c: -- Executing [start@agent_group:10] Dial("SIP/sbc-welt-hh-00039257", "SIP/D00422196372861@sbc-welt-hh,3 0,A()m(Warteschleife)M(destAnswer)gt") in new stack [2016-04-26 10:57:52.715] VERBOSE[3406][C-00005598] netsock2.c: == Using SIP RTP CoS mark 5 [2016-04-26 10:57:52.723] VERBOSE[3406][C-00005598] app_dial.c: -- Called SIP/D00422196372861@sbc-welt-hh [2016-04-26 10:57:59.727] Asterisk 11.5.1 built by root @ inc-bln on a i686 running Linux on 2016-03-15 16:32:52 UTC [2016-04-26 10:57:59.747] VERBOSE[10599] config.c: == Parsing '/etc/asterisk/asterisk.conf': Found .. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-04-26 08:12:10.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: Joshua C. Colp (jcolp) 2016-04-26 08:19:32.416-0500 It appears the bug you have submitted is against a rather old version of a supported branch of Asterisk. There have been many issues fixed between the version you are using and the current version of your branch. Please test with the latest version in your Asterisk branch and report whether the issue persists. Please see the Asterisk Versions [1] wiki page for info on which versions of Asterisk are supported. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions By: Richard Mourits (onliyme) 2016-04-26 08:55:36.090-0500 Since the System is used in Production, this will take some time. We are considering moving to asterisk 13. By: Joshua C. Colp (jcolp) 2016-04-26 08:59:14.038-0500 It's your decision either way but we can't support 11.5.1. It's 17 11 releases behind, and is over 2.5 years old. By: Richard Mourits (onliyme) 2016-04-29 04:33:18.385-0500 Ok, the ticket can be closed. I will verify it on a newer version, someday. | ||