[OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service

Tue Jan 24 11:00:43 EST 2017

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 <tm-utimer> has a 20000 us delay in execution
Jan 24 15:04:15 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us delay in execution
Jan 24 15:10:02 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 80000 us delay in execution
Jan 24 15:19:35 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us delay in execution
Jan 24 15:23:42 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us delay in execution
Jan 24 15:25:55 /usr/local/sbin/opensips[27872]: WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us delay in execution
Jan 24 15:42:04 /usr/local/sbin/opensips[27860]: WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us delay in execution

Regards,
Agalya
From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
Sent: Tuesday, January 24, 2017 6:34 AM
To: OpenSIPS users mailling list <users at lists.opensips.org>; Ramachandran, Agalya (Contractor) <Agalya_Ramachandran at 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-bounces at lists.opensips.org] On Behalf Of Razvan Crainea
Sent: Thursday, January 19, 2017 3:33 AM
To: users at lists.opensips.org<mailto:users at 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-bounces at lists.opensips.org] On Behalf Of Ahmed Munir
Sent: Wednesday, January 18, 2017 1:31 PM
To: OpenSIPs Users <users at lists.opensips.org><mailto:users at 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 <blcore-expire> has a 1500000 us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job <tm-timer> has a 1500000 us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job <dlg-timer> has a 1500000 us delay in execution
Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 2290000 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 <tm-utimer> 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 at 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 at 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 at lists.opensips.org<mailto:Users at lists.opensips.org>

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

_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto: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/20170124/ca21fb0d/attachment-0001.html>