Hello,
I am not sure if there is a better venue for posting this report, so I'll post it here.
I'm running mediaproxy-ng master:cb6990e43864b077dd6a24acfbdf5ef76c1a427e (4 April 2014), pre rtpengine and all that. It crashed yesterday, with an estimated 700 concurrent calls running.
Core dump says:
(gdb) where #0 monologue_offer_answer (monologue=0x0, streams=0x7f5bbff464c0, flags= 0x7f5bbff46430) at call.c:1711 #1 0x000000000041e160 in call_offer_answer_ng (input=<value optimized out>, m= 0x1c19800, output=0x7f5ba00c3c18, opmode=<value optimized out>) at call_interfaces.c:534 #2 0x0000000000414bdc in control_ng_incoming (obj=0x1c1c830, buf=<value optimized out>, sin=0x7f5bbff56700, addr= 0x7f5bbff566c0 "xxx.xxx.xxx.xxx:37956") at control_ng.c:115 #3 0x00000000004140ce in udp_listener_incoming (fd=6, p=0x1c1ba70, x=<value optimized out>) at udp_listener.c:52 #4 0x00000000004094be in poller_poll (p=0x1c179b0, timeout=<value optimized out>) at poller.c:354 #5 0x000000000040710d in poller_loop (d=0x1c179b0) at main.c:522 #6 0x000000000040a1cf in thread_detach_func (d=0x1c142b0) at aux.c:160 #7 0x000000304e6079d1 in start_thread () from /lib64/libpthread.so.0 #8 0x000000304e2e8b6d in clone () from /lib64/libc.so.6
That's all I've got, and I highly, highly doubt I can reproduce this. It's just something that happened after a certain amount of operation.
Any insights would be appreciated. Thanks!
-- Alex
On 06/06/14 08:51, Alex Balashov wrote:
Hello,
I am not sure if there is a better venue for posting this report, so I'll post it here.
I'm running mediaproxy-ng master:cb6990e43864b077dd6a24acfbdf5ef76c1a427e (4 April 2014), pre rtpengine and all that. It crashed yesterday, with an estimated 700 concurrent calls running.
Can you post the log messages leading up to the crash?
cheers
On 06/06/2014 09:01 AM, Richard Fuchs wrote:
On 06/06/14 08:51, Alex Balashov wrote:
Hello,
I am not sure if there is a better venue for posting this report, so I'll post it here.
I'm running mediaproxy-ng master:cb6990e43864b077dd6a24acfbdf5ef76c1a427e (4 April 2014), pre rtpengine and all that. It crashed yesterday, with an estimated 700 concurrent calls running.
Can you post the log messages leading up to the crash?
I'm sorry, I don't think that's possible.
What I can add, which I forgot to do so in the initial post, is the exact line that caused the crash:
#0 monologue_offer_answer (monologue=0x0, streams=0x7f5bbff464c0, flags=0x7f5bbff46430) at call.c:1711 1711 struct call_monologue *other_ml = monologue->active_dialogue; Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-13.el6_3.1.x86_64 glib2-2.26.1-7.el6_5.x86_64 glibc-2.12-1.132.el6.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-18.el6.x86_64 libcurl-7.19.7-37.el6_4.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 libxml2-2.7.6-14.el6.x86_64 nspr-4.10.2-1.el6_5.x86_64 nss-3.15.3-6.el6_5.x86_64 nss-softokn-freebl-3.14.3-9.el6.x86_64 nss-util-3.15.3-1.el6_5.x86_64 openldap-2.4.23-34.el6_5.1.x86_64 openssl-1.0.1e-16.el6_5.4.x86_64 pcre-7.8-6.el6.x86_64 xmlrpc-c-1.16.24-1210.1840.el6.x86_64 xmlrpc-c-client-1.16.24-1210.1840.el6.x86_64 zlib-1.2.3-29.el6.x86_64
But you already know there's going to be a problem if monologue == NULL, so that's not very informative.
-- Alex
On 06/06/14 09:25, Alex Balashov wrote:
But you already know there's going to be a problem if monologue == NULL, so that's not very informative.
Looking through the code, I think it's probably just a case of a missing NULL check. If I'm right, then this would be the fix:
https://github.com/sipwise/rtpengine/commit/cbe1f805363b3d6a117e9e5425d79943...
cheers
On 06/06/2014 09:49 AM, Richard Fuchs wrote:
On 06/06/14 09:25, Alex Balashov wrote:
But you already know there's going to be a problem if monologue == NULL, so that's not very informative.
Looking through the code, I think it's probably just a case of a missing NULL check. If I'm right, then this would be the fix:
https://github.com/sipwise/rtpengine/commit/cbe1f805363b3d6a117e9e5425d79943...
Thank you very much, Richard.
Though, one wonders as to the strange circumstances in which monologue == NULL.
-
Alex Balashov -
Richard Fuchs