Many things share the same timer, dialog expiration cleanup,
userlocation cleanup, nathelper pings etc. If one of the processes that
is triggered by a timer route blocks for some period of time - aka a
hung db query, it will cause the timer to "drift" and you will get logs
indicating that a process that should have takeng X amount of time
actually took Y amount of time - this is due to the blocking operation.
I would suggest that you use dedicated timer processes for as many
things as you can - dialog, tm etc. see the module docs for how to do this.
-Eric
On 02/22/2016 10:28 AM, Rodrigo Pimenta Carvalho wrote:
Hi.
The log of my OpenSIPS began to present thousands of warnings similar to:
"WARNING:core:timer_ticker: timer task <nh-timer> already schedualed
for 93991120 ms (now 248157560 ms), it may ove rlap.."
What does exactly means it?
Some discussions from the past said something about increasing the
number in the global variable "children".
Should I change the number for children? Before trying it i would
like to hear something about, just to know better what I'm going to do.
Any hint will be very helpful!
Thanks a lot.
RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
