Hello Michele,
Not sure if there is any relation between the 2 events (the E-tag and
OOM). Do troubleshoot the OOM issue, see
http://www.opensips.org/Documentation/TroubleShooting-OutOfMem - you
will have to compile in the memory debugger, so , when an OOM event
occurs, you can get a memory dump to check if it is a leak or a simple
overloading of memory (simply not enough mem for your load).
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit May 2017 Amsterdam
http://www.opensips.org/events/Summit-2017Amsterdam.html
On 03/16/2017 10:05 AM, Michele Pinassi wrote:
Opensips 1.11.9-notls on a Debian 8.7 x64, with more that 700 phones
registered.
Sometimes, almost twice a week, i got a lot of:
/usr/sbin/opensips[1585]: ERROR:presence:update_presentity: No E_Tag
match [a.1489409482.1585.24993.147]
/usr/sbin/opensips[1586]: ERROR:presence:update_presentity: No E_Tag
match [a.1489409482.1584.24871.146]
/usr/sbin/opensips[1584]: ERROR:presence:update_presentity: No E_Tag
match [a.1489409482.1586.24799.146]
that, after few hours, results in a:
/usr/sbin/opensips[1585]: ERROR:tm:new_t: out of mem
/usr/sbin/opensips[1584]: WARNING:core:fm_malloc: Not enough free
memory, will attempt defragmentation
/usr/sbin/opensips[1585]: ERROR:tm:t_newtran: new_t failed
/usr/sbin/opensips[1584]: ERROR:tm:new_t: out of mem
of course, users were not happy :-) so i need suggestions how to solve
the problem or how to avoid that error cause opensips to eat all the
memory available...
Thanks, Michele
_______________________________________________
Users mailing list
[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
