Hi Steve.
I had exactly this same problem!
I used to see that log very frequently.
So, I changed a configuration in my opensips.cfg file to be:
modparam("usrloc", "db_mode", 2)
modparam("usrloc", "timer_interval",3)
Then, the problem almost disappeared. That is, nowadays I see this log seldom.
Tell me about the solution for your case, when you have fixed it, please!
I also gonna to consider the last hint from Bogdan and change my TM parameter.
Best regards!
RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
________________________________
De: [email protected] <[email protected]> em nome
de Steve Woolley <[email protected]>
Enviado: segunda-feira, 6 de junho de 2016 22:21
Para: [email protected]
Assunto: [OpenSIPS-Users] Continuous "WARNING:core:timer_ticker: timer task
<tm-timer> already scheduled" messages in log
Running opensips on a Raspberry Pi. At some point after starting opensips
(sometimes immediately, sometimes after quite a bit of time), the following
message fills the log - once a second - continuously.
...
Jun 7 01:10:41 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8258580 ms), it may
overlap..
Jun 7 01:10:42 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8259570 ms), it may
overlap..
Jun 7 01:10:43 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8260560 ms), it may
overlap..
Jun 7 01:10:44 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8261560 ms), it may
overlap..
Jun 7 01:10:45 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8262550 ms), it may
overlap..
Jun 7 01:10:46 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8263550 ms), it may
overlap..
Jun 7 01:10:47 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8264540 ms), it may
overlap..
Jun 7 01:10:48 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8265530 ms), it may
overlap..
Jun 7 01:10:49 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8266530 ms), it may
overlap..
Jun 7 01:10:50 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker:
timer task <tm-timer> already scheduled for 7182080 ms (now 8267520 ms), it may
overlap..
root@pi1:~# opensips -V
version: opensips 2.2.0 (arm6/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, QM_MALLOC,
DBG_MALLOC, USE_PTHREAD_MUTEX
MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
git revision: 0e1cea7
main.c compiled on 21:56:59 Jun 3 2016 with gcc 4.9.2
Anyone experiencing the same?
--
Steve Woolley
[email protected]<mailto:[email protected]>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
