Hi Steve.
The values that you have commented is used by the "make menuconfig". That is, as long as these are the values chosen by the standard configuration, I believe that such values wouldn't be causing problems. Best regards. RODRIGO PIMENTA CARVALHO Inatel Competence Center Software Ph: +55 35 3471 9200 RAMAL 979 ________________________________ De: Steve Woolley <[email protected]> Enviado: quarta-feira, 8 de junho de 2016 09:12 Para: OpenSIPS users mailling list Cc: Bogdan-Andrei Iancu; Rodrigo Pimenta Carvalho Assunto: Re: [OpenSIPS-Users] Continuous "WARNING:core:timer_ticker: timer task <tm-timer> already scheduled" messages in log So i made two changes to my config: 1. per Bogdan, changed my timer_partitions to: modparam("tm", "timer_partitions", 4) 2. I had previously used some settings found in a number of configuration examples in my transaction module. After a little research, I commented them out. Still doing some research into whether these new (default) values may trigger other problems. My new config is as so (snippet): #### Transaction Module loadmodule "tm.so" # modparam("tm", "fr_timeout", 5) # modparam("tm", "fr_inv_timeout", 30) # modparam("tm", "restart_fr_on_each_reply", 0) # modparam("tm", "onreply_avp_mode", 1) modparam("tm", "timer_partitions", 4) Since making these changes and restarting, the messages have gone away. On Jun 7, 2016, at 6:47 AM, Bogdan-Andrei Iancu <[email protected]<mailto:[email protected]>> wrote: Hello Steve, What OpenSIPS tells you is that you the TM timer routine (which gets executed once per second) takes longer than 1 second (as execution). Probably you have retransmissions or many failure routes to be executed. You can increase the level of parallelism in TM timer via the timer_partition parameter: http://www.opensips.org/html/docs/modules/2.2.x/tm.html#id294483 Try to set it to 4. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com<http://www.opensips-solutions.com/> On 07.06.2016 04:21, Steve Woolley wrote: 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]<mailto:[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
