星号失败 - 核心生成

时间:2015-01-09 13:02:10

标签: centos asterisk core

昨天,我用centOS 6.5和Asterisk 11.13.1监视我的服务器。

一切都很完美,一切顺利,但到了下午,Asterisk死了,产生了一个核心。

我试图破译日志但没有成功。

你能帮助我吗?希望我能知道发生了什么。

非常感谢!!!

Core was generated by `/usr/sbin/asterisk -f -vvvg'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000000000447a70 in internal_ao2_link (c=0x27fc4a8, user_data=0x7f109b08f8c8, flags=<value optimized out>, tag=0x0, file=0x596a98 "astobj2.c", line=929, func=0x596c42 "__ao2_link") at astobj2.c:904
904     AST_LIST_INSERT_TAIL(&c->buckets[i], p, entry);
Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-13.el6_3.1.x86_64 glibc-2.12-1.107.el6_4.5.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-10.el6_4.6.x86_64 libcom_err-1.41.12-14.el6_4.4.x86_64 libcurl-7.19.7-37.el6_4.x86_64 libgcc-4.4.7-3.el6.x86_64 libidn-1.18-2.el6.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64 libssh2-1.4.2-1.el6.x86_64 libstdc++-4.4.7-3.el6.x86_64 libxml2-2.7.6-14.el6_5.2.x86_64 ncurses-libs-5.7-3.20090208.el6.x86_64 nspr-4.9.5-2.el6_4.x86_64 nss-3.14.3-4.el6_4.x86_64 nss-softokn-freebl-3.14.3-3.el6_4.x86_64 nss-util-3.14.3-3.el6_4.x86_64 openldap-2.4.23-32.el6_4.1.x86_64 openssl-1.0.1e-16.el6_5.7.x86_64 postgresql93-libs-9.3.5-1PGDG.rhel6.x86_64 sqlite-3.6.20-1.el6.x86_64 zlib-1.2.3-29.el6.x86_64
(gdb) where
#0  0x0000000000447a70 in internal_ao2_link (c=0x27fc4a8, user_data=0x7f109b08f8c8, flags=<value optimized out>, tag=0x0, file=0x596a98 "astobj2.c", line=929, func=0x596c42 "__ao2_link") at astobj2.c:904
#1  0x0000000000447bcf in __ao2_link (c=<value optimized out>, obj_new=<value optimized out>, flags=<value optimized out>) at astobj2.c:929
#2  0x000000000047c4da in __ast_channel_alloc_ap (needqueue=<value optimized out>, state=0, cid_num=0x841826 "", cid_name=0x841826 "", acctcode=0x841826 "", exten=0x841826 "", context=0x7f109b8980c8 "server", 
    linkedid=0x7f109a96e8e8 "1420651982.13202891", amaflag=0, file=0x7f12b39b5971 "chan_sip.c", line=7918, function=0x7f12b39bee92 "sip_new", name_fmt=0x7f12b39b8656 "SIP/%s-%08x", ap=0x7f0f86c96450)
    at channel.c:1136
#3  0x000000000047ca95 in __ast_channel_alloc (needqueue=<value optimized out>, state=<value optimized out>, cid_num=<value optimized out>, cid_name=<value optimized out>, acctcode=<value optimized out>, 
    exten=<value optimized out>, context=0x7f109b8980c8 "server", linkedid=0x7f109a96e8e8 "1420651982.13202891", amaflag=0, file=0x7f12b39b5971 "chan_sip.c", line=7918, function=0x7f12b39bee92 "sip_new", 
    name_fmt=0x7f12b39b8656 "SIP/%s-%08x") at channel.c:1190
#4  0x00007f12b394a4c8 in sip_new (i=0x7f109b892898, state=0, title=<value optimized out>, linkedid=0x7f109a96e8e8 "1420651982.13202891", callid=0x7f109ac0e340) at chan_sip.c:7918
#5  0x00007f12b39763b3 in sip_request_call (type=<value optimized out>, cap=0x7f109b6a85c0, requestor=0x7f109a457288, dest=<value optimized out>, cause=0x7f109b8928b8) at chan_sip.c:30051
#6  0x0000000000477f52 in ast_request (type=0x7f1098f0ace0 "SIP", request_cap=0x7f1099cd2280, requestor=0x7f109a457288, addr=0x7f1098f0ace8 "server334S258/101S0312125390450S65116093", cause=0x7f0f86c98358)
    at channel.c:5973
#7  0x00007f12a1f40067 in dial_exec_full (chan=<value optimized out>, data=<value optimized out>, peerflags=0x7f0f86c983b0, continue_exec=0x0) at app_dial.c:2434
#8  0x00007f12a1f42f06 in dial_exec (chan=<value optimized out>, data=<value optimized out>) at app_dial.c:3130
#9  0x000000000051f494 in pbx_exec (c=0x7f109a457288, app=0x2e4e040, data=0x7f0f86c98a2a "SIP/server334S258/101S0312125390450S65116093,30000,S(3600)T") at pbx.c:1622
#10 0x00007f12e9478ce7 in handle_exec (chan=0x7f109a457288, agi=0x7f0f86c9a4d0, argc=3, argv=0x7f0f86c98590) at res_agi.c:2561
#11 0x00007f12e947b881 in agi_handle_command (chan=0x7f109a457288, agi=0x7f0f86c9a4d0, buf=0x7f0f86c98a20 "EXEC", dead=0) at res_agi.c:3458
#12 0x00007f12e947bfc4 in run_agi (chan=0x7f109a457288, request=0x7f0f86c992a0 "agi://localhost/dialer_handler", agi=0x7f0f86c9a4d0, pid=-1, status=0x7f0f86c9a538, dead=<value optimized out>, argc=1, 
    argv=0x7f0f86c99b08) at res_agi.c:3656
#13 0x00007f12e947d7c5 in agi_exec_full (chan=0x7f109a457288, data=<value optimized out>, enhanced=<value optimized out>, dead=0) at res_agi.c:3941
#14 0x000000000051f494 in pbx_exec (c=0x7f109a457288, app=0x285bf40, data=0x7f0f86c9c680 "agi://localhost/dialer_handler") at pbx.c:1622
#15 0x000000000052ca67 in pbx_extension_helper (c=0x7f109a457288, con=0x0, context=<value optimized out>, exten=<value optimized out>, priority=5, label=0x0, callerid=0x7f10991832a0 "'31950900'", 
    action=E_SPAWN, found=0x7f0f86c9ecfc, combined_find_spawn=1) at pbx.c:4915
#16 0x0000000000530d85 in ast_spawn_extension (c=0x7f109a457288, args=0x0) at pbx.c:6031
#17 __ast_pbx_run (c=0x7f109a457288, args=0x0) at pbx.c:6506
#18 0x000000000053258b in pbx_thread (data=<value optimized out>) at pbx.c:6836
#19 0x000000000057392b in dummy_start (data=<value optimized out>) at utils.c:1169
#20 0x00007f12ecafa851 in start_thread () from /lib64/libpthread.so.0
#21 0x00007f12ee0c494d in clone () from /lib64/libc.so.6

1 个答案:

答案 0 :(得分:0)

您可以参考此页面

http://www.voip-info.org/wiki/view/Asterisk+debugging

但无论如何,它需要c / c ++和asterisk internals的guru等级。

相关问题