[OpenSIPS-Users] "WARNING:core:timer_ticker: timer task <ul-timer> already schedualed issue." Some hint ?

Fri Mar 18 22:27:35 CET 2016

Hi.

Finally, after 2 weeks analyzing the case, I found the solution. So, I would like to share it here:

modparam("usrloc", "timer_interval", 300)

After configuring this timer interval equals to 300, the issue disappeared.

Does it make sense?

In my case, my system will never has more than 2 simultaneous calls. It is a project requirement. So, i guess this new timer interval will not affect the system.

Any comment will be very helpful!

Thanks a lot.

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 Rodrigo Pimenta Carvalho <pimenta at inatel.br>
Enviado: quinta-feira, 17 de março de 2016 14:25
Para: OpenSIPS users mailling list
Assunto: Re: [OpenSIPS-Users] "WARNING:core:timer_ticker: timer task <ul-timer> already schedualed issue." Some hint ?

Hi.

I was analyzing more details about this issue.

I guess the problem rises when OpenSIPS receives a SIP REGISTER message in some moment. When OpenSIPS receives a SIP REGISTER message, it has to update the location table, according to my opensips.cfg file.

See:

                if (!save("location")){
                        sl_reply_error();
                }
                avp_db_query("UPDATE location SET callerName='$fn' WHERE id = last_insert_rowid()");

So, immediately after saving data in location table, there is a db query to update the same table. Maybe it is occurring some kind of concurrence here. So I asK:

1 - Does "<ul-timer> " means something related to user location?

2 - Is the save function a kind of asynchronous routine?

3 - If it is asynchronous, could it be a good idea to put a 'sleep' between such function and the db query?

Any hint will be very helpful!

Thanks a a lot.

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 Rodrigo Pimenta Carvalho <pimenta at inatel.br>
Enviado: quinta-feira, 17 de março de 2016 09:01
Para: OpenSIPS users mailling list
Assunto: Re: [OpenSIPS-Users] "WARNING:core:timer_ticker: timer task <ul-timer> already schedualed issue." Some hint ?

Hi.

What is the module that has Asyn radius? Do you mean module AAA-Radius?

In my script opensips.cfg I don't have any module for RADIUS. That is why I think my case might be little different from those seen on old discussions.

Have you seen any another function from OpenSIPS 2.2 that could cause such issue? I'm using OpenSIPS 2.2 too.

Best 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 Dragomir Haralambiev <goup2010 at gmail.com>
Enviado: quinta-feira, 17 de março de 2016 03:35
Para: OpenSIPS users mailling list
Assunto: Re: [OpenSIPS-Users] "WARNING:core:timer_ticker: timer task <ul-timer> already schedualed issue." Some hint ?

Hi,

I check my log. I have same messages too.

This is appear when use Asyn radius at Opensips 2.2.

Regards,
Dragomir

2016-03-16 20:03 GMT+02:00 Rodrigo Pimenta Carvalho <pimenta at inatel.br<mailto:pimenta at inatel.br>>:

Hi.

Since some days ago I'm analyzing an issue related to "WARNING:core:timer_ticker: timer task <ul-timer> already scheduled".

Some times my OpenSIPS starts printing 'like in a loop' too many messages about "WARNING:core:timer_ticker: timer task <ul-timer> already schedualed". See below a part of my log. I have read some discussions about it, but the information didn't help me, because my case might be little different from those seen on old discussions.

So, I have some basic questions:

1 - What does mean "WARNING:core:timer_ticker: timer task <ul-timer> already schedualed" in terms of OpenSIPS task scheduler?

2 - What should I try to avoid this issue? Some special configuration on opensips.cfg? Or maybe give up accessing the database sqlite?

3 - If I do nothing about it, after some time receiving such warning, what will be the logic consequence?

Any hint will be very helpful!

Thanks alot.

-------------------------------------------------------------------------------------------------------------------------------------------------

Mar 16 17:36:27 colibri-imx6 opensips[12369]: new branch at sip:6001 at 192.168.100.156:64917;transport=TCP;ob
Mar 16 17:36:27 colibri-imx6 opensips[12369]: new branch at sip:6001 at 177.79.5.103:1880;transport=TCP;rinstance=444fe9d0040e73ce
Mar 16 17:36:27 colibri-imx6 opensips[12369]: new branch at sip:6001 at 177.79.5.103:1880;transport=TCP;rinstance=444fe9d0040e73ce
Mar 16 17:36:31 colibri-imx6 opensips[12369]: Mar 16 17:36:31 [12381] WARNING:rr:after_strict: no socket found to match RR [1][192.168.100.166:5060<http://192.168.100.166:5060>]
Mar 16 17:36:46 colibri-imx6 opensips[12369]: new branch at sip:6002 at 192.168.100.108:34113;transport=TCP;rinstance=b79e897f4f560fa5
Mar 16 17:36:47 colibri-imx6 opensips[12369]: Mar 16 17:36:47 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 2980740 ms), it may overlap..
Mar 16 17:36:48 colibri-imx6 opensips[12369]: incoming reply
Mar 16 17:36:48 colibri-imx6 opensips[12369]: Mar 16 17:36:48 [12381] WARNING:rr:after_strict: no socket found to match RR [1][192.168.100.166:5060<http://192.168.100.166:5060>]
Mar 16 17:37:00 colibri-imx6 opensips[12369]: Mar 16 17:37:00 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 2993620 ms), it may overlap..
Mar 16 17:37:01 colibri-imx6 opensips[12369]: Mar 16 17:37:01 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 2994610 ms), it may overlap..
Mar 16 17:37:02 colibri-imx6 opensips[12369]: Mar 16 17:37:02 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 2995600 ms), it may overlap..
Mar 16 17:37:03 colibri-imx6 opensips[12369]: Mar 16 17:37:03 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 2996590 ms), it may overlap..
Mar 16 17:37:04 colibri-imx6 opensips[12369]: Mar 16 17:37:04 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 2997580 ms), it may overlap..
Mar 16 17:37:05 colibri-imx6 opensips[12369]: Mar 16 17:37:05 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 2998570 ms), it may overlap..
Mar 16 17:37:06 colibri-imx6 opensips[12369]: Mar 16 17:37:06 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 2999560 ms), it may overlap..
Mar 16 17:37:07 colibri-imx6 opensips[12369]: Mar 16 17:37:07 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 3000550 ms), it may overlap..
Mar 16 17:37:08 colibri-imx6 opensips[12369]: Mar 16 17:37:08 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 3001540 ms), it may overlap..
Mar 16 17:37:09 colibri-imx6 opensips[12369]: Mar 16 17:37:09 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 3002530 ms), it may overlap..
Mar 16 17:37:10 colibri-imx6 opensips[12369]: Mar 16 17:37:10 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 3003520 ms), it may overlap..
Mar 16 17:37:11 colibri-imx6 opensips[12369]: Mar 16 17:37:11 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 3004510 ms), it may overlap..
Mar 16 17:37:12 colibri-imx6 opensips[12369]: Mar 16 17:37:12 [12378] WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for 2970850 ms (now 3005500 ms), it may overlap..

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200<tel:%2B55%2035%203471%209200> RAMAL 979

_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto: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/20160318/26f8ff80/attachment-0001.htm>