I put the -m to 7168 and -M to 512 , i dont think this is a good way and as
i never see this happen before on a real server (not VM) i think that the
kvm can be the problem, i have 400 call with 8MB private memory without
problem i cant understand how this server got this problem otherwise the VM
Hello Guys,
I got the same problem again
this is how im executing
/usr/local/opensips/sbin/opensips -P /var/run/opensips.pid -f
/etc/opensips/opensips.cfg -m 1024 -M 64
/usr/local/opensips/sbin/opensips -P /var/run/opensips.pid -f
/etc/opensips/opensips.cfg -m 1024 -M 64
Hello Guys,
Im getting a problem with out of memory on a opensips, this opensips
is running on kvm server and i have just two servers on this server, i
have enough memory, can you guys try to help me to understand the
debug on the link below ?
http://204.16.1.50/memoryfail.txt
This opensips
Hello Mike,
The pkg memory hash dump you have posted looks ok. It has some parser,
networking, pseudo-variable and timer memory allocated, and no obvious
signs of a leak.
What ERRORs do you see in the OpenSIPS logs? Are you able to extract the
similar logs which show the Memory status (shm)
Hello Liviu,
Thanks for you help.
Im receiving messages of no memmory
: WARNING:core:fm_malloc: Not enough free memory, will atempt defragmenation
Feb 25 15:13:02 sipproxy1 /usr/local/opensips/sbin/opensips[8125]:
ERROR:dialog:dlg_add_leg_info: Failed to resize legs array
Feb 25 15:13:02
It doesn't matter how many memory you have. OpenSIPS only uses what it
is configured to start with.
Restart your OpenSIPS daemon using the -m 512 -M 32 options (512MB
shared between children, 32MB private for each one). It should be more
than enough to handle 600 concurrent calls.
Best
Ok, i will try that, sorry my mistake with the subject so e thanks for
your help, on my man opensips i didint see thes -M option (just -m)
2014-02-27 12:45 GMT-05:00 Liviu Chircu li...@opensips.org:
It doesn't matter how many memory you have. OpenSIPS only uses what it is
configured to start
