<div dir="auto">I think you can. Check the documentation of rtpengine on github. And if you can, please use the latest commit. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 3 Dec 2019, 18:02 Callum Guy, <<a href="mailto:callum.guy@x-on.co.uk">callum.guy@x-on.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi All,<br><div><br></div><div>I'm working through this memory issue and have some additional data. The server crashed this afternoon due to memory exhaustion on a UDP listener process, as far as I know at this time. Note that the processes all have 4GB assigned so this is a gradual and constant growth issue. </div><div><br></div><div>At this point I have my suspicions that it could be related to the RTPEngine module - the first memory allocation error messages are all related to what I believe the be RTCP session reports coming in from the RTP engine servers. These came through about every second for an hour before OpenSIPs finally gave up the ghost and restarted.</div><div><br></div><div>Is this normal behaviour? We have only recently moved to RTPEngine from RTPProxy so I am new to this software. Does anyone know if it is possible to prevent RTPEngine from sending this data to OpenSIPs - its not something that we require and I'd like to check if this is at all related to the memory growth. Any other ideas would also be appreciated!</div><div><br></div><div>Many thanks,</div><div><br></div><div>Callum</div><div><font face="monospace"><br></font></div><div><font face="monospace">2019-12-03T11:48:14.653225+00:00 TH-P-SIPREG-1 opensips[2521]: ERROR:core:fm_malloc: not enough free pkg memory (214628248 bytes left, need 536), please increase the "-M" command line parameter!<br>2019-12-03T11:48:14.653851+00:00 TH-P-SIPREG-1 opensips[2521]: INFO:core:fm_malloc: attempting defragmentation...<br>2019-12-03T11:48:15.651495+00:00 TH-P-SIPREG-1 opensips[2521]: INFO:core:fm_malloc: unable to alloc a big enough fragment!<br>2019-12-03T11:48:15.652218+00:00 TH-P-SIPREG-1 opensips[2521]: ERROR:rtpengine:rtpe_function_call: failed to decode bencoded reply from proxy: d7:createdi1575373650e10:created_usi505483e11:last signali1575373670e4:SSRCd10:3831331386d11:average MOSd3:MOSi44e15:round-trip timei6754e6:jitteri0e11:packet lossi0e7:samplesi9ee10:lowest MOSd3:MOSi44e15:round-trip timei6175e6:jitteri0e11:packet lossi0e11:reported ati1575373656ee11:highest MOSd3:MOSi44e15:round-trip timei6175e6:jitteri0e11:packet lossi0e11:reported ati1575373656ee15:MOS progressiond8:intervali3e7:entriesld3:MOSi44e15:round-trip timei6175e6:jitteri0e11:packet lossi0e11:reported ati1575373656eed3:MOSi44e15:round-trip timei6307e6:jitteri0e11:packet lossi0e11:reported ati1575373660eed3:MOSi44e15:round-trip timei6884e6:jitteri0e11:packet lossi0e11:reported ati1575373664eed3:MOSi44e15:round-trip timei7016e6:jitteri0e11:packet lossi0e11:reported ati1575373668eed3:MOSi44e15:round-trip timei6368e6:jitteri0e11:packet lossi0e11:reported ati1575373674eed3:MOSi44e15:round-trip timei6929e6:jitteri0e11:packet lossi0e11:reported ati1575373679eed3:MOSi44e15:round-trip timei6884e6:jitteri0e11:packet lossi0e11:reported ati1575373684eed3:MOSi44e15:round-trip timei7241e6:jitteri0e11:packet lossi0e11:reported ati1575373689eed3:MOSi44e15:round-trip timei6988e6:jitteri0e11:packet lossi0e11:reported ati1575373694eeeee10:1028099660d11:average MOSd3:MOSi43e15:round-trip timei29936e6:jitteri0e11:packet lossi0e7:samplesi7ee10:lowest MOSd3:MOSi43e15:round-trip timei29515e6:jitteri0e11:packet lossi0e11:reported ati1575373661ee11:highest MOSd3:MOSi43e15:round-trip timei29515e6:jitteri0e11:packet lossi0e11:reported ati1575373661ee15:MOS progressiond8:intervali3e7:entriesld3:MOSi43e15:round-trip timei29515e6:jitteri0e11:packet lossi0e11:reported ati1575373661eed3:MOSi43e15:round-trip timei29817e6:jitteri0e11:packet lossi0e11:reported ati1575373666eed3:MOSi43e15:round-trip timei30695e6:jitteri0e11:packet lossi0e11:reported ati1575373671eed3:MOSi43e15:round-trip timei29541e6:jitteri0e11:packet lossi0e11:reported ati1575373676eed3:MOSi43e15:round-trip timei30073e6:jitteri0e11:packet lossi0e11:reported ati1575373681eed3:MOSi43e15:round-trip timei29526e6:jitteri0e11:packet lossi0e11:reported ati1575373686eed3:MOSi43e15:round-trip timei30391e6:jitteri0e11:packet lossi0e11:reported ati1575373691eeeeee4:tagsd10:3044367218d3:tag10:30443672187:createdi1575373650e16:in dialogue with13:N8Nr5mDpcNt1a6:mediasld5:indexi1e4:type5:audio8:protocol7:RTP/AVP7:streamsld10:local porti32494e8:endpointd6:family4:IPv47:address13:51.51.51.514:porti47360ee19:advertised endpointd6:family4:IPv47:address9:10.0.0.154:porti12672ee11:last packeti1575373694e5:flagsl3:RTP6:filled9:confirmed10:kernelizede4:SSRCi1028099660e5:statsd7:packetsi2045e5:bytesi351740e6:errorsi0eeed10:local porti32495e8:endpointd6:family4:IPv47:address13:51.51.51.514:porti47361ee19:advertised endpointd6:family4:IPv47:address9:10.0.0.154:porti12673ee11:last packeti1575373691e5:flagsl4:RTCP6:filled9:confirmed10:kernelized17:no kernel supporte4:SSRCi1028099660e5:statsd7:packetsi8e5:bytesi1240e6:errorsi0eeee5:flagsl11:initialized4:send4:recveeee13:N8Nr5mDpcNt1ad3:tag13:N8Nr5mDpcNt1a7:createdi1575373650e16:in dialogue with10:30443672186:mediasld5:indexi1e4:type5:audio8:protocol7:RTP/AVP7:streamsld10:local porti34226e8:endpointd6:family4:IPv47:address15:192.168.163.2224:porti11484ee19:advertised endpointd6:family4:IPv47:address15:192.168.163.2224:porti11484ee11:last packeti1575373694e5:flagsl3:RTP6:filled9:confirmed10:kernelizede4:SSRCi3831331386e5:statsd7:packetsi2018e5:bytesi347096e6:errorsi0eeed10:local porti34227e8:endpointd6:family4:IPv47:address15:192.168.163.2224:porti11485ee19:advertised endpointd6:family4:IPv47:address15:192.168.163.2224:porti11485ee11:last packeti1575373694e5:flagsl4:RTCP6:filled9:confirmed10:kernelized17:no kernel supporte4:SSRCi3831331386e5:statsd7:packetsi9e5:bytesi1008e6:errorsi0eeee5:flagsl11:initialized4:send4:recv15:ICE controllingeeeee6:totalsd3:RTPd7:packetsi4063e5:bytesi698836e6:errorsi0ee4:RTCPd7:packetsi17e5:bytesi2248e6:errorsi0eee6:result2:oke</font><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 30 Nov 2019 at 22:51, Callum Guy <<a href="mailto:callum.guy@x-on.co.uk" target="_blank" rel="noreferrer">callum.guy@x-on.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Hi Ben,<div dir="auto"><br></div><div dir="auto">Thank you for your reply and insight here, very helpful to know you're running a drastically different setting for the package memory.</div><div dir="auto"><br></div><div dir="auto">I presumed if it preallocated that I would have seen some issues during testing, hence I've ended up with figures that were intended to provide 75% of the system memory to the application.<br></div><div dir="auto"><br></div><div dir="auto">Memory usage had been creeping up all day at the time of writing however migrations to this platform had been on hold since the initial capture of memory usage although call traffic would have been relatively even during daytime hours where the increase continued. On that basis I'm still concerned that there is an issue with my config causing this growth however I've now increased available memory and restarted so I should have ample time to investigate this week, I'll report back any findings for the community benefit. I will give some serious thought to lowering the package allocation value once I've got to grips with the situation.</div><div dir="auto"><br></div><div dir="auto">Usefully this implementation shares a lot of common components to another variant which acts as a pure proxy and does not deal with registrations where I'm not seeing this issue so that will narrow down the search area somewhat.</div><div dir="auto"><br></div><div dir="auto">Thanks again for your time,</div><div dir="auto"><br></div><div dir="auto">Callum</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 30 Nov 2019, 15:46 Ben Newlin, <<a href="mailto:Ben.Newlin@genesys.com" target="_blank" rel="noreferrer">Ben.Newlin@genesys.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal">Callum,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">It’s my understanding that OpenSIPS does not release memory back to the OS, but it also pre-allocates all memory at startup into its private pool and then allocates from that internally. Normally shared memory should be significantly higher
than package memory. For reference, on our system we run with “-m 1024 -M 64” and that is sufficient for us to process very high traffic volume. We don’t do registration though, so that may affect the sizes you need.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">You are setting your package memory size to 4G, so that will allocate 4G memory for every package (process) that loads and then 2G for shared memory. That will use up all the memory on your machine extremely quickly for sure. The statistics
you provided seem like the memory increase is consistent with higher traffic levels on the second reading. You can see in your case that all of your “pkmem” processes have an extremely high amount of free memory (~3GB!). But that memory is still allocated
from the OS, so you are instructing OpenSIPS to allocate much more than your system memory right at startup.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Your shared memory also has just under 2GB free, so you have a lot of headroom there too. Since OpenSIPS pre-allocates, the amount of memory being used by the system overall should be fairly steady; if it is continuously increasing that
implies a leak somewhere. IIRC there are a few processes/modules/commands in OpenSIPS or libraries it uses that do allocate memory directly from the system and not from OpenSIPS’ pool. You may need to investigate some of those to find out where your memory
is going, or look at other processes/daemons you have running that could be using that memory.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="color:black">Ben Newlin </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Users <<a href="mailto:users-bounces@lists.opensips.org" rel="noreferrer noreferrer" target="_blank">users-bounces@lists.opensips.org</a>> on behalf of Callum Guy <<a href="mailto:callum.guy@x-on.co.uk" rel="noreferrer noreferrer" target="_blank">callum.guy@x-on.co.uk</a>><br>
<b>Reply-To: </b>OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" rel="noreferrer noreferrer" target="_blank">users@lists.opensips.org</a>><br>
<b>Date: </b>Friday, November 29, 2019 at 10:57 AM<br>
<b>To: </b>OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" rel="noreferrer noreferrer" target="_blank">users@lists.opensips.org</a>><br>
<b>Subject: </b>[OpenSIPS-Users] Memory Leak - runtime flags?<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Hi All,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I have recently deployed a new registrar and have been seeing a gradual increase in the memory footprint - enough that I'm having to expand the RAM (its virtualised) to ensure it doesn't run out.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">You can see a diff of the statistics collected last night at 11pm and today at 3pm here: <a href="https://gist.github.com/spacetourist/2103503674e134bd598c7f1e3a82674c/revisions" rel="noreferrer noreferrer" target="_blank">https://gist.github.com/spacetourist/2103503674e134bd598c7f1e3a82674c/revisions</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Processes 5-9 are my UDP SIP receiver threads (autoscaled down from an initial footprint of 20 threads).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Using 3.0.1 on CentOS 7 8GB RAM (soon to be 32GB!). Currently OpenSIPs is using all the RAM (minus OS usage) and 2GB of swap. Trying to use dialog and dr clustering if that is significant. Alos have NAT pings configured for all registrations
(4000 at time of writing).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">I am using runtime configuration flags of "<b>-m 2048 -M 4096</b>" and am concerned that these were (way) too high, I think I've misinterpreted their meaning during initial setup. Is this a ridiculous setting for my environment? Is it just
as simple as OpenSIPs being greedy with the memory such that it doesn't bother to free anything while each process free space remaining? Should my -M value * max number of processes fit into my RAM? I guess with an 8GB system that would mean dropping this
to "-M 256"?<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I've done some research into the issue however I haven't found anything else that would be an obvious target so wondered if the community might have some ideas of where I can begin investigations. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Many thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Callum<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><span style="border:1pt solid windowtext;padding:0in"><img border="0" width="32" height="32" style="width:0.3333in;height:0.3333in" id="m_5760916369927915gmail-m_-6107517085594241240m_6008324240704655150_x0000_i1028" alt="Image removed by sender."></span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><b><sup><span style="font-size:13.5pt;font-family:Verdana,sans-serif">0333 332 0000 |
<a href="http://www.x-on.co.uk" rel="noreferrer noreferrer" target="_blank">
www.x-on.co.uk</a> | </span></sup></b><b><sub><span style="font-size:13.5pt;font-family:Verdana,sans-serif"> </span></sub></b><b><sup><span style="font-size:13.5pt;font-family:Verdana,sans-serif"><a href="https://www.linkedin.com/company/x-on" rel="noreferrer noreferrer" target="_blank"><span style="color:windowtext;text-decoration:none"><span style="color:blue;border:1pt solid windowtext;padding:0in"><img border="0" width="24" height="24" style="width:0.25in;height:0.25in" id="m_5760916369927915gmail-m_-6107517085594241240m_6008324240704655150_x0000_i1027" alt="Image removed by sender."></span></span></a>
<a href="https://www.facebook.com/XonTel" rel="noreferrer noreferrer" target="_blank"><span style="color:windowtext;text-decoration:none"><span style="color:blue;border:1pt solid windowtext;padding:0in"><img border="0" width="24" height="24" style="width:0.25in;height:0.25in" id="m_5760916369927915gmail-m_-6107517085594241240m_6008324240704655150_x0000_i1026" alt="Image removed by sender."></span></span></a>
<a href="https://twitter.com/xonuk" rel="noreferrer noreferrer" target="_blank"><span style="color:windowtext;text-decoration:none"><span style="color:blue;border:1pt solid windowtext;padding:0in"><img border="0" width="24" height="24" style="width:0.25in;height:0.25in" id="m_5760916369927915gmail-m_-6107517085594241240m_6008324240704655150_x0000_i1025" alt="Image removed by sender."></span></span></a></span></sup></b><b><span style="font-size:13.5pt"> </span></b><u></u><u></u></p>
<p><span style="font-size:6pt;font-family:Verdana,sans-serif;color:black">X-on is a trading name of Storacall Technology Ltd a limited company registered in England and Wales.<br>
Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, Herts, HP3 9SD. Company Registration No. 2578478.<br>
The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient, please notify X-on immediately on +44(0)333 332 0000 and delete the<br>
message from your computer. If you are not a named addressee you must not use, disclose, disseminate, distribute, copy, print or reply to this email. Views or opinions expressed by an individual<br>
within this email may not necessarily reflect the views of X-on or its associated companies. Although X-on routinely screens for viruses, addressees should scan this email and any attachments<br>
for viruses. X-on makes no representation or warranty as to the absence of viruses in this email or any attachments.</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" rel="noreferrer noreferrer" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>
</blockquote></div></div>
<br>
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><font size="3" face="Verdana"><span style="font-size:8px;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline"></span></font></p><div><img src="https://www.x-on.co.uk/email/footer/General-Practice-Awards-winners.jpg"></div><div><br></div><div><div><div><font size="4"><b><sup><font face="Verdana">0333 332 0000 | <a href="http://www.x-on.co.uk" target="_blank" rel="noreferrer">www.x-on.co.uk</a> | <sub> </sub></font></sup></b></font><font size="4"><b><sub><sup><font face="Verdana"><a href="https://www.linkedin.com/company/x-on" target="_blank" rel="noreferrer"><img src="http://www.x-on.co.uk//images/icon/linkedin.png" width="24" height="24"></a> <a href="https://www.facebook.com/XonTel" target="_blank" rel="noreferrer"><img src="http://www.x-on.co.uk//images/icon/facebook.png" width="24" height="24"></a> <a href="https://twitter.com/xonuk" target="_blank" rel="noreferrer"><img src="http://www.x-on.co.uk//images/icon/twitter.png" width="24" height="24"></a></font></sup></sub> </b></font><br><p><span style="font-size:6.0pt;font-family:Verdana;color:black">X-on
is a trading name of Storacall Technology Ltd a limited company registered in
England and Wales.<br>
Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead,
Herts, HP3 9SD. Company Registration No. 2578478.<br>
The information in this e-mail is confidential and for use by the addressee(s)
only. If you are not the intended recipient, please notify X-on immediately on <span>+44(0)333 332 0000</span> and delete the<br>message from your computer. If you are not a named addressee you must not use,
disclose, disseminate, distribute, copy, print or reply to this email. </span><span style="font-size:6.0pt;font-family:Verdana;color:black">Views
or opinions expressed by an individual<br>within this email may not necessarily
reflect the views of X-on or its associated companies. Although X-on routinely
screens for viruses, addressees should scan this email and any attachments<br>for
viruses. X-on makes no representation or warranty as to the absence of viruses
in this email or any attachments.</span></p>
<p><span style="font-size:6.0pt;font-family:Verdana;color:black"></span><font size="2"><span style="font-size:6.0pt;font-family:Verdana;color:black"></span></font></p></div></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank" rel="noreferrer">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>