[OpenSIPS-Users] opensips crash when doing load test

[Ramachandran, Agalya (Contractor)]

Sure. I will test and share the results by end of day or tomorrow.

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
Sent: Wednesday, October 05, 2016 10:47 AM
To: Ramachandran, Agalya (Contractor) <Agalya_Ramachandran at comcast.com>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: opensips crash when doing load test

Yes, that is ok (without the REST) - just to be sure which patch introduces the bug.

Regards,



Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 05.10.2016 17:45, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

I have observed one more thing. In the same source code, when opensips acts as pure proxy no HTTP call is made opensips is not crashing.
I suspect the crashes may be due to the new async fix provided.

I can do load test in 2.2, but it  will be just pure-proxy load test and not with the REST queries made.
If that is OK, I can test and share the results.

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
Sent: Wednesday, October 05, 2016 9:46 AM
To: Ramachandran, Agalya (Contractor) <Agalya_Ramachandran at comcast.com><mailto:Agalya_Ramachandran at comcast.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: opensips crash when doing load test

Hi Agalya,

That is really weird, as that field (my_T) is initialized (with the address of the transaction) when the transaction is created (for all the possible branches) and never reset or set again.

To avoid any regression due the patches you applied, could you please run your load test with the stock 2.2 code from git ? And see if the crash occurs again.

Regards,



Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 04.10.2016 19:51, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

Please find the values. Any common folder you have access for the outside world to put files?
If yes, share me the details. I can upload the core file there.

(gdb) print r_buf
$1 = (struct retr_buf *) 0x7fded2484098
(gdb) print *r_buf
$2 = {activ_type = 0, buffer = {
    s = 0x7fded0ca79f0 "INVITE sip:++12001000004 at 10.0.0.1:5060<mailto:sip:++12001000004 at 10.0.0.1:5060> SIP/2.0\r\nRecord-Route: <sip:96.119.240.35;lr>\r\nTo: sut <sip:+12452123456 at 10.0.0.1:5060;user=phone><mailto:sip:+12452123456 at 10.0.0.1:5060;user=phone>\r\nFrom: sipp <sip:sipp at 10.0.0.2:5060;user=phone<mailto:sip:sipp at 10.0.0.2:5060;user=phone>"..., len = 968}, dst = {proto = 1,
    proto_reserved1 = 0, to = {s = {sa_family = 2, sa_data = "\023\304`w\347\375\000\000\000\000\000\000\000"}, sin = {
        sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 4259805024}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {
        sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 4259805024, sin6_addr = {__in6_u = {
            __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}},
        sin6_scope_id = 0}}, send_sock = 0x7fded841dcb0}, retr_timer = {next_tl = 0x7fded1af3518, prev_tl = 0x7fded15c8ae0,
    ld_tl = 0x0, time_out = 169500000, timer_list = 0x7fded0acbc48, deleted = 1, set = 0}, fr_timer = {next_tl = 0x0, prev_tl = 0x0,
    ld_tl = 0x0, time_out = 165, timer_list = 0x7fded8005b00 <detached_timer>, deleted = 0, set = 0}, retr_list = RT_T2, my_T = 0x0,
  branch = 0}

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
Sent: Tuesday, October 04, 2016 11:52 AM
To: Ramachandran, Agalya (Contractor) <Agalya_Ramachandran at comcast.com><mailto:Agalya_Ramachandran at comcast.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: opensips crash when doing load test

Could you also print r_buf and *r_buf  ?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20161005/a3f4eb1a/attachment-0001.htm>