| Summary: | ASTERISK-26286: ERROR[9264][C-0000072f] astobj2.c: user_data is NULL | ||||
| Reporter: | Drew Dickenson (ddickenson) | Labels: | |||
| Date Opened: | 2016-08-10 18:38:08 | Date Closed: | 2016-08-11 09:24:01 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | Applications/app_queue | ||
| Versions: | 13.9.1 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | CentOS 6.8 x86_64, Dell PowerEdge 2950, Asterisk 13.9.1, DPMA 13.0_2.2.0, Digium D45 sets Firmware versions 2_0_2_0_78957, and 2_1_0_0_81296. Flash Operator panel version fop2-231.02-centos-x86_64 using AMI | Attachments: | ( 0) extensions.conf ( 1) messages.trk ( 2) queue_log ( 3) queues.conf | ||
| Description: | Issue noted on multiple versions of Asterisk 13 with both pjsip and chan_sip where a call in the queue will attempt to ring a phone that is unavailable for some reason (has been noted when using DND or when an agent set is for some reason forwarded to a non-working number).
The following is always noted in the logs just prior to an endless loop of the below error message. {noformat} [Aug 10 12:45:42] NOTICE[9264][C-0000072f] core_local.c: No such extension/context FDMC_09_0000_0716@fdmc_users while calling Local channel [Aug 10 12:45:42] NOTICE[9264][C-0000072f] app_queue.c: Forwarding failed to dial 'Local/FDMC_09_0000_0716@fdmc_users' [Aug 10 12:45:42] ERROR[9264][C-0000072f] astobj2.c: user_data is NULL [Aug 10 12:45:42] ERROR[9264][C-0000072f] astobj2.c: user_data is NULL [Aug 10 12:45:42] ERROR[9264][C-0000072f] astobj2.c: user_data is NULL ... {noformat} This continues until asterisk either crashes or restarts itself. If it continues a while poor call quality has been noted, also high memory usage. Ex: Box normally uses aprox 2gb ram and it's maxed out the 8gb or the 16gb of the box. Unsure if the device in the log snippit was actually unavailable at the time of the crash but it IS a valid device and is online now. attaching "messages" "queue_log" "queues.conf" and "extensions.conf" | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-08-10 18:38:08.613-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: Drew Dickenson (ddickenson) 2016-08-10 18:45:55.319-0500 the messages file has been truncated as the file grew to 392MB in a matter of seconds. I've got all the way through the build (and debug) process and through the first day of live operation where the issue was noted and probably 150 lines of the error message that continues to the end of the original file. The JSON errors are another issue that seems to have to do with the D45 voicemail application on certain, but not all sets. By: Etienne Lessard (hexanol) 2016-08-11 06:58:44.987-0500 This ticket seems like a duplicate of ASTERISK-25797. By: Drew Dickenson (ddickenson) 2016-08-11 07:27:17.576-0500 I was in discussion with Matt Jordan about this issue over on the communities site and he asked that I put in a report with the attached documents. https://community.asterisk.org/t/asterisk-error-astobj2-c-user-data-is-null/49125/10 By: Drew Dickenson (ddickenson) 2016-08-11 07:28:09.410-0500 Though I agree, it sounds like the same issue. By: Rusty Newton (rnewton) 2016-08-11 08:37:31.574-0500 Thank you for the crash report. However, we need more information to investigate the crash. Please provide: 1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1]. 2. Specific steps taken that lead to the crash. 3. All configuration information necesary to reproduce the crash. Thanks! [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Drew Dickenson (ddickenson) 2016-08-11 08:44:24.447-0500 I am unable to provide such things as I'm not able to attempt to crash this system intentionally while it's in production. Also as noted in the other similar ticket the fact that it runs the system out of memory appears to not cause a dump. Also mjordan appeared to think that would not be necessary to address this issue as seen in the forum post linked above. I can say that I just saw an interesting thing come across the command line while watching. It is a similar message to the one shown in app_queue but this one did not cause a crash. Also as noted further below the user in question is available at the time which has been my thought all along. {noformat} [Aug 11 08:36:06] NOTICE[31198][C-000000ef]: app_dial.c:904 do_forward: Not accepting call completion offers from call-forward recipient Local/FDMC_09_0029_0716@fdmc_users-00000003;1 PRI Span: 1 Ignored redirecting update because call in state Active(10). [Aug 11 08:36:06] NOTICE[31198][C-000000ef]: core_local.c:740 local_call: No such extension/context FDMC_09_0029_0716@fdmc_users while calling Local channel [Aug 11 08:36:06] NOTICE[31198][C-000000ef]: app_dial.c:1010 do_forward: Forwarding failed to dial 'Local/FDMC_09_0029_0716@fdmc_users' [Aug 11 08:36:12] ERROR[28687]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s, s: s, s: s, s: s, s: s, s: s, s: s}': Invalid UTF-8 string. [Aug 11 08:36:13] ERROR[28687]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s, s: s, s: s, s: s, s: s, s: s, s: s}': Invalid UTF-8 string. [Aug 11 08:36:20] ERROR[28687]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s, s: s, s: s, s: s, s: s, s: s, s: s}': Invalid UTF-8 string. [Aug 11 08:36:53] NOTICE[31235][C-000000f2]: pbx.c:2867 pbx_extension_helper: No such label 'busy' in extension 's' in context 'macro-stdvoicemail' [Aug 11 08:36:53] WARNING[31235][C-000000f2]: pbx.c:8463 pbx_parseable_goto: Priority 'busy' must be a number > 0, or valid label Hillsboro-Asterisk1*CLI> sip show peers Name/username Host Dyn Forcerport Comedia ACL Port Status Description Drew_Hill/Drew_Hill (Unspecified) D Auto (No) No 0 UNKNOWN FDMC_09_0000_0716/FDMC_09 192.168.65.47 D Auto (No) No 5060 OK (2 ms) FDMC_09_0001_0716/FDMC_09 192.168.65.41 D Auto (No) No 5060 OK (2 ms) FDMC_09_0002_0716/FDMC_09 192.168.65.46 D Auto (No) No 5060 OK (3 ms) FDMC_09_0003_0716 (Unspecified) D Auto (No) No 0 UNKNOWN FDMC_09_0004_0716/FDMC_09 192.168.65.43 D Auto (No) No 5060 OK (2 ms) FDMC_09_0005_0716/FDMC_09 192.168.65.40 D Auto (No) No 5060 OK (2 ms) FDMC_09_0006_0716/FDMC_09 192.168.65.37 D Auto (No) No 5060 OK (283 ms) FDMC_09_0007_0716/FDMC_09 192.168.65.50 D Auto (No) No 5060 OK (2 ms) FDMC_09_0008_0716/FDMC_09 192.168.65.38 D Auto (No) No 5060 OK (2 ms) FDMC_09_0009_0716/FDMC_09 192.168.65.22 D Auto (No) No 5060 OK (2 ms) FDMC_09_0010_0716/FDMC_09 192.168.65.23 D Auto (No) No 5060 OK (2 ms) FDMC_09_0011_0716/FDMC_09 192.168.65.31 D Auto (No) No 5060 OK (2 ms) FDMC_09_0012_0716/FDMC_09 192.168.65.33 D Auto (No) No 5060 OK (2 ms) FDMC_09_0013_0716/FDMC_09 192.168.65.36 D Auto (No) No 5060 OK (2 ms) FDMC_09_0014_0716/FDMC_09 192.168.65.51 D Auto (No) No 5060 OK (187 ms) FDMC_09_0015_0716/FDMC_09 192.168.65.53 D Auto (No) No 5060 OK (2 ms) FDMC_09_0016_0716/FDMC_09 192.168.65.34 D Auto (No) No 5060 OK (2 ms) FDMC_09_0017_0716/FDMC_09 192.168.65.56 D Auto (No) No 5060 OK (2 ms) FDMC_09_0018_0716/FDMC_09 192.168.65.54 D Auto (No) No 5060 OK (2 ms) FDMC_09_0019_0716/FDMC_09 192.168.65.52 D Auto (No) No 5060 OK (2 ms) FDMC_09_0020_0716/FDMC_09 192.168.65.42 D Auto (No) No 5060 OK (2 ms) FDMC_09_0021_0716/FDMC_09 192.168.65.44 D Auto (No) No 5060 OK (2 ms) FDMC_09_0022_0716/FDMC_09 192.168.65.55 D Auto (No) No 5060 OK (2 ms) FDMC_09_0023_0716 (Unspecified) D Auto (No) No 0 UNKNOWN FDMC_09_0024_0716/FDMC_09 192.168.65.48 D Auto (No) No 5060 OK (2 ms) FDMC_09_0025_0716/FDMC_09 192.168.65.49 D Auto (No) No 5060 OK (2 ms) FDMC_09_0026_0716/FDMC_09 192.168.65.20 D Auto (No) No 5060 OK (2 ms) FDMC_09_0027_0716 (Unspecified) D Auto (No) No 0 UNKNOWN FDMC_09_0028_0716/FDMC_09 192.168.65.24 D Auto (No) No 5060 OK (2 ms) FDMC_09_0029_0716/FDMC_09 192.168.65.57 D Auto (No) No 5060 OK (2 ms) FDMC_09_0030_0716 (Unspecified) D Auto (No) No 0 UNKNOWN FDMC_09_0031_0716/FDMC_09 192.168.65.45 D Auto (No) No 5060 OK (2 ms) FDMC_09_0032_0716 (Unspecified) D Auto (No) No 0 UNKNOWN FDMC_09_0033_0716/FDMC_09 192.168.65.21 D Auto (No) No 5060 OK (3 ms) FDMC_09_0034_0716/FDMC_09 192.168.65.35 D Auto (No) No 5060 OK (6 ms) FDMC_09_0035_0716/FDMC_09 192.168.65.27 D Auto (No) No 5060 OK (3 ms) FDMC_09_0036_0716/FDMC_09 192.168.65.30 D Auto (No) No 5060 OK (2 ms) FDMC_09_0037_0716/FDMC_09 192.168.65.32 D Auto (No) No 5060 OK (2 ms) FDMC_09_0038_0716/FDMC_09 192.168.65.39 D Auto (No) No 5060 OK (2 ms) FDMC_09_0039_0716/FDMC_09 192.168.65.29 D Auto (No) No 5060 OK (2 ms) FDMC_09_0040_0716/FDMC_09 192.168.65.28 D Auto (No) No 5060 OK (2 ms) FDMC_09_0041_0716/FDMC_09 192.168.65.25 D Auto (No) No 5060 OK (2 ms) FDMC_09_0042_0716/FDMC_09 192.168.65.26 D Auto (No) No 5060 OK (12 ms) 44 sip peers [Monitored: 38 online, 6 offline Unmonitored: 0 online, 0 offline] {noformat} By: Rusty Newton (rnewton) 2016-08-11 09:24:01.980-0500 Thanks, yeah we should be fine without it. Closing this out as a duplicate of ASTERISK-25797. I'll link the two. By: Rusty Newton (rnewton) 2016-08-11 09:31:30.073-0500 You can post further updates on the other issue, ASTERISK-25797, your additional information should help resolve the issue for sure. | ||||