[OpenSIPS-Users] WARNING:core:timer_ticker: timer task <uac_reg_check> already schedualed

[Rodrigo Pimenta Carvalho]

Hi Yarkob.


I'm getting almost the same problem here.

So, I have discussed about it in this list since 2 days ago.


I didn't find the solution, but you can see those discussion from me.

In my case, I have some SQL queries that executes in my opensips.cfg file. I will try to investigate if such queries are blocking next processes for OpenSIPS. Let's see....


Regards.


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979


________________________________
De: users-bounces at lists.opensips.org <users-bounces at lists.opensips.org> em nome de ?????? ????? <achalkov at ya.ru>
Enviado: terça-feira, 23 de fevereiro de 2016 21:50
Para: users &gt;&gt; OpenSIPS users mailling list
Assunto: [OpenSIPS-Users] WARNING:core:timer_ticker: timer task <uac_reg_check> already schedualed

Hi all!

My opensips version:
opensips 2.1.2 (x86_64/linux)
git revision: 44cc594

I use opensips with uac_registrant module and sometimes in log appears these warnings (2-3 warnings every hour):

Feb 17 21:34:56 opensips-uac /usr/sbin/opensips[12971]: WARNING:core:timer_ticker: timer task <uac_reg_check> already schedualed for 62923880 ms (now 62924880 ms), itmay overlap..

Timer offset leads me to approx. (with some little offset like 1-10 minutes) time, when my opensips restarting every day (via service opensips restart).

In particular rare cases (1-2 times in month or rarely) it leads to flood with below warnings:

Feb 17 21:59:36 opensips-uac /usr/sbin/opensips[12971]: WARNING:core:timer_ticker: timer task <tm-timer> already schedualed for 64393870 ms (now 64395870 ms), it may o
verlap..
Feb 17 21:59:36 opensips-uac /usr/sbin/opensips[12971]: WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for 64395870 ms (now 64395970 ms), it ma
y overlap..
Feb 17 21:59:36 opensips-uac /usr/sbin/opensips[12971]: WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for 64395970 ms (now 64396060 ms), it ma
y overlap..

But every time it happens, warnings with uac_reg_check appears first in large quantities. While it happens, opensips starts to ignore most incoming traffic. In log with debug=4 i doesn't see any unusual entrys before it starts. After some time (2-3 hours) flood stops and problem disappears itself without any workaround on my side.

I know about similar issue with radius (http://comments.gmane.org/gmane.comp.voip.opensips.user/31415), but i'm not using radius in my configuration, so can it be some new issue or it is a same issue and it would be resolved, as planned, in v.2.2?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160224/c9fa7ca8/attachment.htm>