Hi Brett, in your case it was a temporary overload of the memory (due the looping) and not a leak, right ? - btw, it such cases, reducing the maxfwd value will help in reducing the number of loops. Also some script logic is good (to detect loops based on src ip, ruri, etc)
Regards, Bogdan Brett Nemeroff wrote: > For what it's worth, I have also experienced out of memory error > occurring from large quantities of routing loops that I hadn't > detected. The memory loss was so bad that opensips stopped processing > calls (but never seemed to have crashed). > > Memory errors went away when I resolved the route loops. :) > -Brett > > > On Thu, Apr 29, 2010 at 7:22 PM, Julien Chavanton <[email protected] > <mailto:[email protected]>> wrote: > > > I found is a routing loop with another equipement, I was able to > find some trace, this is not an Opensips related problem anymore. > > > ------------------------------------------------------------------------ > *From:* [email protected] > <mailto:[email protected]> on behalf of Julien > Chavanton > *Sent:* Thu 29/04/2010 11:22 PM > *To:* OpenSIPS users mailling list; [email protected] > <mailto:[email protected]> > *Subject:* Re: [OpenSIPS-Users] tm - module out of memory > > > I have to diagnostic this system further, as before facing > a memory shortage, there is a huge bunch of > ERROR:tm:t_check: reply cannot be parsed > > > Apr 29 19:16:58 osip /usr/local/sbin/opensips[20101]: ***BRANCH > ROUTE** > Apr 29 19:16:58 osip /usr/local/sbin/opensips[20104]: ***REPLY > ROUTE - td[10.1.16.50]** > Apr 29 19:16:58 osip /usr/local/sbin/opensips[20103]: > ERROR:tm:t_check: reply cannot be parsed > Apr 29 19:16:58 osip /usr/local/sbin/opensips[20101]: ***HOST > ROUTED *** > > ------------------------------------------------------------------------ > *From:* [email protected] > <mailto:[email protected]> on behalf of Julien > Chavanton > *Sent:* Thu 29/04/2010 8:27 PM > *To:* [email protected] <mailto:[email protected]> > *Subject:* [OpenSIPS-Users] tm - module out of memory > > tm module went out of memory, we did face other problems with a > non compliant SIP device, so this could well be a side effect of it. > > Any recommendation on tm memory usage ? > > opensips log > > ------------------------------------------------------------------------------------------- > > Apr 29 19:17:33 osip /usr/local/sbin/opensips[20101]: > ERROR:tm:new_t: out of mem > Apr 29 19:17:33 osip /usr/local/sbin/opensips[20101]: > ERROR:tm:t_newtran: new_t failed > > > > > _______________________________________________ > Users mailing list > [email protected] <mailto:[email protected]> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
