<div dir="ltr"><div>Hi Razvan,<br><br></div>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;<br><br>[root@qorblpsisprxyd1 ~]# top -c -u opensips<br>top - 10:49:54 up 76 days, 23:31, 5 users, load average: 0.00, 0.00, 0.00<br>Tasks: 229 total, 1 running, 228 sleeping, 0 stopped, 0 zombie<br>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<br>Mem: 65964364k total, 2568124k used, 63396240k free, 180220k buffers<br>Swap: 1023996k total, 0k used, 1023996k free, 1226104k cached<br><br> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND<br>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<br>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<br>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<br>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<br>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<br>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<br>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<br>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<br>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<br>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<br>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<br>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<br>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<br>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<br>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<br><br><div><div><div class="gmail_extra">[root@qorblpsisprxyd1 ~]# opensipsctl fifo ps<br>Process:: ID=0 PID=11166 Type=attendant<br>Process:: ID=1 PID=11168 Type=MI FIFO<br>Process:: ID=2 PID=11169 Type=time_keeper<br>Process:: ID=3 PID=11171 Type=timer<br>Process:: ID=4 PID=11172 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=5 PID=11174 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=6 PID=11175 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=7 PID=11177 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=8 PID=11179 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=9 PID=11181 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=10 PID=11183 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=11 PID=11185 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=12 PID=11187 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=13 PID=11189 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=14 PID=11190 Type=Timer handler<br><br>OpenSIPs used by each CPU processor;<br><br>[root@qorblpsisprxyd1 ~]# ps -o pid,psr,comm -C opensips<br> PID PSR COMMAND<br>11166 0 opensips<br>11168 2 opensips<br>11169 6 opensips<br>11171 5 opensips<br>11172 5 opensips<br>11174 5 opensips<br>11175 5 opensips<br>11177 5 opensips<br>11179 7 opensips<br>11181 1 opensips<br>11183 0 opensips<br>11185 2 opensips<br>11187 5 opensips<br>11189 5 opensips<br>11190 4 opensips<br><br><br>[root@qorblpsisprxyd1 ~]# lscpu<br>Architecture: x86_64<br>CPU op-mode(s): 32-bit, 64-bit<br>Byte Order: Little Endian<br>CPU(s): 8<br>On-line CPU(s) list: 0-7<br>Thread(s) per core: 1<br>Core(s) per socket: 4<br>Socket(s): 2<br>NUMA node(s): 2<br>Vendor ID: GenuineIntel<br>CPU family: 6<br>Model: 44<br>Stepping: 2<br>CPU MHz: 1197.000<br>BogoMIPS: 4266.58<br>Virtualization: VT-x<br>L1d cache: 32K<br>L1i cache: 32K<br>L2 cache: 256K<br>L3 cache: 8192K<br>NUMA node0 CPU(s): 0-3<br>NUMA node1 CPU(s): 4-7<br><br><br></div><div class="gmail_extra">Please advise for the fix as currently setting child processes to 10 in opensips config. <br></div><div class="gmail_extra"><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Date: Thu, 19 Jan 2017 10:32:35 +0200<br>
From: Răzvan Crainea <<a href="mailto:razvan@opensips.org">razvan@opensips.org</a>><br>
To: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start<br>
service<br>
Message-ID: <<a href="mailto:2d785128-affa-c955-e779-1d4305ec1119@opensips.org">2d785128-affa-c955-e779-<wbr>1d4305ec1119@opensips.org</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
When starting opensips, is there any opensips process that is using more<br>
than 80% of a core? If so, can you pinpoint the PID in the opensipsctl<br>
ps command?<br>
<br>
Best regards,<br>
<br>
Răzvan Crainea<br>
OpenSIPS Solutions<br>
<a href="http://www.opensips-solutions.com" rel="noreferrer" target="_blank">www.opensips-solutions.com</a><br>
<br>
On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote:<br>
><br>
> Same with my case too.<br>
><br>
> Regards,<br>
> Agalya<br>
><br>
> *From:*Users [mailto:<a href="mailto:users-bounces@lists.opensips.org">users-bounces@lists.<wbr>opensips.org</a>] *On Behalf Of<br>
> *Ahmed Munir<br>
> *Sent:* Wednesday, January 18, 2017 1:31 PM<br>
> *To:* OpenSIPs Users <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
> *Subject:* [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service<br>
><br>
> Hi,<br>
><br>
> I'm currently seeing the warnings when I start opensips service;<br>
><br>
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:<br>
> WARNING:core:handle_timer_job: timer job <blcore-expire> has a 1500000<br>
> us delay in execution<br>
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:<br>
> WARNING:core:handle_timer_job: timer job <tm-timer> has a 1500000 us<br>
> delay in execution<br>
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:<br>
> WARNING:core:handle_timer_job: timer job <dlg-timer> has a 1500000 us<br>
> delay in execution<br>
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:<br>
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 2290000 us<br>
> delay in execution<br>
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]:<br>
> INFO:core:do_action: max while loops are encountered<br>
> Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]:<br>
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled<br>
> for 190 ms (now 2470 ms), it may over<br>
> lap..<br>
><br>
> I've tried to update the source code for timer.c (line#: 190) ref:<br>
> <a href="https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split" rel="noreferrer" target="_blank">https://github.com/OpenSIPS/<wbr>opensips/commit/<wbr>fd8f6ec442b4365da9d274af693995<wbr>4246ece865?diff=split</a>,<br>
> but didn't work at all.<br>
><br>
> Currently running 8 child processors, see below;<br>
><br>
> [root@qorblpsisprxyd1 ]# opensips -V<br>
> version: opensips 2.2.2 (x86_64/linux)<br>
> flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC,<br>
> F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT<br>
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,<br>
> MAX_URI_SIZE 1024, BUF_SIZE 65535<br>
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.<br>
> main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7<br>
><br>
><br>
> [root@qorblpsisprxyd1 ]# opensipsctl fifo ps<br>
> Process:: ID=0 PID=3083 Type=attendant<br>
> Process:: ID=1 PID=3085 Type=MI FIFO<br>
> Process:: ID=2 PID=3086 Type=time_keeper<br>
> Process:: ID=3 PID=3088 Type=timer<br>
> Process:: ID=4 PID=3089 Type=SIP receiver udp:<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">10.3.120.94:5060</a><br>
> <<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">http://10.3.120.94:5060</a>><br>
> Process:: ID=5 PID=3091 Type=SIP receiver udp:<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">10.3.120.94:5060</a><br>
> <<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">http://10.3.120.94:5060</a>><br>
> Process:: ID=6 PID=3092 Type=SIP receiver udp:<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">10.3.120.94:5060</a><br>
> <<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">http://10.3.120.94:5060</a>><br>
> Process:: ID=7 PID=3094 Type=SIP receiver udp:<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">10.3.120.94:5060</a><br>
> <<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">http://10.3.120.94:5060</a>><br>
> Process:: ID=8 PID=3096 Type=SIP receiver udp:<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">10.3.120.94:5060</a><br>
> <<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">http://10.3.120.94:5060</a>><br>
> Process:: ID=9 PID=3098 Type=SIP receiver udp:<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">10.3.120.94:5060</a><br>
> <<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">http://10.3.120.94:5060</a>><br>
> Process:: ID=10 PID=3100 Type=SIP receiver udp:<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">10.3.120.94:5060</a><br>
> <<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">http://10.3.120.94:5060</a>><br>
> Process:: ID=11 PID=3102 Type=SIP receiver udp:<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">10.3.120.94:5060</a><br>
> <<a href="http://10.3.120.94:5060" rel="noreferrer" target="_blank">http://10.3.120.94:5060</a>><br>
> Process:: ID=12 PID=3104 Type=Timer handler<br>
><br>
> I would like to know what changes required to fix this change? Please<br>
> advise.<br>
><br>
><br>
> --<br>
><br>
> Regards,<br>
><br>
> Ahmed Munir Chohan<br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-<wbr>bin/mailman/listinfo/users</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20170119/81b8d547/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.opensips.org/<wbr>pipermail/users/attachments/<wbr>20170119/81b8d547/attachment-<wbr>0001.html</a>><br>
<br><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Regards,<br><br>Ahmed Munir Chohan<br><br></div>
</div></div></div></div>