<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
On 10/4/11 12:27 PM, Klaus Darilion wrote:
<blockquote cite="mid:4E8ADF9A.7020306@pernau.at" type="cite">Meanwhile
the server was restarted and the DB problems were fixed. As it is
a production server I can not reproduce anymore.
<br>
</blockquote>
<br>
So, once it started it didn't recovered, continued always with that
error? How much of shm did you configure?<br>
<br>
You can try to attach from time to time to one process (can be even
the main one to avoid blocking a sip worker) and walk through the
shm allocated chunks, in order to see if there are some unexpected
repetitions of allocation from same place in sources.<br>
<br>
I posted the gdb script for walking through pkg at some point, the
difference will be to start from the head of shm list (i.e.,
starting with
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
shm_block->first_frag instead of mem_block->first_frag):<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory#walking_through_pkg_with_gdb">http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory#walking_through_pkg_with_gdb</a><br>
<br>
You should go as much as possible to the end of the allocated list.<br>
<br>
Another option is to add shm_status() (see cfgutils module) in your
config, executed on a special request you can send with
sipsak/udp_flood/sipp . There are other options if you load the
cfg_rpc module and send some rpc commands with sercmd.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<blockquote cite="mid:4E8ADF9A.7020306@pernau.at" type="cite">
<br>
Sorry
<br>
Klaus
<br>
<br>
On 04.10.2011 12:24, Daniel-Constantin Mierla wrote:
<br>
<blockquote type="cite">Hello,
<br>
<br>
sqlops is using pkg and tm shm, so they should not be directly
related,
<br>
but maybe in the way config file works.
<br>
<br>
Can you run it again with memlog lower than debug and see where
the
<br>
allocated (not-freed) chunks were done? It should appear soon,
not
<br>
waiting for out of mem message.
<br>
<br>
If you haven't restarted, there is a way to attach with gdb and
walk
<br>
through shm allocated chunks to spot the occurences.
<br>
<br>
Cheers,
<br>
Daniel
<br>
<br>
<br>
On 10/4/11 12:08 PM, Klaus Darilion wrote:
<br>
<blockquote type="cite">Hi!
<br>
<br>
I recently had a problem with Kamailio 3.1.4 (provided Debian
packages):
<br>
<br>
I had some DB problems (missing tables). Thus, the timer
module failed
<br>
to insert the statistics (for siremis):
<br>
<br>
ERROR: db_mysql [km_dbase.c:120]: driver error on query: Table
<br>
'kamailio.statistics_tmx' doesn't exist
<br>
ERROR: <core> [db_query.c:130]: error while submitting
query
<br>
ERROR: sqlops [sql_api.c:217]: cannot do the query
<br>
<br>
<br>
This happened for some time (weeks?), other DB queries were
unaffected.
<br>
<br>
Then, suddenly Kamailio ran out of memory:
<br>
<br>
ERROR: <core> [sip_msg_clone.c:506]: ERROR:
sip_msg_cloner: cannot
<br>
allocate memory
<br>
ERROR: tm [t_lookup.c:1338]: ERROR: new_t: out of mem:
<br>
ERROR: tm [t_lookup.c:1478]: ERROR: t_newtran: new_t failed
<br>
ERROR: sl [sl_funcs.c:282]: ERROR: sl_reply_error used: I'm
terribly
<br>
sorry, server error occurred (1/SL)
<br>
<br>
<br>
It do not think it is a load problem as the server is more or
less
<br>
idle. May it be a memory leak due to wrong error handling?
<br>
<br>
Where there any fixes recently?
<br>
<br>
Thanks
<br>
Klaus
<br>
<br>
_______________________________________________
<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
<br>
</blockquote>
<br>
</blockquote>
<br>
_______________________________________________
<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
Kamailio Advanced Training, Dec 5-8, Berlin: <a class="moz-txt-link-freetext" href="http://asipto.com/u/kat">http://asipto.com/u/kat</a>
<a class="moz-txt-link-freetext" href="http://linkedin.com/in/miconda">http://linkedin.com/in/miconda</a> -- <a class="moz-txt-link-freetext" href="http://twitter.com/miconda">http://twitter.com/miconda</a></pre>
</body>
</html>