<div dir="ltr">See details 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, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT<br>ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535<br>poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.<br>main.c compiled on 11:09:47 Jan 13 2017 with gcc 4.4.7<br><br>[root@qorblpsisprxyd1 ~]# opensipsctl ps<br>Process:: ID=0 PID=8269 Type=attendant<br>Process:: ID=1 PID=8271 Type=MI FIFO<br>Process:: ID=2 PID=8272 Type=time_keeper<br>Process:: ID=3 PID=8274 Type=timer<br>Process:: ID=4 PID=8275 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=5 PID=8278 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=6 PID=8279 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=7 PID=8281 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=8 PID=8283 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=9 PID=8285 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=10 PID=8287 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=11 PID=8289 Type=SIP receiver udp:<a href="http://10.3.120.94:5060">10.3.120.94:5060</a><br>Process:: ID=12 PID=8291 Type=Timer handler<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><div><div class="gmail_extra">In /etc/default/opensips config, declaring shared and pkg memory as server memory is 64 GB;<br><br># Amount of shared memory to allocate for the running OpenSIPS server (in Mb)<br>S_MEMORY=256<br><br># Amount of pkg memory to allocate for the running OpenSIPS server (in Mb)<br>P_MEMORY=32<br><br></div><div class="gmail_extra">Let me know any other info needed from my end.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Date: Mon, 16 Jan 2017 10:49:37 +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 crashed<br>
Message-ID: <<a href="mailto:1584806e-a154-a5ad-a464-4eef609158f4@opensips.org">1584806e-a154-a5ad-a464-<wbr>4eef609158f4@opensips.org</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
Hi, Ahmed!<br>
<br>
Can you tell us exactly what revision of OpenSIPS you are using? Please<br>
provide the output of the following commands:<br>
opensips -V<br>
opensipsctl ps<br>
<br>
Also, during startup, is there a process who's "eating" a lot of CPU? If<br>
so, can you pinpoint the PID to see what type of process is that?<br>
<br>
Regarding the avp_db_query() issue, did you define a db_url parameter<br>
for it? Also I am not sure you can do something like $var(res) =<br>
avp_db_query(...). But anyways, this is something completely different,<br>
so please open a different topic for it.<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/14/2017 12:24 AM, Ahmed Munir wrote:<br>
> Hi,<br>
><br>
> I've just installed new version of opensips 2.2.2 on the test box and<br>
> updated by routing script, the issue currently I'm seeing alot warning<br>
> messages while starting opensips service below;<br>
><br>
> /usr/sbin/opensips[6902]: WARNING:core:handle_timer_job: utimer job<br>
> <tm-utimer> has a 2830000 us delay in execution<br>
><br>
> Number of children running on that server is 8 as it is 8 core processor.<br>
><br>
> I would like to know what steps do I need to take to fix this issue.<br>
> Btw, warnings only occurred during the time of starting opensips<br>
> service but not during calls.<br>
><br>
><br>
> Further added, a issue I face using avp_db_query () function i.e. when<br>
> using it as<br>
><br>
> $var(res) = avp_db_query("SELECT Outpulse_number,setid FROM<br>
> Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse),<br>
> $avp(trunkid)");<br>
><br>
> failed to start opensips service due to errors below;<br>
><br>
> ERROR:avpops:__fixup_db_query_<wbr>avp: no db url defined to be used by<br>
> this function<br>
> ERROR:core:fix_actions: fixing failed (code=-6) at<br>
> //etc/opensips/opensips.cfg:<wbr>207<br>
> CRITICAL:core:fix_expr: fix_actions error<br>
> ERROR:core:main: failed to fix configuration with err code -6<br>
><br>
><br>
> If I add this line: avp_db_query("SELECT 1"); above to my $var(res) db<br>
> query, opensips service starts successfully.<br>
><br>
> Please advise the steps do I need to take to fix above issues.<br>
><br>
><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>