THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Josh (JoshE)
Attached to Project - sip-router
Summary - mtree mt_summary display incorrectly, or memory leak?
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - I am running latest production Kamailio, and seeing weird behavior with multiple mtree's running.
Start the service and run a:
[root@nproxy-1:/usr/local/etc/kamailio#]kamctl mi mt_summary
MT:: TNAME=fc_did TTYPE=0 MEMSIZE=3486296 NRNODES=14398 NRITEMS=6973
MT:: TNAME=fc_tenant TTYPE=0 MEMSIZE=3542806 NRNODES=14398 NRITEMS=6973
Then run a:
kamctl mi mt_reload
[root@nyc-proxy-1:/usr/local/etc/kamailio#]kamctl mi mt_summary
MT:: TNAME=fc_did TTYPE=0 MEMSIZE=6972592 NRNODES=28796 NRITEMS=13946
MT:: TNAME=fc_tenant TTYPE=0 MEMSIZE=7085612 NRNODES=28796 NRITEMS=13946
Then run another"
kamctl mi mt_reload
root@nyc-proxy-1:/usr/local/etc/kamailio#]kamctl mi mt_summary
MT:: TNAME=fc_did TTYPE=0 MEMSIZE=10458888 NRNODES=43194 NRITEMS=20919
MT:: TNAME=fc_tenant TTYPE=0 MEMSIZE=10628418 NRNODES=43194 NRITEMS=20919
I am not sure if I'm seeing leaking behavior here, or something else is going on entirely.
When I do a grep through the actual mtree list, like: kamctl mi mt_list | grep "fc_tenant" | wc -l ... I see that the actual count of mtree items is the same.
Is this just a bug in presentation, or is something else going on here I should be concerned about?
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=398
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#249 - default_expires_range should be applied to all expire times, not only to default
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Implemented
Additional comments about closing: Now in master branch.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=249
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#353 - carrierroute not loading with kamailio 4.0.x
User who did this - Daniel-Constantin Mierla (miconda)
----------
There was a patch sent some time ago not to depend on libconfuse:
- http://lists.sip-router.org/pipermail/sr-dev/2013-November/022030.html
I pinged to get some updates about its status.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=353#comment1307
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi all,
This has been in the back of my head from some time now. Libconfuse is a
small project not distributed with major distros and unmaintained for 3.5
years now. As it is only used for reading of a simple cfg file, I want to
write a simple parser that does the job(I do not want external deps ... see
below why)
Benefits: we can now pack carrierroute with the common used modules (as it
will not have any external dependencies) and also will remove a lot of
problems seen on the list regarding linkage of libconfuse.
Any thoughts?
Marius
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#356 - kamctl does not work properly for sqlite
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Implemented
Additional comments about closing: No follow up after the patch, reopen if still an issue.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=356
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.