| Summary: | ASTERISK-18281: ERROR[3385]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x0 for 0x11f76860 | ||
| Reporter: | Ross Beer (rossbeer) | Labels: | |
| Date Opened: | 2011-08-17 09:33:44 | Date Closed: | 2011-09-13 10:54:58 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Core/PBX |
| Versions: | 1.8.6.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Cent OS 5.5 | Attachments: | |
| Description: | In the CLI, I am receiving thousands of error messages stating: [Aug 17 15:01:33] ERROR[3385]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x0 for 0x11f76860 [Aug 17 15:01:33] ERROR[3385]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x0 for 0x11f76860 [Aug 17 15:01:33] ERROR[3385]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x0 for 0x11f76860 [Aug 17 15:01:33] ERROR[3385]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x0 for 0x11f76860 It appears to happen randomly. I had this issue with version 1.8.5 however since I upgraded a test box to 1.8.6.0 it no longer causes a seg fault as it did before. Therefore it's just the messages being displayed. There are very few phones registered to the test server using BLF, this can happen at any time even when not making calls so may be related to BLF or registers. There is a MySQL realtime database in use along with BLF using wild cards. | ||
| Comments: | By: Ross Beer (rossbeer) 2011-09-01 02:55:34.258-0500 After upgrading the MySQL ODBC connector on Cent OS 5.5 to version 5 asterisk has not shown any further 'bad magic numbers'. I will continue to monitor to confirm. By: Ross Beer (rossbeer) 2011-09-13 10:54:58.385-0500 Upgrading MySQL ODBC connector resolved the issue | ||