subject:"\[OpenSIPS\-Users\] OpenSIPs 2.2.2 warnings during start service"

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-05-29 Thread suresh.talasaniya

Hello Johan,

If you have a testing patch, kindly provide me.

https://opensips.org/pipermail/users/2016-August/035400.html




Thank you.



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPs-2-2-2-warnings-during-start-service-tp7607495p7607536.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-05-22 Thread Johan De Clercq

Check radius.

On 22 May 2017 17:07, "suresh.talasaniya" 
wrote:

> Hi,
>
> I'm currently seeing the warnings when I start opensips service;
>
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
> WARNING:core:handle_timer_job: timer job  has a 150 us
> delay in execution
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
> WARNING:core:handle_timer_job: timer job  has a 150 us delay
> in execution
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
> WARNING:core:handle_timer_job: timer job  has a 150 us delay
> in execution
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
> WARNING:core:handle_timer_job: utimer job  has a 229 us
> delay in execution
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
> INFO:core:do_action: max while loops are encountered
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]:
> WARNING:core:utimer_ticker: utimer task  already scheduled for
> 190 ms (now 2470 ms), it may over
>
> I check my server load but it seems normal. I am facing this issue when I
> hit 50 cps and 500 CC.
>
> Can you please assist me how to resolve it ?
>
>
>
> --
> View this message in context: http://opensips-open-sip-
> server.1449251.n2.nabble.com/OpenSIPs-2-2-2-warnings-during-start-service-
> tp7607495.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-05-22 Thread suresh.talasaniya

Hi,

I'm currently seeing the warnings when I start opensips service;

Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a 150 us
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a 150 us delay
in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a 150 us delay
in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: utimer job  has a 229 us
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
INFO:core:do_action: max while loops are encountered
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]:
WARNING:core:utimer_ticker: utimer task  already scheduled for
190 ms (now 2470 ms), it may over

I check my server load but it seems normal. I am facing this issue when I
hit 50 cps and 500 CC.

Can you please assist me how to resolve it ?



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPs-2-2-2-warnings-during-start-service-tp7607495.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-25 Thread Bogdan-Andrei Iancu

Hi,

That explains - during the execution of the startup route the rest of 
worker-like processes are not yet created (we wait to have the startup 
route finished), while the timer is already fires. So it triggers some 
timer jobs but there is no proc available to handle them.

This is a corner case, still I'm thinking of a solution on how to go 
around it. Still, at the end, there is nothing wrong (the timer jobs 
will still be handled, but later, after startup route is done), but you 
get those warnings.

Regards,

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

On 01/24/2017 11:28 PM, Ahmed Munir wrote:
Yes, this works not to do DB op during route startup script and 
eliminate the warnings.

I would like to know, what method will you recommend for route startup 
DB op in opensips 2.2?

On Tue, Jan 24, 2017 at 9:12 AM, Bogdan-Andrei Iancu 
> wrote:

The versions before 2.1 had a completely different approach on hoe
the timer jobs were handled - different code, so no such warnings.
The 2.1 introduces the a more flexible and scalable processing for
the timer jobs.

Could you confirm that removing the DB op from the startup route
eliminates the warnings ?

Thanks,

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

On 01/24/2017 03:49 PM, Ahmed Munir wrote:

Yes, using startup route in my routing script and running DB
query. This kind of warning I didn't face using 1.6 and 1.8
opensips versions but 2.2.2.
Will you recommend async statement for my current routing (see
below) for the startup? startup_route { $var(res) = 1;
$avp(tmp) = "1";# $var(x) = 0; while($var(res) > 0) {

$var(res) = avp_db_query("SELECT Distinct One800, dnis
FROM DNIS_Mapping where One800 > $avp(tmp) order by One800;",
"$avp(One800), $avp(dnis)"); if($var(res) >= 0) {
$var(i) = 0;
while($(avp(One800)[$var(i)]) != "NULL") {

cache_store("local",
"DNIS_$(avp(dnis)[$var(i)])", "$(avp(One800)[$var(i)])");
$avp(tmp) = $(avp(One800)[$var(i)]);
 #   $var(x) = $var(x) + 1;
$(avp(One800)[$var(i)]) = "NULL";
$var(i) = $var(i) + 1;
#   xlog("$var(x) : $(avp(s:dnis)[$var(i)])");

} } } }
On Tue, Jan 24, 2017 at 6:38 AM, Bogdan-Andrei Iancu
> wrote:

Hi Ahmed, So, the warnings pop up ONLY during startup
sequence.  Do you use startup route or any module performing
mem caching of some DB table (drouting, permission, etc) ?
Usually, the first UDP child is doing some heavy lifting
during startup.Regards,

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

On 01/19/2017 06:01 PM, Ahmed Munir wrote:

