[SR-Users] crash on using http_query when response is 200

[Daniel-Constantin Mierla]

Hello Olle,

I made a note on your but tracker issue, because the new curl module
doesn't seem to have some fixed done to utils module in august/september
-- those patches look like fixing what you are facing. Have you seen it?

Cheers,
Daniel

On 07/12/15 16:06, Olle E. Johansson wrote:
> Please post this on the issue tracker. I also get crashes, but they’re
> not like this. 
>
> /Olle
>
>> On 07 Dec 2015, at 15:54, Jayesh Nambiar <jayesh1017 at gmail.com
>> <mailto:jayesh1017 at gmail.com>> wrote:
>>
>> Hi,
>> I'm using http_query to send a post request on a https URL. The weird
>> part is it crashes with segmentation fault when the response from the
>> server is 200. If the response was a 500, it works and continues
>> processing.
>> Here's the function:
>> http_query("https://notify.abcd.com/onnet/call", "$avp(devices)",
>> "Content-Type: application/json" "$var(response)");
>> xlog("L_INFO", "Response is $var(response)");
>>
>> And here's the backtrace on crash:
>> 0x00007f62f2bf8e38 in ?? ()
>> #1  0x00007f62ea22251b in http_query (_m=0x7f62f2c3a038,
>> _url=0x7f62f2bf3548 "\330\064\277\362b\177", _dst=0x7f62f2bf9250
>> "\030\215\277\362b\177", _post=0x7f62f2bf35c8 "\200r\277\362b\177", 
>>     _hdr=0x7f62f2bf91d0 "h\221\277\362b\177") at functions.c:226
>> #2  0x00007f62ea229e0b in w_http_query_post_hdr (_m=0x7f62f2c3a038,
>> _url=0x7f62f2bf3548 "\330\064\277\362b\177", _post=0x7f62f2bf35c8
>> "\200r\277\362b\177", _hdr=0x7f62f2bf91d0 "h\221\277\362b\177", 
>>     _result=0x7f62f2bf9250 "\030\215\277\362b\177") at utils.c:483
>> #3  0x000000000041f6b5 in do_action (h=0x7ffeb128c8c0,
>> a=0x7f62f2bf8a58, msg=0x7f62f2c3a038) at action.c:1079
>> #4  0x000000000042c2ea in run_actions (h=0x7ffeb128c8c0,
>> a=0x7f62f2bf6fc0, msg=0x7f62f2c3a038) at action.c:1549
>> #5  0x000000000041f3ce in do_action (h=0x7ffeb128c8c0,
>> a=0x7f62f2bfb9b0, msg=0x7f62f2c3a038) at action.c:1045
>> #6  0x000000000042c2ea in run_actions (h=0x7ffeb128c8c0,
>> a=0x7f62f2bb9388, msg=0x7f62f2c3a038) at action.c:1549
>> #7  0x000000000041bc28 in do_action (h=0x7ffeb128c8c0,
>> a=0x7f62f2b8f248, msg=0x7f62f2c3a038) at action.c:678
>> #8  0x000000000042c2ea in run_actions (h=0x7ffeb128c8c0,
>> a=0x7f62f2b8e268, msg=0x7f62f2c3a038) at action.c:1549
>> #9  0x000000000041f3ce in do_action (h=0x7ffeb128c8c0,
>> a=0x7f62f2b91040, msg=0x7f62f2c3a038) at action.c:1045
>> #10 0x000000000042c2ea in run_actions (h=0x7ffeb128c8c0,
>> a=0x7f62f2b8b7a8, msg=0x7f62f2c3a038) at action.c:1549
>> #11 0x000000000041bc28 in do_action (h=0x7ffeb128c8c0,
>> a=0x7f62f2b3a2c0, msg=0x7f62f2c3a038) at action.c:678
>> #12 0x000000000042c2ea in run_actions (h=0x7ffeb128c8c0,
>> a=0x7f62f2b3a2c0, msg=0x7f62f2c3a038) at action.c:1549
>> #13 0x000000000041f3ce in do_action (h=0x7ffeb128c8c0,
>> a=0x7f62f2b47f00, msg=0x7f62f2c3a038) at action.c:1045
>> #14 0x000000000042c2ea in run_actions (h=0x7ffeb128c8c0,
>> a=0x7f62f2b37e80, msg=0x7f62f2c3a038) at action.c:1549
>> #15 0x000000000041bc28 in do_action (h=0x7ffeb128c8c0,
>> a=0x7f62f2b1c9c8, msg=0x7f62f2c3a038) at action.c:678
>> #16 0x000000000042c2ea in run_actions (h=0x7ffeb128c8c0,
>> a=0x7f62f2b1c9c8, msg=0x7f62f2c3a038) at action.c:1549
>> #17 0x000000000041f3ce in do_action (h=0x7ffeb128c8c0,
>> a=0x7f62f2b1cc28, msg=0x7f62f2c3a038) at action.c:1045
>> #18 0x000000000042c2ea in run_actions (h=0x7ffeb128c8c0,
>> a=0x7f62f2b170a0, msg=0x7f62f2c3a038) at action.c:1549
>> #19 0x000000000042ca93 in run_top_route (a=0x7f62f2b170a0,
>> msg=0x7f62f2c3a038, c=0x0) at action.c:1635
>> #20 0x000000000051c115 in receive_msg (
>>     buf=0xab7520 <buf> "INVITE
>> sip:bdbbf600000001b5b919d0 at devsip.abcd.com:8321
>> <http://sip:bdbbf600000001b5b919d0@devsip.abcd.com:8321/>
>> SIP/2.0\r\nRecord-Route:
>> <sip:203.153.53.145:8300;r2=on;lr=on>\r\nRecord-Route:
>> <sip:203.153.53.145:8321;transport=tcp;r2=on;lr=on>\r\nVia:
>> SIP/2.0/UDP"..., len=1901, rcv_info=0x7ffeb128cc10) at receive.c:196
>> #21 0x000000000062d427 in udp_rcv_loop () at udp_server.c:495
>> #22 0x00000000004b28c1 in main_loop () at main.c:1593
>> #23 0x00000000004b9aa5 in main (argc=5, argv=0x7ffeb128d118) at
>> main.c:2597
>>
>> Can someone please confirm the crash so that I'll go ahead and report
>> this as an issue on the tracker. Basically when it crashes, kamailio
>> doesn't even execute the xlog function after the http_query call.
>> P.S. abcd.com <http://abcd.com/> is a changed domain for confidential
>> reasons.
>>
>> Thanks,
>>
>> - Jayesh
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20151207/6efec983/attachment.html>