| Summary: | ASTERISK-26381: app_queue: Crash possibly related to very long dial string | ||||
| Reporter: | Jaco van Niekerk (faqterson) | Labels: | |||
| Date Opened: | 2016-09-15 09:14:58 | Date Closed: | 2016-09-16 07:09:02 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | |||
| Versions: | 13.10.0 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) backtrace.txt ( 1) Coredump.txt ( 2) Coredumpfull.txt | |||
| Description: | [2016-09-15 16:03:20] WARNING[8731] res_musiconhold.c: poll() failed: Interrupted system call
[2016-09-15 16:03:20] WARNING[8781] chan_sip.c: Retransmission timeout reached on transmission 4d68fbd7362cf1a269a971e828405489@10.100.0.252:5060 for seqno 102 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 6528ms with no response [2016-09-15 16:03:20] WARNING[8781] chan_sip.c: Hanging up call 4d68fbd7362cf1a269a971e828405489@10.100.0.252:5060 - no reply to our critical packet (see https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions). [2016-09-15 16:03:20] WARNING[23357][C-0000130c] channel.c: Invalid private redirecting-to name valid (54) [2016-09-15 16:03:20] WARNING[23357][C-0000130c] channel.c: Invalid private redirecting-to name valid (54) [2016-09-15 16:03:20] WARNING[23357][C-0000130c] channel.c: Invalid private redirecting-to name valid (54) [2016-09-15 16:03:20] WARNING[23357][C-0000130c] channel.c: Invalid private redirecting-to name valid (54) [2016-09-15 16:03:20] WARNING[23357][C-0000130c] channel.c: Invalid private redirecting-to name valid (54) [2016-09-15 16:03:20] NOTICE[23357][C-0000130c] core_local.c: No such extension/context 2350000026932693269326932693269326932693269326932693269326932693269326932693269@default while calling Local channel [2016-09-15 16:03:20] NOTICE[23357][C-0000130c] app_queue.c: Forwarding failed to dial 'Local/235000002693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326592693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269' [2016-09-15 16:03:20] WARNING[8717] core_local.c: Someone used Local/2350000026932693269326932693269326932693269326932693269326932693269326932 somewhere without a @context. This is bad. [2016-09-15 16:03:20] WARNING[8717] core_local.c: Someone used Local/2350000026932693269326932693269326932693269326932693269326932693269326932 somewhere without a @context. This is bad. [2016-09-15 16:03:20] ERROR[23357][C-0000130c] astobj2.c: user_data is NULL [2016-09-15 16:03:20] ERROR[23357][C-0000130c] astobj2.c: user_data is NULL [2016-09-15 16:03:20] ERROR[23357][C-0000130c] astobj2.c: user_data is NULL [2016-09-15 16:03:20] ERROR[23357][C-0000130c] astobj2.c: user_data is NULL | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-09-15 09:14:59.015-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: George Joseph (gjoseph) 2016-09-15 09:40:44.947-0500 There isn't enough information here to see what's going on. Was there actually a crash or are you just seeing the "user_data is NULL" messages. Follow the guidelines mentioned in the comment above to get the full backtraces. By: Jaco van Niekerk (faqterson) 2016-09-16 00:51:18.013-0500 There was an actual crash 1 min after this error displaying in the CLI: Sep 15 16:04 core.8703 I have attached the core dumps. By: Jaco van Niekerk (faqterson) 2016-09-16 01:00:20.952-0500 Backtrace attached as requested. I am keep eye on the dial plan to day to see if its the cause of the astobj errors, it might cause load and then crash asterisk. By: George Joseph (gjoseph) 2016-09-16 08:17:37.857-0500 The crash is actually in app_queue so I'll change the title. I wonder if it's related to that very long dial string... "23500000269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326932693269326932659269326932693269326932693269326932693269326932693269326932693" By: Jaco van Niekerk (faqterson) 2016-09-16 08:33:56.937-0500 The problem has been replicated: Connected to Asterisk 13.11.2 currently running on localhost (pid = 30307) – Got SIP response 302 "Moved Temporarily" back from 192.168.97.71:5060 – Now forwarding DAHDI/i1/0871350000-1 to 'Local/444@internal' (thanks to SIP/4000-00000000) 2016-09-16 14:49:44 NOTICE: core_local.c:740 local_call: No such extension/context 444@internal while calling Local channel 2016-09-16 14:49:44 NOTICE: app_queue.c:4962 wait_for_answer: Forwarding failed to dial 'Local/444@internal' Its related to a forward request from a queuemember to an invalid extension. I resolve the problem until its patched: i: Ignore call forward requests from queue members and do nothing when they are requested. {{exten => s,10,Queue($QUEUE,$OPTIONStTi,,,$TIME)}} By: Asterisk Team (asteriskteam) 2016-09-16 08:33:57.216-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Joshua C. Colp (jcolp) 2016-09-16 08:53:47.106-0500 This issue has already been fixed on the linked issue and will be in a future release. | ||||