Hi Razvan,
During starting up the opensips service, I see the first
opensips child process (pid"11172) consumes CPU process to
70-80% and later drop downs to 0.3 - 0.0 % CPU per core. See
below; [root@qorblpsisprxyd1 ~]# top -c -u opensips top -
10:49:54 up 76 days, 23:31,  5 users,  load average: 0.00,
0.00, 0.00 Tasks: 229 total,   1 running, 228 sleeping,   0
stopped,   0 zombie Cpu(s):  0.0%us,  0.1%sy,  0.0%ni,
99.9%id,  0.0%wa,  0.0%hi, 0.0%si,  0.0%st Mem:  65964364k
total,  2568124k used, 63396240k free,   180220k buffers
Swap:  1023996k total,0k used,  1023996k free, 
1226104k cached   PID USER  PR  NI  VIRT  RES  SHR S

%CPU %MEMTIME+ COMMAND 11177 opensips  20   0  165m 5696
4528 S  0.3  0.0   0:00.23 /usr/sbin/opensips -P
/var/run/opensips.pid -m 64 -u opensips -g opensips 11187
opensips  20   0  165m 5628 4460 S  0.3  0.0   0:00.41
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u
opensips -g opensips 11166 opensips  20   0  165m 6892 5752
S  0.0  0.0   0:00.23 /usr/sbin/opensips -P
/var/run/opensips.pid -m 64 -u opensips -g opensips 11168
opensips  20   0  165m 1980  840 S  0.0  0.0   0:00.00
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u
opensips -g opensips 11169 opensips  20   0  165m 1464  328
S  0.0  0.0   0:00.53 /usr/sbin/opensips -P
/var/run/opensips.pid -m 64 -u opensips -g opensips 11171
opensips  20   0  165m 1640  504 S  0.0  0.0   0:00.15
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u
opensips -g opensips 11172 opensips  20   0  166m  40m  38m

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-24 Thread Bogdan-Andrei Iancu


Hi Agalya,

1)do you get warning only for the tm-utimer job ? or do you see other too ?

2) do you have some load on the server (in terms of traffic) ? or is it 
idle/almost-idle ?


3) the "ps" and the logs are not from the same run (the pid's do not 
match) - can you get thedata from same run please ?


Best regards,

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

On 01/24/2017 06:00 PM, Ramachandran, Agalya (Contractor) wrote:


Hi Bogdan,

Please find the result of “opensipsctl fifo ps” and the warnings am 
seeing in logs.


Process:: ID=0 PID=3497 Type=attendant

Process:: ID=1 PID=3498 Type=MI FIFO

Process:: ID=2 PID=3499 Type=time_keeper

Process:: ID=3 PID=3500 Type=timer

Process:: ID=4 PID=3501 Type=SIP receiver udp:10.0.0.1:5060

Process:: ID=5 PID=3502 Type=SIP receiver udp:10.0.0.1:5060

Process:: ID=6 PID=3503 Type=SIP receiver udp:10.0.0.1:5060

Process:: ID=7 PID=3504 Type=SIP receiver udp:10.0.0.1:5060

Process:: ID=8 PID=3505 Type=SIP receiver udp:10.0.0.1:5060

Process:: ID=9 PID=3506 Type=SIP receiver udp:10.0.0.1:5060

Process:: ID=10 PID=3507 Type=SIP receiver udp:10.0.0.1:5060

Process:: ID=11 PID=3508 Type=SIP receiver udp:10.0.0.1:5060

Process:: ID=12 PID=3509 Type=Timer handler

Warnings:

Jan 24 15:03:00 /usr/local/sbin/opensips[27867]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us 
delay in execution


Jan 24 15:04:15 /usr/local/sbin/opensips[27866]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us 
delay in execution


Jan 24 15:10:02 /usr/local/sbin/opensips[27866]: 
WARNING:core:handle_timer_job: utimer job  has a 8 us 
delay in execution


Jan 24 15:19:35 /usr/local/sbin/opensips[27866]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us 
delay in execution


Jan 24 15:23:42 /usr/local/sbin/opensips[27866]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us 
delay in execution


Jan 24 15:25:55 /usr/local/sbin/opensips[27872]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us 
delay in execution


Jan 24 15:42:04 /usr/local/sbin/opensips[27860]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us 
delay in execution


Regards,
Agalya

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Tuesday, January 24, 2017 6:34 AM
*To:* OpenSIPS users mailling list <users@lists.opensips.org>; 
Ramachandran, Agalya (Contractor) <agalya_ramachand...@comcast.com>
*Subject:* Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start 
service


Hi Agalya,

Please provide the output of "opensipsctl fifo ps"

Best regards.


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

On 01/19/2017 04:55 PM, Ramachandran, Agalya (Contractor) wrote:

Hi Razvan,

I didn’t see any process that is using more than 80% of a core.
OpenSIPS is simply being idle and these warnings come periodically.

Like once in couple of hours. I didn’t track the exact time line,
how frequent am getting this warnings.

Ahmed,

Do you notice these warnings only when you start OpenSIPS or could
see it in regular intervals?

Regards,
Agalya

*From:*Users [mailto:users-boun...@lists.opensips.org] *On Behalf
Of *Razvan Crainea
*Sent:* Thursday, January 19, 2017 3:33 AM
*To:* users@lists.opensips.org <mailto:users@lists.opensips.org>
*Subject:* Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during
start service

When starting opensips, is there any opensips process that is
using more than 80% of a core? If so, can you pinpoint the PID in
the opensipsctl ps command?

Best regards,


Răzvan Crainea

OpenSIPS Solutions

www.opensips-solutions.com <http://www.opensips-solutions.com>

On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote:

Same with my case too.

Regards,
Agalya

