Summary: | ASTERISK-25768: astobj2.c:124 INTERNAL_OBJ: bad magic number [..] for object [..] | ||
Reporter: | Ronaldo Rathis Sacco (ronaldo.sacco) | Labels: | |
Date Opened: | 2016-02-10 06:52:48.000-0600 | Date Closed: | 2016-02-10 07:46:28.000-0600 |
Priority: | Critical | Regression? | |
Status: | Closed/Complete | Components: | Channels/chan_sip/General |
Versions: | 1.8.31.1 1.8.32.3 | Frequency of Occurrence | Frequent |
Related Issues: | |||
Environment: | Ubuntu 12.04 LTS model name : Intel(R) Celeron(R) CPU J1800 @ 2.41GHz MemTotal: 4016276 kB Asterisk 1.8.32.3 Linux asterisk-prefeitura-npt 3.2.0-23-generic-pae #36-Ubuntu SMP Tue Apr 10 22:19:09 UTC 2012 i686 i686 i386 GNU/Linux | Attachments: | ( 0) backtrace.txt ( 1) console_full_logs.txt |
Description: | Many message of "bad magic number" appears and after asterisk stops automatically (or restart if I use safe_asterisk). Last time, appeared more then 400 times (about 10 per second).
The message is: [Feb 10 08:41:32] ERROR[29506] astobj2.c: bad magic number for object 0xb6e9a728. Object is likely destroyed. or, sometimes: [Feb 10 08:41:34] ERROR[29506] astobj2.c: bad magic number 0x4d584157 for object 0xb6e9a728 I dont know exactly how to reproduce this error. But it happens ~5 times per week. I tried to change version, but same error happened. On that server have about 92 SIP peers and more 100 analogic peers (Khomp device). Attached are complete logs and gdb file. | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-02-10 06:52:49.877-0600 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: Ronaldo Rathis Sacco (ronaldo.sacco) 2016-02-10 06:56:12.444-0600 backtrace file By: Ronaldo Rathis Sacco (ronaldo.sacco) 2016-02-10 07:03:44.284-0600 full logs from console when that error happens By: Joshua C. Colp (jcolp) 2016-02-10 07:46:08.973-0600 Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions The information you have provided is against 1.8, if this is happening in a supported version (such as 11 or 13) please provide information for that instead. As well as you are using a third party channel driver it may be required that you provide a backtrace from an environment that is not using it. |