[Home]

Summary:ASTERISK-19429: ERROR[23303]: astobj2.c:110 INTERNAL_OBJ: user_data is NULL when login to AMI
Reporter:Vladimir Astafiev (vldmr)Labels:
Date Opened:2012-02-23 13:38:20.000-0600Date Closed:2012-04-11 11:19:18
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/ManagerInterface
Versions:1.8.9.2 1.8.10.0 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:OS: CentOS 5.7 i386 Kernel: 2.6.18-274.18.1.el5 CPU: Dual-Core AMD Opteron(tm) Processor 1214 CLI> core show sysinfo System Statistics ----------------- System Uptime: 0 hours Total RAM: 2074996 KiB Free RAM: 1868608 KiB Buffer RAM: 14708 KiB Total Swap Space: 4128760 KiB Free Swap Space: 4128760 KiB Number of Processes: 134 Attachments:( 0) issue_19429_full_log
Description:Periodically when user log in to AMI, I got in CLI:

[Feb 23 23:19:11] ERROR[2757]: astobj2.c:110 INTERNAL_OBJ: user_data is NULL
[Feb 23 23:19:11] ERROR[2757]: astobj2.c:110 INTERNAL_OBJ: user_data is NULL
[Feb 23 23:19:11] ERROR[2757]: astobj2.c:110 INTERNAL_OBJ: user_data is NULL
[Feb 23 23:19:11] ERROR[2757]: astobj2.c:110 INTERNAL_OBJ: user_data is NULL
[Feb 23 23:19:11] ERROR[2757]: astobj2.c:110 INTERNAL_OBJ: user_data is NULL
[Feb 23 23:19:11] ERROR[2757]: astobj2.c:110 INTERNAL_OBJ: user_data is NULL
[Feb 23 23:19:11] ERROR[2757]: astobj2.c:110 INTERNAL_OBJ: user_data is NULL
[Feb 23 23:19:11] ERROR[2757]: astobj2.c:110 INTERNAL_OBJ: user_data is NULL
 == Manager 'test_op1' logged on from 192.168.1.10

EventFilters not working.
When I comment all users in manager.conf, reload manager, uncomment users, reload manager - all working fine.

my manager.conf:

[general]
enabled=yes
webenabled=yes
port = 5038
bindaddr = 0.0.0.0
channelvars=USERNAME
displayconnects = yes

[admin]
secret = password
read = all
write = all

[test_op1]
read=all
write=all
secret=1234
eventfilter=Username: test_op1

[test_op2]
read=all
write=all
secret=1234
eventfilter=Username: test_op2
Comments:By: Matt Jordan (mjordan) 2012-02-23 16:40:17.351-0600

We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information


By: Vladimir Astafiev (vldmr) 2012-03-07 09:18:07.626-0600

I'm update to 1.8.10, restart dahdi & asterisk and get this issue again.
By: Matt Jordan (mjordan) 2012-03-27 10:02:22.216-0500

First of all, when you enter feedback you have to use the "Enter Feedback" option.  Otherwise, it never gets sent back to the bug marshals, and we have no notification that you've provided feedback.

Second, what you've attached is not a DEBUG log.  Please follow the instructions on the wiki and attach a DEBUG log.
By: Matt Jordan (mjordan) 2012-04-11 11:19:13.136-0500

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines


By: Jaco van Niekerk (faqterson) 2014-01-09 08:51:20.655-0600

I am getting the exact same error, just opening the AMI port creates the error:
ERROR[13355]: astobj2.c:146 INTERNAL_OBJ: user_data is NULL