Quick update here after a discussion with Liviu.
It looks (after checking the #3235 issue, that it is the httpd process,
responsible for running the MI cmds when JSONRPC is used. And it is
about listing dialog, so a command that may produce a huge output.
The exact issue you are reporting here was solved some time ago, please
check :
f91a4aa0c8 - 3.2.12
d4edccc628 - 3.2.13
You should have them if running 3.2.15 - are you sure you are using the
right code and binaries (as version) ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 11/13/23 9:50 AM, Bogdan-Andrei Iancu wrote:
Hi Alexander,
The warning is actually reporting a highly fragmented memory and not a
lack of memory. It reports 303 available Mb, but not a single
continuous slot for like 33K.
By doing an MI "ps", could you identify the name/type of the process
reporting this issue ? do you get it from a single process or from
multiple processes ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 11/9/23 4:32 PM, Alexander Kogan wrote:
I've tried all of them - Q, F, and HP with the same result.
Best regards,
Alexander Kogan,
Director of R&D317724640
5g Future
http://5gfuture.com
On 09.11.2023 18:24, solarmon wrote:
What memory management and allocator are you using?
I had similar issues using opensips 3.2.7 and the quick workaround
was to change from F_MALLOC to HP_MALLOC. But I thought there should
have been fixes for such issues in newer versions, so your issue
might be different.
On Thu, 9 Nov 2023 at 12:33, Alexander Kogan <[email protected]>
wrote:
Hi,
of course I did. It doesn't help.
Best regards,
Alexander Kogan,
Director of R&D
5g Future
http://5gfuture.com
On 09.11.2023 16:03, Marcin Groszek wrote:
> You may try adding more pgk memory in
>
> /etc/sysconfig/opensips i.e.
>
> P_MEMORY=256
>
>
> On 11/9/2023 5:07 AM, Alexander Kogan wrote:
>> Hello all,
>>
>> I regularly get a memory error after upgrading to 3.2.14 and
3.2.15
>> builds.
>>
>> Nov 9 11:53:02 FI173 /usr/sbin/opensips[3243]:
>> WARNING:core:fm_malloc: not enough contiguous free pkg memory
>> (317724640 bytes left, need 33832), attempting
defragmentation...
>> please increase the "-M" command line parameter!
>> Nov 9 11:53:02 FI173 /usr/sbin/opensips[3243]:
ERROR:core:fm_malloc:
>> not enough free pkg memory (317724640 bytes left, need
33832), please
>> increase the "-M" command line parameter!
>> Nov 9 11:53:02 FI173 /usr/sbin/opensips[3243]:
>> ERROR:core:receive_msg: no pkg mem left for sip_msg
>>
>> Surprisingly, it happens only with one or two UDP workers of
15 or
>> more. I've already created issue
>> https://github.com/OpenSIPS/opensips/issues/3235 and I'm
waiting for it.
>>
>> Meanwhile, I'm looking for a way of restarting particular
opensips
>> process. Is it possible?
>>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
