Hello,
On 01/01/09 10:42, Krunal Patel wrote:
Hi,looks like all memory chunks were allocated at start up time.
Here is the memory dump captured using kill -SIGHUP1 OPENSERPID.
Please help me out to interpret it.
http://pastebin.com/m39a6c204
http://pastebin.com/m518f27b7
Was the signal SIGHUP or SIGUSR1?
A cause can be insufficient private memory, as it seems you have a quite big config file, with lot of variables. In this case, the private memory used by config is relevant, considering that private memory per process is 1MB, for runtime is not that much left. Try to recompile openser with 2MB of private memory and see if the situation occurs again.
Cheers,
Daniel
Thanks
Krunal Patel
On Wed, Dec 31, 2008 at 6:26 PM, Daniel-Constantin Mierla <miconda@gmail.com <mailto:miconda@gmail.com>> wrote:
Hello,
there is something wrong in your side the DBG_QM_MALLOG does not
show up in the flags. Here is mine:
# openser -V
version: openser 1.2.3-notls (i386/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST,
SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN
16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
svnrevision: 2:5379M
After PKG_MALLOC, I have DBG_QM_MALLOC. Double check your
Makefile.defs.
Daniel
On 12/31/08 14:50, Krunal Patel wrote:
Hi
Here is the output:
version: openser 1.2.3-notls (i386/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE,
USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144,
MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
svnrevision: unknown
@(#) $Id: main.c 3173 2007-11-20 08:26:35Z bogdan_iancu $
main.c compiled on 02:27:47 Dec 24 2008 with gcc 4.0.2
Thanks,
Krunal Patel
On Wed, Dec 31, 2008 at 6:17 PM, Daniel-Constantin Mierla
<miconda@gmail.com <mailto:miconda@gmail.com><mailto:miconda@gmail.com <mailto:miconda@gmail.com>>> wrote:
Hello,
send the output of "openser -V".
Daniel
On 12/31/08 14:36, Krunal Patel wrote:
Hi
Yes I have recompiled/reinstalled openser with
-DDBG_QM_MALLOC.
Thanks,
Krunal Patel
On Wed, Dec 31, 2008 at 6:03 PM, Daniel-Constantin Mierla
<miconda@gmail.com <mailto:miconda@gmail.com>
<mailto:miconda@gmail.com <mailto:miconda@gmail.com>><mailto:miconda@gmail.com <mailto:miconda@gmail.com>
<mailto:miconda@gmail.com <mailto:miconda@gmail.com>>>> wrote:
Hello,
have you recompiled/reinstalled openser with
-DDBG_QM_MALLOC?
The log does not show it. There should be messages like:
alloc'd from file.c: function(line)
Cheers,
Daniel
On 12/31/08 13:55, Krunal Patel wrote:
Hi,
I have captured memory dump using kill -SIGUSR1
OPENSER-PID.
Here is the link for the dump.
http://pastebin.com/m1e8fcd01
As well as I have stopped openser & captured
memory Dump.
Here is the link for the same.
http://pastebin.com/m2edde70
Would you please help me to interpret the logs &
find out
whether memory leak does exist or not?
Thanks in advance!!
--
Krunal Patel
On Sun, Dec 28, 2008 at 3:06 PM,
Daniel-Constantin Mierla
<miconda@gmail.com <mailto:miconda@gmail.com>
<mailto:miconda@gmail.com <mailto:miconda@gmail.com>>
<mailto:miconda@gmail.com <mailto:miconda@gmail.com>
<mailto:miconda@gmail.com <mailto:miconda@gmail.com>>>
<mailto:miconda@gmail.com
<mailto:miconda@gmail.com> <mailto:miconda@gmail.com
<mailto:miconda@gmail.com>>
<mailto:miconda@gmail.com <mailto:miconda@gmail.com>
<mailto:miconda@gmail.com <mailto:miconda@gmail.com>>>>> wrote:
Hello,
On 12/23/08 16:20, Krunal Patel wrote:
Hi,
I am using openser 1.2.3.
1.2.3 is rather old. Can you update to a
newer version?
kamailio
1.4.3 for example...
I have increased PKG_MEM_POOL_SIZE to 4MB.
Openser worked properly for 4 days since last
restart.
I found get_hdr_field: out of memory for all
messages.
This might be a side effect, the leak can be in
other parts.
Please follow the guidelines described here:
http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory
Grab the log messages and put them somewhere to
download,
if they
are too big. The log will help to identify
where the
issue is.
Note that out of memory messages can occur
due to heavy
traffic,
with no leak there -- case when increasing
the private
memory size
is the solution.
Happy holidays!
Daniel
I did openser restart & the issue is
fixed now.
Is anybody there who have faced the same
issue?
Thanks in advance!!
--
Krunal patel
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>>>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>>>>
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
-- Daniel-Constantin
Mierla
http://www.asipto.com
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>
<mailto:Users@lists.kamailio.org
<mailto:Users@lists.kamailio.org>>>
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
-- Daniel-Constantin Mierla
http://www.asipto.com