[OpenSIPS-Users] opensips 3.2.2 Segfault on debian 11 bullseye

James Fox jpfox156 at yahoo.com.au
Sun Sep 26 12:48:02 EST 2021


Hi Liviu,

 

Thanks for your response. I’m still experiencing the segfault after upgrading to 3.2.2.

 

I’ve managed to output a stack trace from the core dump. I believe it shows the segfault occurring on MD5Update().

 

Reading symbols from /usr/sbin/opensips...

(No debugging symbols found in /usr/sbin/opensips)

[New LWP 92955]

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".

Core was generated by `/usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.

Program terminated with signal SIGSEGV, Segmentation fault.

--Type <RET> for more, q to quit, c to continue without paging--c

#0  0x0000aaaaba47c7c8 in ?? ()

(gdb) bt full

#0  0x0000aaaaba47c7c8 in ?? ()

No symbol table info available.

#1  0x0000aaaaba47d2cc in MD5Update ()

No symbol table info available.

#2  0x0000ffffac85c8fc in ?? ()

   from /usr/lib/aarch64-linux-gnu/opensips/modules/auth.so

No symbol table info available.

#3  0x0000ffffac858678 in ?? ()

   from /usr/lib/aarch64-linux-gnu/opensips/modules/auth.so

No symbol table info available.

#4  0x0000ffffac5aec20 in ?? ()

   from /usr/lib/aarch64-linux-gnu/opensips/modules/auth_db.so

No symbol table info available.

#5  0x0000ffffac5afb28 in www_authorize ()

   from /usr/lib/aarch64-linux-gnu/opensips/modules/auth_db.so

No symbol table info available.

#6  0x0000aaaaba491d1c in do_action ()

No symbol table info available.

#7  0x0000aaaaba4944a8 in run_action_list ()

No symbol table info available.

#8  0x0000aaaaba4daf9c in ?? ()

No symbol table info available.

#9  0x0000aaaaba4da94c in eval_expr ()

--Type <RET> for more, q to quit, c to continue without paging--c

No symbol table info available.

#10 0x0000aaaaba4daa14 in eval_expr ()

No symbol table info available.

#11 0x0000aaaaba491c84 in do_action ()

No symbol table info available.

#12 0x0000aaaaba4944a8 in run_action_list ()

No symbol table info available.

#13 0x0000aaaaba493b28 in do_action ()

No symbol table info available.

#14 0x0000aaaaba4944a8 in run_action_list ()

No symbol table info available.

#15 0x0000aaaaba492fac in do_action ()

No symbol table info available.

#16 0x0000aaaaba4944a8 in run_action_list ()

No symbol table info available.

#17 0x0000aaaaba493b28 in do_action ()

No symbol table info available.

#18 0x0000aaaaba4944a8 in run_action_list ()

No symbol table info available.

#19 0x0000aaaaba494814 in run_top_route ()

No symbol table info available.

#20 0x0000aaaaba4a36ec in receive_msg ()

No symbol table info available.

#21 0x0000aaaaba61af20 in ?? ()

No symbol table info available.

#22 0x0000aaaaba5f2248 in ?? ()

No symbol table info available.

#23 0x0000aaaaba5f6e00 in udp_start_processes ()

No symbol table info available.

#24 0x0000aaaaba472ae4 in main ()

No symbol table info available.

 

 

Client is performing MD5 authentication using the following header (anonymised):

Authorization: Digest username="username", realm="realm", nonce="+P1CdVJHGkKtXhTn4vsZUwM66e8TYcsFS0V0cIYYcrsA", uri="sip:ipaddress", response="32charhash", cnonce="32charhash", qop=auth, nc=00000001

 

Any help would be appreciated.

 

Regards,

 

James

 

From: Liviu Chircu <liviu at opensips.org> 
Sent: Saturday, 25 September 2021 1:03 AM
To: James Fox <jpfox156 at yahoo.com.au>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] opensips 3.2.2 Segfault on debian 11 bullseye

 

On 24.09.2021 17:53, James Fox via Users wrote:

Previously this script was working with Opensips 3.1.1. I’ve manually upgraded the subscriber database schema to include the new column: ha1_sha512t256. 

I’ll work on getting a crash dump. Any ideas in the meantime would be welcome. 

Hi,

This bug was fixed ~2 months ago, and I'm pretty sure that both 3.2.0 or 3.1.1 minors date *before* the fix.  So please update your repo, grab the latest minor release for each of them and the bug should go away.

Best,

-- 
Liviu Chircu
www.twitter.com/liviuchircu <http://www.twitter.com/liviuchircu>  | www.opensips-solutions.com <http://www.opensips-solutions.com> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210926/f6352006/attachment-0001.html>


More information about the Users mailing list