| Summary: | ASTERISK-27327: glibc detected | ||||
| Reporter: | PowerPBX (PowerPBX) | Labels: | |||
| Date Opened: | 2017-10-09 14:25:13 | Date Closed: | 2017-10-09 14:31:33 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | |||
| Versions: | 13.17.2 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | CentOS v6 x86, latest updates | Attachments: | |||
| Description: | Without making any other changes, downgrading from v13.17.2 to v13.15.0 corrects problem. I am compiling asterisk from source with ./configure --with-pjproject-bundled
It may have shown up on versions prior to 13.17.2. I can reproduce this on multiple servers including a from scratch install. To reproduce run "core restart gracefully" as follows with the resulting error shown. Seems to happen quite consistently but not always and may need an asterisk restart first. CLI> core restart gracefully CLI> *** glibc detected *** /usr/sbin/asterisk: corrupted double-linked list: 0x098fafc8 *** ======= Backtrace: ========= /lib/libc.so.6(+0x70bb1)[0xb755abb1] /lib/libc.so.6(+0x70e4d)[0xb755ae4d] /lib/libc.so.6(+0x744cd)[0xb755e4cd] /lib/libc.so.6(__libc_calloc+0xab)[0xb755ef1b] /usr/sbin/asterisk(__ast_calloc_with_stringfields+0x46)[0x820ea26] /usr/sbin/asterisk[0x816ee83] /usr/sbin/asterisk[0x816dd01] /usr/sbin/asterisk(ast_log_callid+0x2f)[0x816deef] /usr/sbin/asterisk(__ast_verbose_ap+0x1fc)[0x816eb5c] /usr/sbin/asterisk(__ast_verbose+0x40)[0x816f810] /usr/sbin/asterisk(ast_cdr_unregister+0x127)[0x80d63b7] /usr/lib/asterisk/modules/cdr_mysql.so(+0x38ee)[0xb54518ee] /usr/sbin/asterisk[0x81692f7] /usr/sbin/asterisk[0x80944b5] /usr/sbin/asterisk[0x80952d5] /usr/sbin/asterisk(ast_cli_command_full+0x250)[0x810f080] /usr/sbin/asterisk(ast_cli_command_multiple_full+0x6c)[0x810f27c] /usr/sbin/asterisk[0x8092d8a] /usr/sbin/asterisk[0x822769b] /lib/libpthread.so.0(+0x6bc9)[0xb76a2bc9] /lib/libc.so.6(clone+0x5e)[0xb75cd04e] ======= Memory map: ======== 00101000-0010b000 r-xp 00000000 09:02 23351507 /lib/libkrb5support.so.0.1 0010b000-0010c000 r--p 00009000 09:02 23351507 /lib/libkrb5support.so.0.1 0010c000-0010d000 rw-p 0000a000 09:02 23351507 /lib/libkrb5support.so.0.1 0010f000-00116000 r-xp 00000000 09:02 23351505 /lib/libacl.so.1.1.0 00116000-00117000 r--p 00006000 09:02 23351505 /lib/libacl.so.1.1.0 00117000-00118000 rw-p 00007000 09:02 23351505 /lib/libacl.so.1.1.0 0011a000-0011c000 r-xp 00000000 09:02 23351260 /lib/libkeyutils.so.1.3 0011c000-0011d000 r--p 00001000 09:02 23351260 /lib/libkeyutils.so.1.3 0011d000-0011e000 rw-p 00002000 09:02 23351260 /lib/libkeyutils.so.1.3 00120000-0015e000 r-xp 00000000 09:02 23351511 /lib/libgssapi_krb5.so.2.2 0015e000-0015f000 r--p 0003e000 09:02 23351511 /lib/libgssapi_krb5.so.2.2 0015f000-00160000 rw-p 0003f000 09:02 23351511 /lib/libgssapi_krb5.so.2.2 00162000-00188000 r-xp 00000000 09:02 23351477 /lib/libexpat.so.1.5.2 00188000-0018a000 rw-p 00025000 09:02 23351477 /lib/libexpat.so.1.5.2 001b6000-0026c000 r-xp 00000000 09:02 25716299 /usr/lib/libgnutls.so.26.22.6 0026c000-00270000 rw-p 000b6000 09:02 25716299 /usr/lib/libgnutls.so.26.22.6 002da000-002f1000 r-xp 00000000 09:02 25716286 /usr/lib/libelf-0.164.so 002f1000-002f2000 ---p 00017000 09:02 25716286 /usr/lib/libelf-0.164.so 002f2000-002f3000 r--p 00017000 09:02 25716286 /usr/lib/libelf-0.164.so 002f3000-002f4000 rw-p 00018000 09:02 25716286 /usr/lib/libelf-0.164.so 002f6000-0031e000 r-xp 00000000 09:02 23351508 /lib/libk5crypto.so.3.1 0031e000-0031f000 r--p 00028000 09:02 23351508 /lib/libk5crypto.so.3.1 0031f000-00320000 rw-p 00029000 09:02 23351508 /lib/libk5crypto.so.3.1 00320000-00321000 rw-p 00000000 00:00 0 00323000-00346000 r-xp 00000000 09:02 25716287 /usr/lib/liblzma.so.0.0.0 00346000-00347000 rw-p 00022000 09:02 25716287 /usr/lib/liblzma.so.0.0.0 00349000-0034c000 r-xp 00000000 09:02 23351504 /lib/libcap.so.2.16 0034c000-0034d000 rw-p 00002000 09:02 23351504 /lib/libcap.so.2.16 0034f000-00398000 r-xp 00000000 09:02 25716300 /usr/lib/libssl3.so 00398000-0039a000 r--p 00049000 09:02 25716300 /usr/lib/libssl3.so 0039a000-0039b000 rw-p 0004b000 09:02 25716300 /usr/lib/libssl3.so 0039d000-003c5000 r-xp 00000000 09:02 25716301 /usr/lib/libsmime3.so 003c5000-003c7000 r--p 00028000 09:02 25716301 /usr/lib/libsmime3.so 003c7000-003c8000 rw-p 0002a000 09:02 25716301 /usr/lib/libsmime3.so 003ca000-00510000 r-xp 00000000 09:02 25715497 /usr/lib/libxml2.so.2.7.6 00510000-00515000 rw-p 00145000 09:02 25715497 /usr/lib/libxml2.so.2.7.6 00515000-00516000 rw-p 00000000 00:00 0 00567000-005c9000 r-xp 00000000 09:02 25716305 /usr/lib/libssl.so.1.0.1e 005c9000-005cc000 r--p 00061000 09:02 25716305 /usr/lib/libssl.so.1.0.1e 005cc000-005d0000 rw-p 00064000 09:02 25716305 /usr/lib/libssl.so.1.0.1e 005d2000-005fe000 r-xp 00000000 09:02 25716288 /usr/lib/liblua-5.1.so 005fe000-005ff000 rw-p 0002c000 09:02 25716288 /usr/lib/liblua-5.1.so 007dc000-007de000 r-xp 00000000 09:02 25713883 /usr/lib/libresample.so.1.0 007de000-007df000 rw-p 00001000 09:02 25713883 /usr/lib/libresample.so.1.0 00800000-00811000 r-xp 00000000 09:02 25715514 /usr/lib/libodbcinst.so.2.0.0 00811000-00812000 rw-p 00010000 09:02 25715514 /usr/lib/libodbcinst.so.2.0.0 00837000-00849000 r-xp 00000000 09:02 23351478 /lib/libz.so.1.2.3 00849000-0084a000 r--p 00011000 09:02 23351478 /lib/libz.so.1.2.3 0084a000-0084b000 rw-p 00012000 09:02 23351478 /lib/libz.so.1.2.3 0084d000-0086a000 r-xp 00000000 09:02 23351474 /lib/libselinux.so.1 0086a000-0086b000 r--p 0001d000 09:02 23351474 /lib/libselinux.so.1 0086b000-0086c000 rw-p 0001e000 09:02 23351474 /lib/libselinux.so.1 0086e000-00884000 r-xp 00000000 09:02 23351496 /lib/libtinfo.so.5.7 00884000-00887000 rw-p 00015000 09:02 23351496 /lib/libtinfo.so.5.7 00889000-00917000 r-xp 00000000 09:02 25716302 /usr/lib/libsqlite3.so.0.8.6 00917000-00919000 rw-p 0008d000 09:02 25716302 /usr/lib/libsqlite3.so.0.8.6 Disconnected from Asterisk server Asterisk cleanly ending (0). Executing last minute cleanups | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-10-09 14:25:14.620-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: Joshua C. Colp (jcolp) 2017-10-09 14:31:33.950-0500 This is the same underlying problem as ASTERISK-27270. | ||||