Hi Hamid,

There is no such option in OpenSIPS 2.1 as the timer system has a completly different architecture.

Are you running with a single process ?

If you get those errors means your OpenSIPS has no single process able to do any kind of processing.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 23.09.2015 10:38, Hamid Hashmi wrote:
Hello

I am upgrading opensips from v1.9 to v2.1.1. What is the alternate of own_timer_proc in latest version v2.1.1. I am having following wearings continuously after starting the service.

.
.
INFO:acc:mod_init: initializing...
WARNING:acc:mod_init: Integer flags are now deprecated! Use unique quoted strings!
INFO:core:evi_publish_event: Registered event <E_ACC_EVENT(11)>
INFO:core:evi_publish_event: Registered event <E_ACC_CDR(12)>
INFO:core:evi_publish_event: Registered event <E_ACC_MISSED_EVENT(13)>
INFO:auth_aaa:mod_init: initializing...
INFO:exec:mod_init: exec - initializing
INFO:load_balancer:mod_init: Load-Balancer module - initializing
WARNING:load_balancer:lb_db_load_data: table "load_balancer" empty
INFO:core:evi_publish_event: Registered event <E_LOAD_BALANCER_STATUS(14)>
INFO:uac:mod_init: initializing...
WARNING:rtpproxy:fixup_deprecated_warn: function unforce_rtp_proxy() is now deprecated - use rtpproxy_unforce() instead
INFO:core:probe_max_sock_buff: using rcv buffer of 244 kb
WARNING:core:utimer_ticker: utimer task *<tm-utimer>* already schedualed for 190 ms (now 290 ms), it may overlap.. WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for 290 ms (now 390 ms), it may overlap.. WARNING:core:timer_ticker: timer task *<tm-timer>* already schedualed for 980 ms (now 1970 ms), it may overlap.. WARNING:core:timer_ticker: timer task *<blcore-expire>* already schedualed for 980 ms (now 1970 ms), it may overlap.. WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for 2860 ms (now 2960 ms), it may overlap.. WARNING:core:timer_ticker: timer task <exec_kill> already schedualed for 980 ms (now 2960 ms), it may overlap.. WARNING:core:timer_ticker: timer task *<nt-pinger>* already schedualed for 980 ms (now 2960 ms), it may overlap.. WARNING:core:timer_ticker: timer task *<nh-timer>* already schedualed for 980 ms (now 2960 ms), it may overlap.. WARNING:core:timer_ticker: timer task *<dlg-timer>* already schedualed for 980 ms (now 2960 ms), it may overlap.. WARNING:core:timer_ticker: timer task <tm-timer> already schedualed for 980 ms (now 2960 ms), it may overlap.. WARNING:core:timer_ticker: timer task <blcore-expire> already schedualed for 980 ms (now 2960 ms), it may overlap..

.
.
.

Regards
Hamid R. Hashmi


_______________________________________________
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

Reply via email to