[OpenSIPS-Users] Opensips crash!!!!!!

[Arsen]

Hey Dragomir,

Do you use radius in your setup?
I had exactly same issue when i was trying to send radius acct request.

You can check this issue here in the list "opensips 2.1 custom radius
accounting error"

Regards,
Arsen

On Tuesday, 3 November 2015, Dragomir Haralambiev <goup2010 at gmail.com>
wrote:

> Hello all,
>
> I am upgrading opensips from v1.11 to v2.1.1.
>
> I am having following wearings continuously after first call:
>
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
> <tm-utimer> already schedualed for 1548180 ms (now 1548280 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
> <tm-utimer> already schedualed for 1548280 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
> <nh-timer> already schedualed for 1545910 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
> <dlg-timer> already schedualed for 1545910 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
> <tm-timer> already schedualed for 1545910 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
> <blcore-expire> already schedualed for 1545910 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
> <tm-utimer> already schedualed for 1548380 ms (now 1548480 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
> <tm-utimer> already schedualed for 1548480 ms (now 1548580 ms), it may
> overlap..
>
>
> Where is problem?
>
> Regards,
> PlayMen
>


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