[asterisk-bugs] [JIRA] (ASTERISK-26286) ERROR[9264][C-0000072f] astobj2.c: user_data is NULL

Rusty Newton (JIRA) noreply at issues.asterisk.org
Thu Aug 11 09:23:56 CDT 2016


    [ https://issues.asterisk.org/jira/browse/ASTERISK-26286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231796#comment-231796 ] 

Rusty Newton edited comment on ASTERISK-26286 at 8/11/16 9:22 AM:
------------------------------------------------------------------

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 at 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 at 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 at 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}


was (Author: ddickenson):
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.

[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 at 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 at 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 at 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]


> ERROR[9264][C-0000072f] astobj2.c: user_data is NULL
> ----------------------------------------------------
>
>                 Key: ASTERISK-26286
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26286
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 13.9.1
>         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
>            Reporter: Drew Dickenson
>            Assignee: Unassigned
>         Attachments: extensions.conf, messages.trk, queue_log, queues.conf
>
>
> 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 at 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 at 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"



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list