Core dump , how to fix


#1

Program terminated with signal 6, Aborted.
#0 0x00007f4398d04277 in __GI_raise (sig=sig@entry=6) at …/nptl/sysdeps/unix/sysv/linux/raise.c:56
56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0 0x00007f4398d04277 in __GI_raise (sig=sig@entry=6) at …/nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007f4398d05968 in __GI_abort () at abort.c:90
#2 0x00007f4398d46d37 in __libc_message (do_abort=2, fmt=fmt@entry=0x7f4398e58d58 “*** Error in `%s’: %s: 0x%s ***\n”) at …/sysdeps/unix/sysv/linux/libc_fatal.c:196
#3 0x00007f4398d50c86 in malloc_printerr (ar_ptr=0x7f431c000020, ptr=0x7f431c07f9e0, str=0x7f4398e5645b “malloc(): memory corruption”, action=) at malloc.c:5025
#4 _int_malloc (av=av@entry=0x7f431c000020, bytes=bytes@entry=568) at malloc.c:3473
#5 0x00007f4398d5384c in __GI___libc_malloc (bytes=bytes@entry=568) at malloc.c:2899
#6 0x00007f4398d3ca4d in __fopen_internal (filename=0x7f43330dd54e “/etc/hosts”, mode=0x7f43330dd52d “rce”, is32=1) at iofopen.c:73
#7 0x00007f43330d89ef in internal_setent (stayopen=0) at nss_files/files-XXX.c:79
#8 _nss_files_gethostbyname4_r (name=name@entry=0x7f42e0d7a6c0 “iz2ze7i2yy5u80gpa5m58nz”, pat=pat@entry=0x7f42e0d79fe0, buffer=0x7f42e0d7a260 “”, buflen=1024, errnop=errnop@entry=0x7f42e0d7e5f0,
herrnop=herrnop@entry=0x7f42e0d7e66c, ttlp=ttlp@entry=0x0) at nss_files/files-hosts.c:384
#9 0x00007f4398db4494 in gaih_inet (name=, name@entry=0x7f42e0d7a6c0 “iz2ze7i2yy5u80gpa5m58nz”, service=, req=req@entry=0x7f42e0d7a730, pai=pai@entry=0x7f42e0d7a1d0,
naddrs=naddrs@entry=0x7f42e0d7a1c0, tmpbuf=tmpbuf@entry=0x7f42e0d7a250) at …/sysdeps/posix/getaddrinfo.c:790
#10 0x00007f4398db5834 in __GI_getaddrinfo (name=0x7f42e0d7a6c0 “iz2ze7i2yy5u80gpa5m58nz”, service=, hints=0x7f42e0d7a730, pai=0x7f42e0d7a728) at …/sysdeps/posix/getaddrinfo.c:2304
#11 0x00000000005b76d9 in ast_sockaddr_resolve (addrs=0x7f42e0d7a7f0, str=0x7f42e0d7a8d0 “iz2ze7i2yy5u80gpa5m58nz”, flags=768, family=0) at netsock2.c:304
#12 0x00000000004485e1 in resolve_first (addr=0x7f42e0d7ab60, name=0x7f42e0d7a8d0 “iz2ze7i2yy5u80gpa5m58nz”, flag=768, family=0) at acl.c:792
#13 0x0000000000448d4f in ast_find_ourip (ourip=0x7f42e0d7ab60, bindaddr=0x7f42e0d7aad0, family=0) at acl.c:970
#14 0x00007f42f4ed90a3 in ast_rtcp_read (instance=instance@entry=0x7f432c4a4030) at res_rtp_asterisk.c:4248
#15 0x00007f42f4ed9d36 in ast_rtp_read (instance=0x7f432c4a4030, rtcp=) at res_rtp_asterisk.c:4408
#16 0x000000000060b714 in ast_rtp_instance_read (instance=0x7f432c4a4030, rtcp=1) at rtp_engine.c:476
#17 0x00007f4310838a8d in sip_rtp_read (ast=0x7f432c4ecd40, p=0x7f432c5303e0, faxdetect=0x7f42e0d7d174) at chan_sip.c:8520
#18 0x00007f43108392c1 in sip_read (ast=0x7f432c4ecd40) at chan_sip.c:8623
#19 0x00000000004c8dd9 in __ast_read (chan=0x7f432c4ecd40, dropaudio=0) at channel.c:3946
#20 0x00000000004ca81c in ast_read (chan=0x7f432c4ecd40) at channel.c:4353


#2

A backtrace provides information about what was happening at the time of a crash. There is no guide on how to fix what a backtrace shows because it depends on what it is and is usually the first step to understanding a crash, you usually have to dig deeper. In your case we asked the system to resolve something and it crashed. I don’t know why it did that. What version of Asterisk? What Linux distribution or environment? What CPU?


#3

asterisk-14.0.1 centos 7.5 Intel® Xeon® Platinum 8163 CPU @ 2.50GHz


#4

Asterisk 14 is no longer supported, and CentOS is a platform we regularly test on. I’d suggest trying a supported version[1] before pursuing it any further.

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions


#5

The abort is due to memory corruption and the actually failure an be in a completely different thread from that which eventually crashes.