[OpenSIPS-Users] SRV lookup causes OpenSIPS to exit signal 11

[Jeff Pyle]

Bogdan,

Never done a backtrace before.  I'm following what documentation I was
able to find and it's not working so well...  Would you be able to point
me in the right direction?

Thanks,
Jeff
 

-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:bogdan at voice-system.ro]
Sent: Wednesday, October 15, 2008 6:10 AM
To: Jeff Pyle
Cc: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] SRV lookup causes OpenSIPS to exit signal
11

Hi Jeff,

do you have a backtrace or something? maybe the guilty code the new SRV
balancer that was introduced in 1.4.0 ....and it is alpha code.

Regards,
Bogdan

Jeff Pyle wrote:
> Hello,
>  
> I'm running OpenSIPS from the opensips_1_4 trunk on SVN (downloaded 
> last week).  It seems that about 50% of the time an SRV lookup causes 
> OpenSIPS to exit signal 11:
>  
> DBG:core:sip_resolvehost: no valid NAPTR record found for 
> ns.onvoip.net, trying direct SRV lookup...
> INFO:core:handle_sigs: child process 19363 exited by a signal 11 When 
> it does not fail, this section of the log looks like:
>  
> DBG:core:sip_resolvehost: no valid NAPTR record found for 
> ns.onvoip.net, trying direct SRV lookup...
> DBG:core:do_srv_lookup: SRV(_sip._udp.ns.onvoip.net) = 
> ns3.onvoip.net:5060
> DBG:core:a2dns_node: storing ns4.onvoip.net:5060
> DBG:core:a2dns_node: storing ns1.onvoip.net:5060
> DBG:core:a2dns_node: storing ns2.onvoip.net:5060 Everything prior to 
> this in the logs is identical between the successful and failed 
> transactions.  Even at debug = 9.
>  
> The location table has the following information on the user:
>  
>            id: 6
>       groupid: 0
>      username: 3032391067
>        domain:
>       contact: sip:3032391067 at ns.onvoip.net
>      received: NULL
>          path: NULL
>       expires: 2020-05-28 21:32:15
>             q: 1.00
>        callid: Default-Call-ID
>          cseq: 13
> last_modified: 2008-04-22 16:25:11
>         flags: 0
>        cflags: 0
>    user_agent:
>        socket: NULL
>       methods: NULL
> I manually inserted this into the database.  It did not come from a 
> registration.
>  
> The route logic is quite simple.  I have:
>  
>         if (!lookup("location")) {
>                 # Stuff that doesn't matter because the lookup was 
> successful in this case
>         }
>         t_on_reply("1");
>         t_on_failure("1");
>         if (!isflagset(26)) {
>                 $(avp(s:acc_callee_user)) = $rU;
>                 avp_printf("$(avp(i:901))",
"$(avp(s:acc_caller_user))");
>                 avp_printf("$(avp(i:902))",
"$(avp(s:acc_callee_user))");
>         }
>  
>         if(is_present_hf("Proxy-Authorization")) { 
> remove_hf("Proxy-Authorization"); }
>  
>         xlog("L_INFO", "-- About to relay...\n");
>         if(!t_relay("0x01")) {
>                 sl_reply_error();
>         }
>         exit;
> Very similar code works okay on OpenSER 1.3.2.  On OpenSIPS 1.4.x it 
> does not seem stable.  I don't know how to determine what's causing it

> to exit.  Any thoughts?
>  
> Thanks,
> Jeff