[OpenSIPS-Users] opensips 2.3

[Tito Cumpen]

Hey Razvan,


I believe I found out what was causing the acc logic crash this failure
route block:


failure_route[missed_call] {
rtpengine_delete("delete-delay=0");
                        xlog("this failure missed call failure to $ci on
missed call failure block for reason $err.rreason \n");
drop_accounting();  I had to comment this drop accounting function to stop
the crashing



        if (t_was_cancelled()) {
xlog("looks like $ci was cancelled?\n");
                exit;
        }



if (next_branches()) {
drop_accounting("evi", "missed");
xlog("found branches with lower priority attempting to relay(\n");
            route(relay);
            exit;
}

             # if (t_check_status("408|486|603|404|477") &&
(!isflagset(friend))) {
              if (!isflagset(friend)) {


xlog("forwarding call on on failure timeout or 603 \n");


xlog("this request does not source from a sister proxy and it must handled
here");
xlog("we are attempting to route it to the AS server for failover");

if (isbflagset(DST_WS)){
    revert_uri();
resetbflag(DST_WS);
}
drop_accounting("evi", "missed");
resetflag(accounted);
force_send_socket(udp:MY_IP:5060);

route(logic);
        }else{
                                xlog("sending a failure to friend\n");
                                t_reply("404","User not found");


}


}


I think the fact that I was dropping accounting() once and then again like
this  drop_accounting("evi", "missed") was causing the issue. The problem
is I still get acc reports on failure although I'd like to drop until it
fails at the "logic route".

Thanks,
Tito


On Thu, Jan 11, 2018 at 7:20 AM, Răzvan Crainea <razvan at opensips.org> wrote:

> Hi, Tito!
>
> That works, it's enough to understand the the issue is very complicated :).
> Can you provide (offsite) the binaries and the core file, so I can inspect
> them? Or if it is easier for you, provide access to the machine that
> crashes, if it is a testing environment.
> Also, how often is this happening? I see you got 3 cores in two days - is
> it production traffic? or testing traffic?
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Developerwww.opensips-solutions.com
>
> On 01/11/2018 11:38 AM, Tito Cumpen wrote:
>
> How's this?
>
>
> https://pastebin.com/srr8MHLK
>
> On Thu, Jan 11, 2018 at 1:03 AM, Răzvan Crainea <razvan at opensips.org>
> wrote:
>
>> Hi, Tito!
>>
>> You're right, it was my mistake regarding the revision, I wasn't looking
>> on the right branch.
>> Can you also post the the CRITICAL/ERROR logs from the second core[2]?
>>
>> [2] https://pastebin.com/2Eq8JZ1A
>>
>> Best regards,
>>
>> Răzvan Crainea
>> OpenSIPS Developer
>> www.opensips-solutions.com
>>
>> On 01/11/2018 10:56 AM, Tito Cumpen wrote:
>>
>>> I'm not sure what to look for to match the previous issue so I pasted a
>>> couple of crashes from the last two days
>>>
>>> https://pastebin.com/aAFsgXEm
>>> https://pastebin.com/2Eq8JZ1A
>>> https://pastebin.com/reDexmqY
>>>
>>> Let me know if this helps.
>>>
>>> Thanks,
>>> Tito
>>>
>>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180122/a36eeac0/attachment.html>