[OpenSIPS-Users] Opensips 2.1 custom radius accounting error

[Arsen]

Hi Lonut-Razvan,

Thank you! :)

On Thursday, 24 September 2015, Ionut Ionita <ionutionita at opensips.org>
wrote:

> Hi Arsen,
>
>     If i completely understand the problem, the server doesn't provide the
> deserved response. The problem in this case is that rc_send_server function
> which is used by rc_acct function (which gives you the error) uses a
> blocking socket and recvfrom blocks until it receives the RADIUS message
> response. You can see the source code here [0] line 224. Blocking causes
> problems in scheduling other timers in opensips, in your case tm and dialog
> timers, and that is the cause for your warnings. So it is a drawback of the
> freeradius-client(or radiusclient-ng) implementation. We tried to solve
> this problem in opensips 2.2 with radius async features[1].
>
> Regards,
> Ionut-Razvan Ionita
>
> [0]
> https://github.com/FreeRADIUS/freeradius-client/blob/master/lib/sendserver.c
> [1]
> http://www.opensips.org/html/docs/modules/2.2.x/aaa_radius.html#id294274
>
> On 24.09.2015 14:12, Arsen wrote:
>
>> Hello,
>>
>> I constantly get following Warnings and opensips seems fails to work once
>> I try to send a custom accounting request to a remote Radius server.
>>
>> Sep 24 10:46:24 ip-172-31-22-93 /usr/sbin/opensips[14435]: LOG:
>> WITHINDLG: [BYE FROM: sip:256779346904 at 31.22.1.133:5060 <
>> http://sip:256779346904@31.22.1.133:5060> TO:
>> sip:447451904526 at 31.22.1.133:5060 <
>> http://sip:447451904526@31.22.1.133:5060>]
>> Sep 24 10:46:25 ip-172-31-22-93 /usr/sbin/opensips[14432]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 89610 ms (now 89710 ms), it may overlap..
>> Sep 24 10:46:25 ip-172-31-22-93 /usr/sbin/opensips[14432]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 89710 ms (now 89810 ms), it may overlap..
>> Sep 24 10:46:25 ip-172-31-22-93 /usr/sbin/opensips[14432]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 89810 ms (now 89910 ms), it may overlap..
>> Sep 24 10:46:25 ip-172-31-22-93 /usr/sbin/opensips[14432]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 89910 ms (now 90010 ms), it may overlap..
>> Sep 24 10:46:25 ip-172-31-22-93 /usr/sbin/opensips[14432]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 90010 ms (now 90110 ms), it may overlap..
>> Sep 24 10:46:25 ip-172-31-22-93 /usr/sbin/opensips[14432]:
>> WARNING:core:timer_ticker: timer task <dlg-pinger> already schedualed for
>> 30680 ms (now 90110 ms), it may overlap..
>>
>> I can confirm that the radius packages have been send to the server and I
>> see them on the radius server, but no reply:
>>
>> Sep 24 10:46:27 ip-172-31-22-93 /usr/sbin/opensips[14436]:
>> rc_send_server: no reply from RADIUS server remote_radius.com:1813 <
>> http://remote_radius.com:1813>
>> Sep 24 10:46:27 ip-172-31-22-93 /usr/sbin/opensips[14436]:
>> ERROR:aaa_radius:send_acct_func: radius accounting message failed to send
>>
>> It works with a local freeradius server but not with a remote one..
>>
>> Any advices?
>>
>> --
>> Regards,
>> Arsen.
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://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
>


-- 
Regards,
Arsen.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150925/e953ee78/attachment.htm>