*From:*Users [mailto:users-boun...@lists.opensips.org] *On
Behalf Of *Ahmed Munir
*Sent:* Wednesday, January 18, 2017 1:31 PM
*To:* OpenSIPs Users <users@lists.opensips.org>
<mailto:users@lists.opensips.org>
    *Subject:* [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during
start service

Hi,

I'm currently seeing the warnings when I start opensips service;

Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a
150 us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a
150 us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a
150 us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: utimer job  has a
229 us de

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-24 Thread Ramachandran, Agalya (Contractor)

Hi Bogdan,

Please find the result of “opensipsctl fifo ps” and the warnings am seeing in 
logs.

Process::  ID=0 PID=3497 Type=attendant
Process::  ID=1 PID=3498 Type=MI FIFO
Process::  ID=2 PID=3499 Type=time_keeper
Process::  ID=3 PID=3500 Type=timer
Process::  ID=4 PID=3501 Type=SIP receiver udp:10.0.0.1:5060
Process::  ID=5 PID=3502 Type=SIP receiver udp:10.0.0.1:5060
Process::  ID=6 PID=3503 Type=SIP receiver udp:10.0.0.1:5060
Process::  ID=7 PID=3504 Type=SIP receiver udp:10.0.0.1:5060
Process::  ID=8 PID=3505 Type=SIP receiver udp:10.0.0.1:5060
Process::  ID=9 PID=3506 Type=SIP receiver udp:10.0.0.1:5060
Process::  ID=10 PID=3507 Type=SIP receiver udp:10.0.0.1:5060
Process::  ID=11 PID=3508 Type=SIP receiver udp:10.0.0.1:5060
Process::  ID=12 PID=3509 Type=Timer handler


Warnings:
Jan 24 15:03:00 /usr/local/sbin/opensips[27867]: WARNING:core:handle_timer_job: 
utimer job  has a 2 us delay in execution
Jan 24 15:04:15 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: 
utimer job  has a 2 us delay in execution
Jan 24 15:10:02 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: 
utimer job  has a 8 us delay in execution
Jan 24 15:19:35 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: 
utimer job  has a 2 us delay in execution
Jan 24 15:23:42 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: 
utimer job  has a 2 us delay in execution
Jan 24 15:25:55 /usr/local/sbin/opensips[27872]: WARNING:core:handle_timer_job: 
utimer job  has a 2 us delay in execution
Jan 24 15:42:04 /usr/local/sbin/opensips[27860]: WARNING:core:handle_timer_job: 
utimer job  has a 2 us delay in execution

Regards,
Agalya
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Tuesday, January 24, 2017 6:34 AM
To: OpenSIPS users mailling list <users@lists.opensips.org>; Ramachandran, 
Agalya (Contractor) <agalya_ramachand...@comcast.com>
Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Hi Agalya,

Please provide the output of "opensipsctl fifo ps"

Best regards.



Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 01/19/2017 04:55 PM, Ramachandran, Agalya (Contractor) wrote:
Hi Razvan,

I didn’t see any process that is using more than 80% of a core. OpenSIPS is 
simply being idle and these warnings come periodically.

Like once in couple of hours. I didn’t track the exact time line, how frequent 
am getting this warnings.

Ahmed,
Do you notice these warnings only when you start OpenSIPS or could see it in 
regular intervals?

Regards,
Agalya

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Razvan 
Crainea
Sent: Thursday, January 19, 2017 3:33 AM
To: users@lists.opensips.org<mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

When starting opensips, is there any opensips process that is using more than 
80% of a core? If so, can you pinpoint the PID in the opensipsctl ps command?

Best regards,



Răzvan Crainea

OpenSIPS Solutions

www.opensips-solutions.com<http://www.opensips-solutions.com>
On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote:
Same with my case too.

Regards,
Agalya

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Ahmed Munir
Sent: Wednesday, January 18, 2017 1:31 PM
To: OpenSIPs Users <users@lists.opensips.org><mailto:users@lists.opensips.org>
Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Hi,
I'm currently seeing the warnings when I start opensips service;

Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us delay 
in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us delay in 
execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us delay in 
execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: utimer job  has a 229 us delay in 
execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: INFO:core:do_action: 
max while loops are encountered
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: 
WARNING:core:utimer_ticker: utimer task  already scheduled for 190 
ms (now 2470 ms), it may over
lap..



I've tried to update the source code for timer.c (line#: 190) ref: 
https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split,
 but didn't work at all.
Currently running 8 child processors, see below;

[root@qorblpsisprxyd1 ]# opensips  -V
version: opensips 2.2.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, 
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
MAX_URI_SIZE 1024, BUF_SIZE 65535

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-24 Thread Bogdan-Andrei Iancu

The versions before 2.1 had a completely different approach on hoe the 
timer jobs were handled - different code, so no such warnings. The 2.1 
introduces the a more flexible and scalable processing for the timer jobs.


Could you confirm that removing the DB op from the startup route 
eliminates the warnings ?


Thanks,

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

On 01/24/2017 03:49 PM, Ahmed Munir wrote:
Yes, using startup route in my routing script and running DB query. 
This kind of warning I didn't face using 1.6 and 1.8 opensips versions 
but 2.2.2.


Will you recommend async statement for my current routing (see below) 
for the startup?


startup_route
{
$var(res) = 1;
$avp(tmp) = "1";
   # $var(x) = 0;
while($var(res) > 0)
{
$var(res) = avp_db_query("SELECT Distinct One800, dnis FROM 
DNIS_Mapping where One800 > $avp(tmp) order by One800;", 
"$avp(One800), $avp(dnis)");

if($var(res) >= 0)
{
$var(i) = 0;
while($(avp(One800)[$var(i)]) != "NULL")
{
cache_store("local", 
"DNIS_$(avp(dnis)[$var(i)])", "$(avp(One800)[$var(i)])");

$avp(tmp) = $(avp(One800)[$var(i)]);
 #   $var(x) = $var(x) + 1;
$(avp(One800)[$var(i)]) = "NULL";
$var(i) = $var(i) + 1;
#   xlog("$var(x) : $(avp(s:dnis)[$var(i)])");
}
}
}
}


On Tue, Jan 24, 2017 at 6:38 AM, Bogdan-Andrei Iancu 
> wrote:


Hi Ahmed,

So, the warnings pop up ONLY during startup sequence.  Do you use
startup route or any module performing mem caching of some DB
table (drouting, permission, etc) ? Usually, the first UDP child
is doing some heavy lifting during startup.

Regards,

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

On 01/19/2017 06:01 PM, Ahmed Munir wrote:

Hi Razvan,
During starting up the opensips service, I see the first opensips
child process (pid"11172) consumes CPU process to 70-80% and
later drop downs to 0.3 - 0.0 % CPU per core. See below;
[root@qorblpsisprxyd1 ~]# top -c -u opensips top - 10:49:54 up 76
days, 23:31,  5 users,  load average: 0.00, 0.00, 0.00 Tasks: 229
total,   1 running, 228 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.0%us,  0.1%sy,  0.0%ni, 99.9%id,  0.0%wa,  0.0%hi,
0.0%si,  0.0%st Mem:  65964364k total,  2568124k used, 63396240k
free,   180220k buffers Swap:  1023996k total,0k used, 
1023996k free,  1226104k cached   PID USER  PR  NI  VIRT 
RES  SHR S %CPU %MEMTIME+ COMMAND 11177 opensips  20   0 
165m 5696 4528 S  0.3  0.0   0:00.23 /usr/sbin/opensips -P

/var/run/opensips.pid -m 64 -u opensips -g opensips 11187
opensips  20   0  165m 5628 4460 S  0.3  0.0   0:00.41
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g
opensips 11166 opensips  20   0  165m 6892 5752 S  0.0  0.0  
0:00.23 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u
opensips -g opensips 11168 opensips  20   0  165m 1980  840 S 
0.0  0.0   0:00.00 /usr/sbin/opensips -P /var/run/opensips.pid -m

64 -u opensips -g opensips 11169 opensips  20   0  165m 1464  328
S  0.0  0.0   0:00.53 /usr/sbin/opensips -P /var/run/opensips.pid
-m 64 -u opensips -g opensips 11171 opensips  20   0  165m 1640 
504 S  0.0  0.0   0:00.15 /usr/sbin/opensips -P

/var/run/opensips.pid -m 64 -u opensips -g opensips 11172
opensips  20   0  166m  40m  38m S  0.0  0.1   0:02.61
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g
opensips 11174 opensips  20   0  165m 6304 5136 S  0.0  0.0  
0:00.24 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u
opensips -g opensips 11175 opensips  20   0  165m 5884 4716 S 
0.0  0.0   0:00.22 /usr/sbin/opensips -P /var/run/opensips.pid -m

64 -u opensips -g opensips 11179 opensips  20   0  165m 7660 6492
S  0.0  0.0   0:00.27 /usr/sbin/opensips -P /var/run/opensips.pid
-m 64 -u opensips -g opensips 11181 opensips  20   0  165m 7756
6588 S  0.0  0.0   0:00.33 /usr/sbin/opensips -P
/var/run/opensips.pid -m 64 -u opensips -g opensips 11183
opensips  20   0  165m 5520 4352 S  0.0  0.0   0:00.34
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g
opensips 11185 opensips  20   0  165m 7336 6168 S  0.0  0.0  
0:00.36 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u
opensips -g opensips 11189 opensips  20   0  165m 7320 6152 S 
0.0  0.0   0:00.36 /usr/sbin/opensips -P /var/run/opensips.pid -m

64 -u opensips -g opensips 11190 opensips  20   0  165m 4688 3528
S  0.0  0.0   0:00.30 /usr/sbin/opensips -P /var/run/opensips.pid
-m 64 -u opensips -g opensips

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-24 Thread Ahmed Munir

Yes, using startup route in my routing script and running DB query. This
kind of warning I didn't face using 1.6 and 1.8 opensips versions but 2.2.2.

Will you recommend async statement for my current routing (see below) for
the startup?

startup_route
{
$var(res) = 1;
$avp(tmp) = "1";
   # $var(x) = 0;
while($var(res) > 0)
{
$var(res) = avp_db_query("SELECT Distinct One800, dnis FROM
DNIS_Mapping where One800 > $avp(tmp) order by One800;", "$avp(One800),
$avp(dnis)");
if($var(res) >= 0)
{
$var(i) = 0;
while($(avp(One800)[$var(i)]) != "NULL")
{
cache_store("local", "DNIS_$(avp(dnis)[$var(i)])",
"$(avp(One800)[$var(i)])");
$avp(tmp) = $(avp(One800)[$var(i)]);
 #   $var(x) = $var(x) + 1;
$(avp(One800)[$var(i)]) = "NULL";
$var(i) = $var(i) + 1;
#   xlog("$var(x) : $(avp(s:dnis)[$var(i)])");
}
}
}
}


On Tue, Jan 24, 2017 at 6:38 AM, Bogdan-Andrei Iancu 
wrote:

> Hi Ahmed,
>
> So, the warnings pop up ONLY during startup sequence.  Do you use startup
> route or any module performing mem caching of some DB table (drouting,
> permission, etc) ? Usually, the first UDP child is doing some heavy lifting
> during startup.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 01/19/2017 06:01 PM, Ahmed Munir wrote:
>
> Hi Razvan,
>
> During starting up the opensips service, I see the first opensips child
> process (pid"11172) consumes CPU process to 70-80% and later drop downs to
> 0.3 - 0.0 % CPU per core. See below;
>
> [root@qorblpsisprxyd1 ~]# top -c -u opensips
> top - 10:49:54 up 76 days, 23:31,  5 users,  load average: 0.00, 0.00, 0.00
> Tasks: 229 total,   1 running, 228 sleeping,   0 stopped,   0 zombie
> Cpu(s):  0.0%us,  0.1%sy,  0.0%ni, 99.9%id,  0.0%wa,  0.0%hi,  0.0%si,
> 0.0%st
> Mem:  65964364k total,  2568124k used, 63396240k free,   180220k buffers
> Swap:  1023996k total,0k used,  1023996k free,  1226104k cached
>
>   PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
> 11177 opensips  20   0  165m 5696 4528 S  0.3  0.0   0:00.23
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11187 opensips  20   0  165m 5628 4460 S  0.3  0.0   0:00.41
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11166 opensips  20   0  165m 6892 5752 S  0.0  0.0   0:00.23
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11168 opensips  20   0  165m 1980  840 S  0.0  0.0   0:00.00
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11169 opensips  20   0  165m 1464  328 S  0.0  0.0   0:00.53
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11171 opensips  20   0  165m 1640  504 S  0.0  0.0   0:00.15
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11172 opensips  20   0  166m  40m  38m S  0.0  0.1   0:02.61
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11174 opensips  20   0  165m 6304 5136 S  0.0  0.0   0:00.24
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11175 opensips  20   0  165m 5884 4716 S  0.0  0.0   0:00.22
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11179 opensips  20   0  165m 7660 6492 S  0.0  0.0   0:00.27
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11181 opensips  20   0  165m 7756 6588 S  0.0  0.0   0:00.33
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11183 opensips  20   0  165m 5520 4352 S  0.0  0.0   0:00.34
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11185 opensips  20   0  165m 7336 6168 S  0.0  0.0   0:00.36
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11189 opensips  20   0  165m 7320 6152 S  0.0  0.0   0:00.36
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
> 11190 opensips  20   0  165m 4688 3528 S  0.0  0.0   0:00.30
> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
>
> [root@qorblpsisprxyd1 ~]# opensipsctl fifo ps
> Process::  ID=0 PID=11166 Type=attendant
> Process::  ID=1 PID=11168 Type=MI FIFO
> Process::  ID=2 PID=11169 Type=time_keeper
> Process::  ID=3 PID=11171 Type=timer
> Process::  ID=4 PID=11172 Type=SIP receiver udp:10.3.120.94:5060
> Process::  ID=5 PID=11174 Type=SIP receiver udp:10.3.120.94:5060
> Process::  ID=6 PID=11175 Type=SIP receiver udp:10.3.120.94:5060
> Process::  ID=7 PID=11177 Type=SIP receiver udp:10.3.120.94:5060
> Process::  ID=8 PID=11179 Type=SIP receiver udp:10.3.120.94:5060
> Process::  ID=9 PID=11181 Type=SIP receiver udp:10.3.120.94:5060
> Process::  ID=10 PID=11183

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-24 Thread Bogdan-Andrei Iancu


Hi Ahmed,

So, the warnings pop up ONLY during startup sequence.  Do you use 
startup route or any module performing mem caching of some DB table 
(drouting, permission, etc) ? Usually, the first UDP child is doing some 
heavy lifting during startup.


Regards,

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

On 01/19/2017 06:01 PM, Ahmed Munir wrote:

Hi Razvan,

During starting up the opensips service, I see the first opensips 
child process (pid"11172) consumes CPU process to 70-80% and later 
drop downs to 0.3 - 0.0 % CPU per core. See below;


[root@qorblpsisprxyd1 ~]# top -c -u opensips
top - 10:49:54 up 76 days, 23:31,  5 users,  load average: 0.00, 0.00, 
0.00

Tasks: 229 total,   1 running, 228 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.0%us,  0.1%sy,  0.0%ni, 99.9%id,  0.0%wa,  0.0%hi, 0.0%si,  
0.0%st

Mem:  65964364k total,  2568124k used, 63396240k free,   180220k buffers
Swap:  1023996k total,0k used,  1023996k free,  1226104k cached

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+ COMMAND
11177 opensips  20   0  165m 5696 4528 S  0.3  0.0   0:00.23 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11187 opensips  20   0  165m 5628 4460 S  0.3  0.0   0:00.41 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11166 opensips  20   0  165m 6892 5752 S  0.0  0.0   0:00.23 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11168 opensips  20   0  165m 1980  840 S  0.0  0.0   0:00.00 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11169 opensips  20   0  165m 1464  328 S  0.0  0.0   0:00.53 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11171 opensips  20   0  165m 1640  504 S  0.0  0.0   0:00.15 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11172 opensips  20   0  166m  40m  38m S  0.0  0.1   0:02.61 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11174 opensips  20   0  165m 6304 5136 S  0.0  0.0   0:00.24 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11175 opensips  20   0  165m 5884 4716 S  0.0  0.0   0:00.22 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11179 opensips  20   0  165m 7660 6492 S  0.0  0.0   0:00.27 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11181 opensips  20   0  165m 7756 6588 S  0.0  0.0   0:00.33 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11183 opensips  20   0  165m 5520 4352 S  0.0  0.0   0:00.34 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11185 opensips  20   0  165m 7336 6168 S  0.0  0.0   0:00.36 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11189 opensips  20   0  165m 7320 6152 S  0.0  0.0   0:00.36 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11190 opensips  20   0  165m 4688 3528 S  0.0  0.0   0:00.30 
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips


[root@qorblpsisprxyd1 ~]# opensipsctl fifo ps
Process::  ID=0 PID=11166 Type=attendant
Process::  ID=1 PID=11168 Type=MI FIFO
Process::  ID=2 PID=11169 Type=time_keeper
Process::  ID=3 PID=11171 Type=timer
Process::  ID=4 PID=11172 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=5 PID=11174 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=6 PID=11175 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=7 PID=11177 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=8 PID=11179 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=9 PID=11181 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=10 PID=11183 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=11 PID=11185 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=12 PID=11187 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=13 PID=11189 Type=SIP receiver udp:10.3.120.94:5060 


Process::  ID=14 PID=11190 Type=Timer handler

OpenSIPs used by each CPU processor;

[root@qorblpsisprxyd1 ~]# ps -o pid,psr,comm -C opensips
  PID PSR COMMAND
11166   0 opensips
11168   2 opensips
11169   6 opensips
11171   5 opensips
11172   5 opensips
11174   5 opensips
11175   5 opensips
11177   5 opensips
11179   7 opensips
11181   1 opensips
11183   0 opensips
11185   2 opensips
11187   5 opensips
11189   5 opensips
11190   4 opensips



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-24 Thread Bogdan-Andrei Iancu


Hi Agalya,

Please provide the output of "opensipsctl fifo ps"

Best regards.

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

On 01/19/2017 04:55 PM, Ramachandran, Agalya (Contractor) wrote:


Hi Razvan,

I didn’t see any process that is using more than 80% of a core. 
OpenSIPS is simply being idle and these warnings come periodically.


Like once in couple of hours. I didn’t track the exact time line, how 
frequent am getting this warnings.


Ahmed,

Do you notice these warnings only when you start OpenSIPS or could see 
it in regular intervals?


Regards,
Agalya

*From:*Users [mailto:users-boun...@lists.opensips.org] *On Behalf Of 
*Razvan Crainea

*Sent:* Thursday, January 19, 2017 3:33 AM
*To:* users@lists.opensips.org
*Subject:* Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start 
service


When starting opensips, is there any opensips process that is using 
more than 80% of a core? If so, can you pinpoint the PID in the 
opensipsctl ps command?


Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com <http://www.opensips-solutions.com>

On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote:

Same with my case too.

Regards,
Agalya

*From:*Users [mailto:users-boun...@lists.opensips.org] *On Behalf
Of *Ahmed Munir
*Sent:* Wednesday, January 18, 2017 1:31 PM
*To:* OpenSIPs Users <users@lists.opensips.org>
<mailto:users@lists.opensips.org>
    *Subject:* [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start
service

Hi,

I'm currently seeing the warnings when I start opensips service;

Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a
150 us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a 150
us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a 150
us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: utimer job  has a
229 us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
INFO:core:do_action : max while loops are
encountered
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]:
WARNING:core:utimer_ticker: utimer task  already
scheduled for 190 ms (now 2470 ms), it may over
lap..


I've tried to update the source code for timer.c (line#: 190) ref:

https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split,
but didn't work at all.

Currently running 8 child processors, see below;

[root@qorblpsisprxyd1 ]# opensips  -V
version: opensips 2.2.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC,
F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, 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.
main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7


[root@qorblpsisprxyd1 ]# opensipsctl fifo ps
Process::  ID=0 PID=3083 Type=attendant
Process::  ID=1 PID=3085 Type=MI FIFO
Process::  ID=2 PID=3086 Type=time_keeper
Process::  ID=3 PID=3088 Type=timer
Process::  ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060
<http://10.3.120.94:5060>
Process::  ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060
<http://10.3.120.94:5060>
Process::  ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060
<http://10.3.120.94:5060>
Process::  ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060
<http://10.3.120.94:5060>
Process::  ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060
<http://10.3.120.94:5060>
Process::  ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060
<http://10.3.120.94:5060>
Process::  ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060
<http://10.3.120.94:5060>
Process::  ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060
<http://10.3.120.94:5060>
Process::  ID=12 PID=3104 Type=Timer handler

I would like to know what changes required to fix this change?
Please advise.


-- 


Regards,

Ahmed Munir Chohan




___

Users mailing list

Users@lists.opensips.org <mailto:Users@lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-24 Thread Bogdan-Andrei Iancu


Hi,

Does this happen ONLY at startup ? without any other warnings during 
runtime ?


There is something interesting in your logs:

First is this log, saying you do an infinite loop in a "while" in the 
script:
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
INFO:core:do_action: max while loops are encountered
And secondly all the warning are from the same process (3089) which is 
the the first SIP UDP listener.


Do you use any startup route ?

Regards,

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

On 01/18/2017 08:30 PM, Ahmed Munir wrote:

Hi,

I'm currently seeing the warnings when I start opensips service;

Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 
us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us 
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us 
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: utimer job  has a 229 us 
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
INFO:core:do_action: max while loops are encountered
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: 
WARNING:core:utimer_ticker: utimer task  already scheduled 
for 190 ms (now 2470 ms), it may over

lap..


I've tried to update the source code for timer.c (line#: 190) ref: 
https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, 
but didn't work at all.


Currently running 8 child processors, see below;

[root@qorblpsisprxyd1 ]# opensips  -V
version: opensips 2.2.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, 
F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, 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.
main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7


[root@qorblpsisprxyd1 ]# opensipsctl fifo ps
Process::  ID=0 PID=3083 Type=attendant
Process::  ID=1 PID=3085 Type=MI FIFO
Process::  ID=2 PID=3086 Type=time_keeper
Process::  ID=3 PID=3088 Type=timer
Process::  ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 

Process::  ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 


Process::  ID=12 PID=3104 Type=Timer handler

I would like to know what changes required to fix this change? Please 
advise.


--
Regards,

Ahmed Munir Chohan



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-19 Thread Ahmed Munir

Hi Razvan,

During starting up the opensips service, I see the first opensips child
process (pid"11172) consumes CPU process to 70-80% and later drop downs to
0.3 - 0.0 % CPU per core. See below;

[root@qorblpsisprxyd1 ~]# top -c -u opensips
top - 10:49:54 up 76 days, 23:31,  5 users,  load average: 0.00, 0.00, 0.00
Tasks: 229 total,   1 running, 228 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.0%us,  0.1%sy,  0.0%ni, 99.9%id,  0.0%wa,  0.0%hi,  0.0%si,
0.0%st
Mem:  65964364k total,  2568124k used, 63396240k free,   180220k buffers
Swap:  1023996k total,0k used,  1023996k free,  1226104k cached

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
11177 opensips  20   0  165m 5696 4528 S  0.3  0.0   0:00.23
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11187 opensips  20   0  165m 5628 4460 S  0.3  0.0   0:00.41
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11166 opensips  20   0  165m 6892 5752 S  0.0  0.0   0:00.23
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11168 opensips  20   0  165m 1980  840 S  0.0  0.0   0:00.00
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11169 opensips  20   0  165m 1464  328 S  0.0  0.0   0:00.53
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11171 opensips  20   0  165m 1640  504 S  0.0  0.0   0:00.15
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11172 opensips  20   0  166m  40m  38m S  0.0  0.1   0:02.61
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11174 opensips  20   0  165m 6304 5136 S  0.0  0.0   0:00.24
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11175 opensips  20   0  165m 5884 4716 S  0.0  0.0   0:00.22
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11179 opensips  20   0  165m 7660 6492 S  0.0  0.0   0:00.27
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11181 opensips  20   0  165m 7756 6588 S  0.0  0.0   0:00.33
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11183 opensips  20   0  165m 5520 4352 S  0.0  0.0   0:00.34
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11185 opensips  20   0  165m 7336 6168 S  0.0  0.0   0:00.36
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11189 opensips  20   0  165m 7320 6152 S  0.0  0.0   0:00.36
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips
11190 opensips  20   0  165m 4688 3528 S  0.0  0.0   0:00.30
/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips

[root@qorblpsisprxyd1 ~]# opensipsctl fifo ps
Process::  ID=0 PID=11166 Type=attendant
Process::  ID=1 PID=11168 Type=MI FIFO
Process::  ID=2 PID=11169 Type=time_keeper
Process::  ID=3 PID=11171 Type=timer
Process::  ID=4 PID=11172 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=5 PID=11174 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=6 PID=11175 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=7 PID=11177 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=8 PID=11179 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=9 PID=11181 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=10 PID=11183 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=11 PID=11185 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=12 PID=11187 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=13 PID=11189 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=14 PID=11190 Type=Timer handler

OpenSIPs used by each CPU processor;

[root@qorblpsisprxyd1 ~]# ps -o pid,psr,comm -C opensips
  PID PSR COMMAND
11166   0 opensips
11168   2 opensips
11169   6 opensips
11171   5 opensips
11172   5 opensips
11174   5 opensips
11175   5 opensips
11177   5 opensips
11179   7 opensips
11181   1 opensips
11183   0 opensips
11185   2 opensips
11187   5 opensips
11189   5 opensips
11190   4 opensips


[root@qorblpsisprxyd1 ~]# lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):8
On-line CPU(s) list:   0-7
Thread(s) per core:1
Core(s) per socket:4
Socket(s): 2
NUMA node(s):  2
Vendor ID: GenuineIntel
CPU family:6
Model: 44
Stepping:  2
CPU MHz:   1197.000
BogoMIPS:  4266.58
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  256K
L3 cache:  8192K
NUMA node0 CPU(s): 0-3
NUMA node1 CPU(s): 4-7


Please advise for the fix as currently setting child processes to 10 in
opensips config.

Date: Thu, 19 Jan 2017 10:32:35 +0200
> From: Răzvan Crainea <raz...@opensips.org>
> To: users@lists.opensips.org
> Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start
> service
> Messa

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-19 Thread Ramachandran, Agalya (Contractor)

Hi Razvan,

I didn’t see any process that is using more than 80% of a core. OpenSIPS is 
simply being idle and these warnings come periodically.

Like once in couple of hours. I didn’t track the exact time line, how frequent 
am getting this warnings.

Ahmed,
Do you notice these warnings only when you start OpenSIPS or could see it in 
regular intervals?

Regards,
Agalya

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Razvan 
Crainea
Sent: Thursday, January 19, 2017 3:33 AM
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

When starting opensips, is there any opensips process that is using more than 
80% of a core? If so, can you pinpoint the PID in the opensipsctl ps command?

Best regards,


Răzvan Crainea

OpenSIPS Solutions

www.opensips-solutions.com<http://www.opensips-solutions.com>
On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote:
Same with my case too.

Regards,
Agalya

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Ahmed Munir
Sent: Wednesday, January 18, 2017 1:31 PM
To: OpenSIPs Users <users@lists.opensips.org><mailto:users@lists.opensips.org>
Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Hi,
I'm currently seeing the warnings when I start opensips service;

Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us delay 
in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us delay in 
execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us delay in 
execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: utimer job  has a 229 us delay in 
execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: INFO:core:do_action: 
max while loops are encountered
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: 
WARNING:core:utimer_ticker: utimer task  already scheduled for 190 
ms (now 2470 ms), it may over
lap..


I've tried to update the source code for timer.c (line#: 190) ref: 
https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split,
 but didn't work at all.
Currently running 8 child processors, see below;

[root@qorblpsisprxyd1 ]# opensips  -V
version: opensips 2.2.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, 
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, 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.
main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7


[root@qorblpsisprxyd1 ]# opensipsctl fifo ps
Process::  ID=0 PID=3083 Type=attendant
Process::  ID=1 PID=3085 Type=MI FIFO
Process::  ID=2 PID=3086 Type=time_keeper
Process::  ID=3 PID=3088 Type=timer
Process::  ID=4 PID=3089 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=5 PID=3091 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=6 PID=3092 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=7 PID=3094 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=8 PID=3096 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=9 PID=3098 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=10 PID=3100 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=11 PID=3102 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=12 PID=3104 Type=Timer handler
I would like to know what changes required to fix this change? Please advise.

--
Regards,

Ahmed Munir Chohan




___

Users mailing list

Users@lists.opensips.org<mailto:Users@lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-19 Thread Răzvan Crainea

When starting opensips, is there any opensips process that is using more 
than 80% of a core? If so, can you pinpoint the PID in the opensipsctl 
ps command?


Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote:


Same with my case too.

Regards,
Agalya

*From:*Users [mailto:users-boun...@lists.opensips.org] *On Behalf Of 
*Ahmed Munir

*Sent:* Wednesday, January 18, 2017 1:31 PM
*To:* OpenSIPs Users <users@lists.opensips.org>
*Subject:* [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Hi,

I'm currently seeing the warnings when I start opensips service;

Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 
us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us 
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us 
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: utimer job  has a 229 us 
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
INFO:core:do_action: max while loops are encountered
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: 
WARNING:core:utimer_ticker: utimer task  already scheduled 
for 190 ms (now 2470 ms), it may over

lap..

I've tried to update the source code for timer.c (line#: 190) ref: 
https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, 
but didn't work at all.


Currently running 8 child processors, see below;

[root@qorblpsisprxyd1 ]# opensips  -V
version: opensips 2.2.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, 
F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, 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.
main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7


[root@qorblpsisprxyd1 ]# opensipsctl fifo ps
Process::  ID=0 PID=3083 Type=attendant
Process::  ID=1 PID=3085 Type=MI FIFO
Process::  ID=2 PID=3086 Type=time_keeper
Process::  ID=3 PID=3088 Type=timer
Process::  ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 
<http://10.3.120.94:5060>
Process::  ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 
<http://10.3.120.94:5060>
Process::  ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 
<http://10.3.120.94:5060>
Process::  ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 
<http://10.3.120.94:5060>
Process::  ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 
<http://10.3.120.94:5060>
Process::  ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 
<http://10.3.120.94:5060>
Process::  ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 
<http://10.3.120.94:5060>
Process::  ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 
<http://10.3.120.94:5060>

Process::  ID=12 PID=3104 Type=Timer handler

I would like to know what changes required to fix this change? Please 
advise.



--

Regards,

Ahmed Munir Chohan



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-18 Thread Ramachandran, Agalya (Contractor)

Same with my case too.

Regards,
Agalya

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Ahmed Munir
Sent: Wednesday, January 18, 2017 1:31 PM
To: OpenSIPs Users <users@lists.opensips.org>
Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Hi,
I'm currently seeing the warnings when I start opensips service;

Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us delay 
in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us delay in 
execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: timer job  has a 150 us delay in 
execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: 
WARNING:core:handle_timer_job: utimer job  has a 229 us delay in 
execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: INFO:core:do_action: 
max while loops are encountered
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: 
WARNING:core:utimer_ticker: utimer task  already scheduled for 190 
ms (now 2470 ms), it may over
lap..

I've tried to update the source code for timer.c (line#: 190) ref: 
https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split,
 but didn't work at all.
Currently running 8 child processors, see below;

[root@qorblpsisprxyd1 ]# opensips  -V
version: opensips 2.2.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, 
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, 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.
main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7

[root@qorblpsisprxyd1 ]# opensipsctl fifo ps
Process::  ID=0 PID=3083 Type=attendant
Process::  ID=1 PID=3085 Type=MI FIFO
Process::  ID=2 PID=3086 Type=time_keeper
Process::  ID=3 PID=3088 Type=timer
Process::  ID=4 PID=3089 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=5 PID=3091 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=6 PID=3092 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=7 PID=3094 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=8 PID=3096 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=9 PID=3098 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=10 PID=3100 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=11 PID=3102 Type=SIP receiver 
udp:10.3.120.94:5060<http://10.3.120.94:5060>
Process::  ID=12 PID=3104 Type=Timer handler
I would like to know what changes required to fix this change? Please advise.

--
Regards,

Ahmed Munir Chohan
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

2017-01-18 Thread Ahmed Munir

Hi,

I'm currently seeing the warnings when I start opensips service;

Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a 150 us
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a 150 us delay
in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: timer job  has a 150 us delay
in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
WARNING:core:handle_timer_job: utimer job  has a 229 us
delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:
INFO:core:do_action: max while loops are encountered
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]:
WARNING:core:utimer_ticker: utimer task  already scheduled for
190 ms (now 2470 ms), it may over
lap..


I've tried to update the source code for timer.c (line#: 190) ref:
https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split,
but didn't work at all.

Currently running 8 child processors, see below;

[root@qorblpsisprxyd1 ]# opensips  -V
version: opensips 2.2.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, 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.
main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7


[root@qorblpsisprxyd1 ]# opensipsctl fifo ps
Process::  ID=0 PID=3083 Type=attendant
Process::  ID=1 PID=3085 Type=MI FIFO
Process::  ID=2 PID=3086 Type=time_keeper
Process::  ID=3 PID=3088 Type=timer
Process::  ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060
Process::  ID=12 PID=3104 Type=Timer handler

I would like to know what changes required to fix this change? Please
advise.

-- 
Regards,

Ahmed Munir Chohan
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

[OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

[OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

16 matches

Site Navigation

Mail list logo

Footer information