<br>Hi Daniel,<br><br>Ya at present Private memory is 1MB.<br>Shared memory is 1GB.<br>My Server is 32B.<br><br>btw Can you please let me know your suggestion how much private memory do I set?<br>As when I have set Private memory 4MB I was getting out of memory issue within 4 days.<br>
<br><br>Thanks,<br>Krunal Patel<br><br><div class="gmail_quote">On Fri, Jan 9, 2009 at 3:28 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The dump shows a lot of free memory, about half of it:<br>
Jan 7 22:25:36 ip-IP /usr/local/sbin/openser[23175]: Memory status (pkg):<br>
Jan 7 22:25:36 ip-IP /usr/local/sbin/openser[23175]: qm_status (0x816cc00):<br>
Jan 7 22:25:36 ip-IP /usr/local/sbin/openser[23175]: heap size= 1048576 Jan 7 22:25:36 ip-IP /usr/local/sbin/openser[23175]: used= 212192, used+overhead=545092, free=503484<br>
Jan 7 22:25:36 ip-IP /usr/local/sbin/openser[23175]: max used (+overhead)= 548088<br>
<br>
However, the log is with openser having 1MB of private memory. Are you sure that you increased the memory pool to 4MB?<br>
<br>
What was the size of shared memory? Is your server 32b or 64b?<br>
<br>
Cheers,<br>
Daniel<div class="Ih2E3d"><br>
<br>
<br>
On 01/08/2009 11:44 AM, Krunal Patel wrote:<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br><div class="Ih2E3d">
I have captured latest memory dump using kill -SIGUSR1 OPENSER_PID.<br>
<br>
Here is the links.<br>
<br>
Link1 -- <a href="http://pastebin.com/m296598e2" target="_blank">http://pastebin.com/m296598e2</a><br>
<br>
Link2 -- <a href="http://pastebin.com/m9963b7c" target="_blank">http://pastebin.com/m9963b7c</a><br>
<br>
Link3 -- <a href="http://pastebin.com/m7438e72a" target="_blank">http://pastebin.com/m7438e72a</a><br>
<br>
<br>
As well as I have stopped openser & captured memory dump for the same.<br>
<br>
Please find attached shutdown.tar.gz.<br>
<br>
<br>
Please suggest me if there is any resolution.<br>
<br>
<br>
Thanks in advance,<br>
<br>
<br>
Krunal Patel<br>
<br></div><div><div></div><div class="Wj3C7c">
On Wed, Jan 7, 2009 at 2:31 PM, Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>> wrote:<br>
<br>
Hello,<br>
<br>
<br>
On 01/07/09 07:26, Krunal Patel wrote:<br>
<br>
Hi,<br>
<br>
Was the signal SIGHUP or SIGUSR1?<br>
<br>
*++ The signal was SIGHUP1.*<br>
<br>
SIGHUP is 1, so i am confused whether there was a mistake in<br>
typing as there should be SIGUSR1.<br>
<br>
<br>
A cause can be insufficient private memory, as it seems you<br>
have a quite big config file, with lot of variables. In this<br>
case, the private memory used by config is relevant,<br>
considering that private memory per process is 1MB, for<br>
runtime is not that much left. Try to recompile openser with<br>
2MB of private memory and see if the situation occurs again.<br>
<br>
*++ I had increased private memory to 4MB eventhough the<br>
situation occurred after 4 days of restarting openser.<br>
*<br>
<br>
*++ Have you find any memory leak in the memory dump?*<br>
<br>
No, that log does not show a leak - there are memory chunks<br>
allocated at startup not at runtime. Please do again the tests and<br>
be sure you follow:<br>
- send SIGUSR1 to the process that log memory error messages, not<br>
to the main process or other processes<br>
- grab that log and send it, then you can stop openser (you will<br>
get another set of memory dump logs)<br>
<br>
Thanks,<br>
Daniel<br>
<br>
<br>
Thanks for you support,<br>
<br>
--<br>
Krunal Patel<br>
<br>
<br>
On Wed, Jan 7, 2009 at 4:35 AM, Daniel-Constantin Mierla<br>
<<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>><br></div></div><div class="Ih2E3d">
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>>> wrote:<br>
<br>
Hello,<br>
<br>
<br></div><div class="Ih2E3d">
On 01/01/09 10:42, Krunal Patel wrote:<br>
<br>
Hi,<br>
<br>
Here is the memory dump captured using kill -SIGHUP1<br>
OPENSERPID.<br>
Please help me out to interpret it.<br>
<br>
<a href="http://pastebin.com/m39a6c204" target="_blank">http://pastebin.com/m39a6c204</a><br>
<a href="http://pastebin.com/m518f27b7" target="_blank">http://pastebin.com/m518f27b7</a><br>
<br>
looks like all memory chunks were allocated at start up time.<br>
<br>
Was the signal SIGHUP or SIGUSR1?<br>
<br>
A cause can be insufficient private memory, as it seems you<br>
have a<br>
quite big config file, with lot of variables. In this case, the<br>
private memory used by config is relevant, considering that<br>
private memory per process is 1MB, for runtime is not that much<br>
left. Try to recompile openser with 2MB of private memory<br>
and see<br>
if the situation occurs again.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<br>
Thanks<br>
Krunal Patel<br>
<br>
<br>
<br>
On Wed, Dec 31, 2008 at 6:26 PM, Daniel-Constantin Mierla<br>
<<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>><br>
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>><br></div><div class="Ih2E3d">
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>><br>
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>>>> wrote:<br>
<br>
Hello,<br>
<br></div><div><div></div><div class="Wj3C7c">
there is something wrong in your side the DBG_QM_MALLOG<br>
does not<br>
show up in the flags. Here is mine:<br>
<br>
# openser -V<br>
<br>
version: openser 1.2.3-notls (i386/linux)<br>
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE,<br>
USE_MCAST,<br>
SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC,<br>
FAST_LOCK-ADAPTIVE_WAIT<br>
<br>
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144,<br>
MAX_LISTEN<br>
16, MAX_URI_SIZE 1024, BUF_SIZE 65535<br>
poll method support: poll, epoll_lt, epoll_et, sigio_rt,<br>
select.<br>
svnrevision: 2:5379M<br>
<br>
After PKG_MALLOC, I have DBG_QM_MALLOC. Double check<br>
your<br>
Makefile.defs.<br>
<br>
Daniel<br>
<br>
<br>
<br>
On 12/31/08 14:50, Krunal Patel wrote:<br>
<br>
Hi<br>
<br>
Here is the output:<br>
version: openser 1.2.3-notls (i386/linux)<br>
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE,<br>
USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC,<br>
FAST_LOCK-ADAPTIVE_WAIT<br>
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE<br>
262144,<br>
MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535<br>
poll method support: poll, epoll_lt, epoll_et,<br>
sigio_rt, select.<br>
svnrevision: unknown<br>
@(#) $Id: main.c 3173 2007-11-20 08:26:35Z<br>
bogdan_iancu $<br>
main.c compiled on 02:27:47 Dec 24 2008 with gcc<br>
4.0.2<br>
<br>
Thanks,<br>
Krunal Patel<br>
<br>
</div></div></blockquote><div><div></div><div class="Wj3C7c">
-- <br>
Daniel-Constantin Mierla<br>
<a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a><br>
<br>
</div></div></blockquote></div><br>