[OpenSIPS-Users] Alternate of own_timer_proc in v2.1.1
Hamid Hashmi
hamid2kviii at hotmail.com
Wed Sep 23 10:14:13 CEST 2015
Hi Bogdan
Sorry, I couldn't understand the reason ?
[root at aws-dev-ec2-sipserver ~]# ps -ef | grep opensipsroot 20735 1 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20742 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20743 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20744 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20745 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20746 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20747 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20748 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20749 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20750 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20751 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20752 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20753 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20754 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20755 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20756 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20757 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20758 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20759 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20760 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20761 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20762 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20763 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20764 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20765 20735 0 08:02 ? 00:00:00 /usr/local/sbin/opensips -P /var/run/opensips.pidroot 20768 19398 0 08:03 pts/1 00:00:00 grep opensips
RegardsHamid R. Hashmi
Date: Wed, 23 Sep 2015 10:43:49 +0300
From: bogdan at opensips.org
To: users at lists.opensips.org; hamid2kviii at hotmail.com
Subject: Re: [OpenSIPS-Users] Alternate of own_timer_proc in v2.1.1
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
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/20150923/3a14f1b9/attachment-0001.htm>
More information about the Users
mailing list