Am Montag, 17. Juni 2013, 07:43:16 schrieb Dragos Oancea:
So far the module performed pretty good for us.
But there might be a problem, when I shut down Kamailio I see this in the
logs :
ERROR: memcached [memcached.c:255]: mod_destroy(): memory manager callbacks
not removed, returned
Hi Henning,
Good work. I just compiled, did a few tests and let it run on a box. It's
working fine.
Just a question , the memory manager was the `system` one before your latest
patch, right ? aka dlmalloc. ?
Since we're using the module and we plan to go to production with it very soon,
I
Am Dienstag, 2. Juli 2013, 07:51:32 schrieb Dragos Oancea:
Good work. I just compiled, did a few tests and let it run on a box. It's
working fine. Just a question , the memory manager was the `system` one
before your latest patch, right ? aka dlmalloc. ?
Since we're using the module and we
Hi Dragos,
I don't think it will make a difference, but do you still see the problem
if you build/run Kamailio completely from master, instead of just copying
across the compiled memcache module?
Cheers,
Charles
On 17 June 2013 15:43, Dragos Oancea droan...@yahoo.com wrote:
Hi Henning
Hi Charles,
Yes, when I build and run it completely from master, I have the same issue.
So I get this when I shut it down with `killall kamailio`.
This time I run it with log_stderror=yes , so it prints alot of debugging
messages - it seems it tries to free() un-allocated memory :
Am Dienstag, 18. Juni 2013, 08:24:49 schrieb Dragos Oancea:
Yes, when I build and run it completely from master, I have the same issue.
So I get this when I shut it down with `killall kamailio`.
This time I run it with log_stderror=yes , so it prints alot of debugging
messages - it seems
Hi Henning Charles,
So far the module performed pretty good for us.
But there might be a problem, when I shut down Kamailio I see this in the logs :
ERROR: memcached [memcached.c:255]: mod_destroy(): memory manager callbacks not
removed, returned INVALID ARGUMENTS but continue anyway
It