THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#95 - SipTrace causing Kamailio not to start
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=95
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#95 - SipTrace causing Kamailio not to start
User who did this - Daniel-Constantin Mierla (miconda)
----------
This was fixed some time ago - the cause was an improper initialization of sl API bind structure for callback registration. If it still does not work for 3.1.1, reopen.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=95#comment142
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.
Daniel-Constantin Mierla has taken ownership of the following task:
FS#95 - SipTrace causing Kamailio not to start
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=95
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#106 - Error db_berkeley
User who did this - Daniel-Constantin Mierla (miconda)
----------
The internal module name was db_bdb which resulted in db url requiring to start with "bdb://...". I did a fix on master, GIT#610126b7, so now it matches the path of the module directory name. It is only for master branch, if you can try it and report back will be great. Anyhow I will backport in the next days to 3.x branches. Thanks for reporting.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=106#comment141
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.
A new Flyspray task has been opened. Details are below.
User who did this - stas (_stas)
Attached to Project - sip-router
Summary - Error db_berkeley
Task Type - Bug Report
Category - usrloc (k)
Status - Assigned
Assigned To - Daniel-Constantin Mierla
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - CONFIG:
mpath="/usr/local/lib/kamailio/modules_k/:/usr/local/lib/kamailio/modules/"
loadmodule "db_berkeley.so"
loadmodule "tm.so"
loadmodule "sl.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
modparam("usrloc", "db_mode", 2)
modparam("usrloc", "db_url", "berkeley:///usr/local/etc/kamailio/db" )
ERROR:
0(4395) DEBUG: <core> [sr_module.c:871]: DEBUG: init_mod: usrloc
0(4395) INFO: usrloc [hslot.c:53]: locks array size 512
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_bind_api> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_bind_api> in module <db_berkeley> not found
0(4395) DEBUG: <core> [db.c:210]: using export interface to bind db_berkeley
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_use_table> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_use_table> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_init> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_init> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_close> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_close> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_query> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_query> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_fetch_result> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_fetch_result> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_raw_query> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_raw_query> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_free_result> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_free_result> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_insert> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_insert> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_delete> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_delete> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_update> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_update> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_replace> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_replace> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_last_inserted_id> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_last_inserted_id> in module <db_berkeley> not found
0(4395) DEBUG: <core> [sr_module.c:516]: find_export_record: <db_insert_update> not found
0(4395) DEBUG: <core> [sr_module.c:569]: find_mod_export: <db_insert_update> in module <db_berkeley> not found
0(4395) ERROR: <core> [db.c:79]: module db_berkeley does not export db_use_table function
0(4395) ERROR: usrloc [ul_mod.c:290]: failed to bind database module
0(4395) ERROR: <core> [sr_module.c:874]: init_mod(): Error while initializing module usrloc
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=106
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.
A user has added themself to the list of users assigned to this task.
FS#106 - Error db_berkeley
User who did this - stas (_stas)
http://sip-router.org/tracker/index.php?do=details&task_id=106
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.
is it ok if i change dp_translate to return -2 instead of -1 when dpid
that is used for the translation does not exist? that way, the script
could know to try the translation with a possible other dpid.
-- juha