Hello Mike,
Could you come up with an estimate for the rows of the biggest MySQL
tables (e.g. dr_rules, dialplan, etc.)? Using this information, we can
estimate the minimum amount of RAM we need. 400 cc should consume like
10MB of shared memory, so the problem is clearly somewhere else.
If big tables are not the problem, then we're most likely talking about
a leak. Are you able to manually recompile and install OpenSIPS? If yes,
I will ask you to set up a debug version. You can follow the
instructions at [1].
1: http://www.opensips.org/Documentation/TroubleShooting-OutOfMem
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 03/03/2014 05:41 PM, Mike Tesliuk wrote:
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 thing.
i have the system working now from two days, let see what happen
2014-02-28 15:24 GMT-05:00 Mike Tesliuk <m...@ultra.net.br
<mailto:m...@ultra.net.br>>:
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
/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
/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
/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
/usr/local/opensips/sbin/opensips -P /var/run/opensips.pid -f
/etc/opensips/opensips.cfg -m 1024 -M 64
Just to remember i have 8 GB Ram for this server
Feb 28 15:35:08 sipproxy1
/usr/local/opensips/sbin/opensips[27539]: Grupo de gateways: 1
Feb 28 15:35:08 sipproxy1
/usr/local/opensips/sbin/opensips[27539]:
ERROR:dialog:build_new_dlg: no more shm mem (300)
Feb 28 15:35:08 sipproxy1
/usr/local/opensips/sbin/opensips[27539]:
ERROR:dialog:dlg_create_dialog: failed to create new dialog
Feb 28 15:35:08 sipproxy1
/usr/local/opensips/sbin/opensips[27539]:
ERROR:load_balancer:do_load_balance: failed to create dialog
The amount of calls was like 400 calls when i got the message.
As i say before, im running this host on a kvm server, this is the
first server that i put in prodcution using virtualization, i have
real servers running without problem , the server run fine from
yeasterday to now
Below the link to the script, i double check the script and dont
see anything that can generate this error
http://204.16.1.50/opensips.cfg
I will appreciate your help.
Thanks
2014-02-27 12:52 GMT-05:00 Mike Tesliuk <m...@ultra.net.br
<mailto:m...@ultra.net.br>>:
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
<mailto:li...@opensips.org>>:
> 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 regards,
>
> Liviu Chircu
> OpenSIPS Developer
> http://www.opensips-solutions.com
>
> On 02/27/2014 07:40 PM, Mike Tesliuk wrote:
>>
>> 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 sipproxy1
/usr/local/opensips/sbin/opensips[8125]:
>> ERROR:dialog:init_leg_info: dlg_add_leg_info failed
>> Feb 25 15:13:02 sipproxy1
/usr/local/opensips/sbin/opensips[8125]:
>> ERROR:dialog:dlg_create_dialog: could not add further info
to the
>> dialog
>> Feb 25 15:13:02 sipproxy1
/usr/local/opensips/sbin/opensips[8125]:
>> ERROR:load_balancer:do_load_balance: failed to create dialog
>>
>>
>> The server is virtual host (kvm) with 8 GB dedicated memory
, i got
>> something like 600 simultaneos calls
>>
>>
>> The memory status error that you ask is on the link below
>>
>>
>> http://204.16.1.50/memorystatus-shm.txt
>>
>>
>> and i get some ERROR messages on the next link
>>
>> http://204.16.1.50/process-errors.txt
>>
>> _______________________________________________
>> Devel mailing list
>> Devel@lists.opensips.org <mailto:Devel@lists.opensips.org>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>
>
>
> _______________________________________________
> Devel mailing list
> Devel@lists.opensips.org <mailto:Devel@lists.opensips.org>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
