<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello Tito,<br>
<br>
Firstly, note that OpenSIPS will not use the entire available RAM
on the box, but rather a predefined value ("-m" parameter, e.g.
"-m 128" for a 128MB preallocated memory pool).<br>
<br>
Does your scenario not work at all or does OpenSIPS start
misbehaving after some time? The log messages tell us that
OpenSIPS has run out of memory and is unable to properly process
incoming traffic.<br>
<br>
Best regards,<br>
<pre class="moz-signature" cols="72">Liviu Chircu
OpenSIPS Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
On 11/20/2013 07:14 AM, Tito Cumpen wrote:<br>
</div>
<blockquote
cite="mid:CANZPVB5-nNK4m2Daj8ZHV75V+G9WqP37XGh+EO6qMgBZktJgyg@mail.gmail.com"
type="cite">
<div dir="ltr">
<p class="">Group,</p>
<p class=""><br>
</p>
<p class=""><br>
</p>
<p class="">I am relaying my invites and loose routes to a
sipservlet using the seas module and wesip. I am noticing that
when acks are sent to opensips it is directed to relay those
acks to wesip and then back out to the recipient it fails to
do so. Consequently I see this message being generated and
eventually a memory problem. I am not seeing the message
traverse through seas into the my servlet. Take note this is a
single call on a server with more than sufficient ram. I am
using version opensips-1.7.2-tls</p>
<p class=""><br>
Thanks,<br>
Tito </p>
<p class=""><br>
</p>
<p class=""><br>
</p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2038]:
here is a loose route </p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2038]:
This has a totag </p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2038]:
ack received by opensips sending to app server!</p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2038]:
received at route 1 sending to seas</p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2038]:
ERROR:seas:create_as_event_t: no transaction provided...</p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2038]:
ERROR:seas:w_as_relay_t: unable to create event code</p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2039]:
here is a lose route </p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2039]:
This has a totag </p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2039]:
received at route 1 sending to seas</p>
<p class="">Nov 19 20:21:08 mediaproxy2 /sbin/opensips[2026]:
<a class="moz-txt-link-freetext" href="INFO:seas:dispatcher_main_loop">INFO:seas:dispatcher_main_loop</a>: polling [2 ServSock] [1 pipe]
[1 App Servers] [0 Uncomplete AS]</p>
<p class="">Nov 19 20:21:09 mediaproxy2 /sbin/opensips[2041]:
WARNING:core:fm_malloc: Not enough free memory, will atempt
defragmenation</p>
<p class="">Nov 19 20:21:09 mediaproxy2 /sbin/opensips[2041]:
ERROR:tm:sip_msg_cloner: no more share memory</p>
<p class="">Nov 19 20:21:09 mediaproxy2 /sbin/opensips[2041]:
ERROR:tm:new_t: out of mem</p>
<p class="">Nov 19 20:21:09 mediaproxy2 /sbin/opensips[2041]:
ERROR:tm:t_newtran: new_t failed</p>
<p class="">Nov 19 20:21:09 mediaproxy2 /sbin/opensips[2026]:
<a class="moz-txt-link-freetext" href="INFO:seas:dispatcher_main_loop">INFO:seas:dispatcher_main_loop</a>: polling [2 ServSock] [1 pipe]
[1 App Servers] [0 Uncomplete AS]</p>
<p class="">Nov 19 20:21:11 mediaproxy2 /sbin/opensips[2026]:
<a class="moz-txt-link-freetext" href="INFO:seas:dispatcher_main_loop">INFO:seas:dispatcher_main_loop</a>: polling [2 ServSock] [1 pipe]
[1 App Servers] [0 Uncomplete AS]</p>
<p class="">Nov 19 20:21:17 mediaproxy2 /sbin/opensips[2038]:
here is a lose route </p>
<p class="">Nov 19 20:21:17 mediaproxy2 /sbin/opensips[2038]:
This has a totag </p>
<p class="">Nov 19 20:21:17 mediaproxy2 /sbin/opensips[2038]:
received at route 1 sending to seas</p>
<p class="">Nov 19 20:21:17 mediaproxy2 /sbin/opensips[2026]:
<a class="moz-txt-link-freetext" href="INFO:seas:dispatcher_main_loop">INFO:seas:dispatcher_main_loop</a>: polling [2 ServSock] [1 pipe]
[1 App Servers] [0 Uncomplete AS]</p>
<p class="">Nov 19 20:21:17 mediaproxy2 /sbin/opensips[2026]:
<a class="moz-txt-link-freetext" href="INFO:seas:dispatcher_main_loop">INFO:seas:dispatcher_main_loop</a>: polling [2 ServSock] [1 pipe]
[1 App Servers] [0 Uncomplete AS]</p>
<p class="">Nov 19 20:21:38 mediaproxy2 /sbin/opensips[2026]:
<a class="moz-txt-link-freetext" href="INFO:seas:dispatcher_main_loop">INFO:seas:dispatcher_main_loop</a>: polling [2 ServSock] [1 pipe]
[1 App Servers] [0 Uncomplete AS]</p>
<p class="">Nov 19 20:21:38 mediaproxy2 /sbin/opensips[2031]:
WARNING:core:fm_malloc: Not enough free memory, will atempt
defragmenation</p>
<p class="">Nov 19 20:21:38 mediaproxy2 /sbin/opensips[2031]:
ERROR:tm:relay_reply: no more share memory</p>
<p class="">Nov 19 20:21:38 mediaproxy2 /sbin/opensips[2031]:
WARNING:core:fm_malloc: Not enough free memory, will atempt
defragmenation</p>
<p class="">Nov 19 20:21:38 mediaproxy2 /sbin/opensips[2031]:
ERROR:tm:_reply_light: failed to allocate shmem buffer</p>
<p class="">Nov 19 20:21:38 mediaproxy2 /sbin/opensips[2031]:
WARNING:core:fm_malloc: Not enough free memory, will atempt
defragmenation</p>
<p class="">Nov 19 20:21:38 mediaproxy2 /sbin/opensips[2031]:
ERROR:tm:relay_reply: no more share memory</p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>