Hi,<br><br>The core dumped but before that happen i see this in messages:<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: Memory status (pkg):<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: qm_status (0x67b560):<br>
Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: heap size= 2097152<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: used= 460784, used+overhead=615648, free=1481504<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: max used (+overhead)= 615648<br>
Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: dumping all alloc'ed. fragments:<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 0. N address=0x685da0 frag=0x685d90 size=48 used=1<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 1. N address=0x685df0 frag=0x685de0 size=48 used=1<br>
Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 2. N address=0x685e40 frag=0x685e30 size=144 used=1<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 3. N address=0x685ef0 frag=0x685ee0 size=144 used=1<br>
Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 4. N address=0x685fa0 frag=0x685f90 size=144 used=1<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 5. N address=0x686050 frag=0x686040 size=144 used=1<br>
Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 6. N address=0x686100 frag=0x6860f0 size=144 used=1<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 7. N address=0x6861b0 frag=0x6861a0 size=144 used=1<br>
Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 8. N address=0x686260 frag=0x686250 size=144 used=1<br>Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 9. N address=0x686310 frag=0x686300 size=144 used=1<br>
Sep 18 07:12:29 sips /usr/local/sbin/opensips[8221]: 10. N address=0x6863c0 frag=0x6863b0 size=224 used=1<br><br><br>Is that what you need to see? I can get the entire file, I have no clue what it's saying really :)<br>
<br>This was with #define PKG_MEM_POOL_SIZE 1024*1024*2 <br><br>Thanks<br><br><div class="gmail_quote">On Fri, Sep 18, 2009 at 1:01 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</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;">Hi Ron,<br>
<br>
your mem error are referring to pkg or shm too ?<br>
<br>
If increasing the memory (note that pkg mem is configured at compile<br>
time, so after changing the PKG_MEM_POOL_SIZE, you need to recompile the<br>
whole stuff) did not hep at all, you should try to enable the memory<br>
debugger - <a href="http://www.opensips.org/Resources/DocsTsMem" target="_blank">http://www.opensips.org/Resources/DocsTsMem</a>. After getting<br>
the out of memory error again, do not stop opensips, by send a USR1<br>
signal the the proc reporting the mem error (kill -SIGUSR1 pid) -> get<br>
the pkg mem dump and send it to me.<br>
<br>
Thanks and regards,<br>
Bogdan<br>
<div class="im"><br>
Ron McCarthy wrote:<br>
> I upgraded to 6147 and still same issue, I also tried making the<br>
> memory bigger, same issue.<br>
><br>
> I do get a core dump, can i debug that somehow?<br>
><br>
> Thanks<br>
><br>
> On Thu, Sep 17, 2009 at 4:16 AM, andrei dragus <<a href="mailto:andreidragus@yahoo.com">andreidragus@yahoo.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:andreidragus@yahoo.com">andreidragus@yahoo.com</a>>> wrote:<br>
><br>
> There was a memory leak in the dialog module.<br>
><br>
> If you were using this module then this was probably the cause.<br>
> It was fixed starting with revision 6147.<br>
><br>
> Please update and try again, and report if you still have issues.<br>
><br>
> Andrei.<br>
><br>
> --- On Wed, 9/16/09, Brett Nemeroff <<a href="mailto:brett@nemeroff.com">brett@nemeroff.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:brett@nemeroff.com">brett@nemeroff.com</a>>> wrote:<br>
><br>
><br>
> > Look in config.h for:#define<br>
> > PKG_MEM_POOL_SIZE 1024*1024<br>
> > and try changing that to:#define<br>
> > PKG_MEM_POOL_SIZE 1024*1024*2<br>
> ><br>
> > On Wed, Sep 16, 2009 at 5:34 PM,<br>
</div>> > Ron McCarthy <<a href="mailto:ronmccar@gmail.com">ronmccar@gmail.com</a> <mailto:<a href="mailto:ronmccar@gmail.com">ronmccar@gmail.com</a>>><br>
<div><div></div><div class="h5">> > wrote:<br>
> ><br>
> ><br>
> > Hi List,<br>
> ><br>
> > I just upgraded to the latest SVN relase and after a few<br>
> > thousand calls I start getting:<br>
> ><br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:core:get_hdr_field: out of pkg memory<br>
> ><br>
> ><br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:tm:t_check: reply cannot be parsed<br>
> ><br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:core:parse_from_header: out of pkg_memory<br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:dialog:pre_match_parse: failed to get From header<br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:core:parse_from_header: out of pkg_memory<br>
> ><br>
> ><br>
> ><br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:tm:parse_dlg: From broken<br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:tm:matching_3261: dlg parsing failed<br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:core:build_req_buf_from_sip_req: out of pkg memory<br>
> ><br>
> ><br>
> ><br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:core:forward_request: building req buf failed<br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:core:get_hdr_field: out of pkg memory<br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:tm:t_check: reply cannot be parsed<br>
> ><br>
> ><br>
> ><br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:core:get_hdr_field: out of pkg memory<br>
> > Sep 16 15:25:37 sips /usr/local/sbin/opensips[2271]:<br>
> > ERROR:tm:t_check: reply cannot be parsed<br>
> ><br>
> > Ive got it using -m 2048 at startup, from what I can tell<br>
> > never more then 1 gig of RAM get's used. This is at<br>
> > around 70CPS on a single dual core Xeon, CPU is at 90%+<br>
> > idle. Anything else I can tweek, or this a bug/memory leak<br>
> > perhaps?<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > We are using quit a few memcache_fetch calls for LCR and<br>
> > other purposes, about 12 or so per call.<br>
> ><br>
> > It's also dumping a core, will that help me?<br>
> ><br>
> > Thanks!<br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> ><br>
><br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>