[OpenSIPS-Users] Core Dump

[opensipslist at encambio.com]

Hello Bogdan,

An sam., févr 27, 2010, opensipslist at encambio.com schrieb:
>An lun., févr 22, 2010, Bogdan-Andrei Iancu schrieb:
>>Maybe you should consider reporting the crashing you are mentioning
>>(if they are so many as you say), so somebody could fix them - in
>>this case everybody will be happier , I guess.
>>
>Here's a backtrace of the OpenSIPS 1.6.0 sometime after INVITE
>request comes in:
>
# gdb /pfx/sbin/opensips opensips.1234.name.host.tld.core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i386-pc-solaris2.11"...
(no debugging symbols found)
Reading symbols from /lib/ld.so.1...done.
Loaded symbols for /lib/ld.so.1

Core was generated by `/pfx/sbin/opensips -P
/pfx/var/opensips/opensips.pid -m 64'.
Program terminated with signal 6, Aborted.
[New process 67527    ]
#0  0xd11d1d75 in _lwp_kill () from /lib/libc.so.1
(gdb) bt
#0  0xd11d1d75 in _lwp_kill () from /lib/libc.so.1
#1  0xd11cb73d in thr_kill () from /lib/libc.so.1
#2  0xd1185722 in raise () from /lib/libc.so.1
#3  0xd1162c7d in abort () from /lib/libc.so.1
#4  0x0808c900 in ?? ()
#5  0x0000001a in ?? ()
#6  0x0826115c in ?? ()
#7  0x082629ac in ?? ()
#8  0xd1268ac0 in _uberdata () from /lib/libc.so.1
#9  0x00000000 in ?? ()
(gdb)

>If it crashes or not it depends a lot of what functionalities
>(modules) you are using (nobody can claim he tested all the modules
>in all possible combinations).
>
This time I don't see where the crash could have happened, maybe
the in the OpenSIPS 1.6.0 core? Here's the last message in the
sip trace before the crash (not sure if it's representative.)

INVITE:477:tls:1.2.3.4:5061:tls:4.3.2.1:1234:ck1b40kwzn:out
7070:1267304859:3c2e8013a0e7-x8fz99gffcy0::SIP/2.0 477 Send failed (477/TM)
Via: SIP/2.0/TLS 192.168.130.130:1234;branch=z9hG4bK-cuia8rmsu1z3;rport=1234;received=4.3.2.1
From: "User-Me" <sip:User-Name at name.host.tld>;tag=ck1b40kwzn
To: <sip:+123454321 at name.host.tld;user=phone>;tag=c3f9bc8b6c0d893b80d355b0f89fbe37-0bbd
Call-ID: 3c2e8013a0e7-x8fz99gffcy0
CSeq: 1 INVITE
Server: OpenSIPS (1.6.0-tls (i386/solaris))
Content-Length: 0
Warning: 392 name.host.tld:5061 "Noisy feedback tells:  pid=2000 req_src_ip=4.3.2.1 req_src_port=1234 in_uri=sip:+123454321 at name.host.tld;user=phone out_uri=sips:niklas at name.host.tld via_cnt==1"

Here are the last few lines from the log before hundreds of memory
debug lines appear (because I have memory debugging on.)

Feb 27 21:44:25 name.host.tld <warning> opensips[3996]: INVITE: Noncancelled fail route [408]
Feb 27 21:44:25 name.host.tld <error> opensips[3996]: ERROR:core:warning_builder: buffer size exceeded
Feb 27 21:44:25 name.host.tld <warning> opensips[3996]: WARNING:core:build_res_buf_from_sip_req: warning skipped -- too big
Feb 27 22:07:39 name.host.tld <critical> opensips[4001]: CRITICAL:core:receive_fd: EOF on 20
Feb 27 22:07:39 name.host.tld <warning> opensips[3994]: Memory status (pkg):
Feb 27 22:07:39 name.host.tld <warning> opensips[3994]: qm_status (8311c20):

If you like I can send more of the memory debug log lines, but
please tell me just what to send (so I can avoid sending hundreds
of lines of log text.)

>For example I'm running opensips.org SIP service with SVN trunk
>and I do not get any core dumps... and it is an almost 3K lines
>config...
>
This time OpenSIPS crashed after only one day, which is unusual for
the 1.6.0 release which usually lasts longer.

>So, again, if you get crashes, please report them.
>
Okay, I'll keep doing that.

Regards,
Brian