Olle,

Here is the gdb debug trace

(gdb) backtrace
#0 0x00007ff76e13bddc in db_cluster_delete (_h=0x7ff7716f2428, _k=0x0, _o=0x0, _v=0x0, _n=0) at dbcl_api.c:390 #1 0x00007ff769d0193c in load_dialog_info_from_db (dlg_hash_size=4096, fetch_num_rows=200) at dlg_db_handler.c:462 #2 0x00007ff769cfcb9a in init_dlg_db (db_url=0x7ff769f58a90 <db_url>, dlg_hash_size=4096, db_update_period=60, fetch_num_rows=200) at dlg_db_handler.c:167
#3  0x00007ff769d1f15c in mod_init () at dialog.c:696
#4  0x000000000053a68d in init_mod (m=0x7ff7715af7b0) at sr_module.c:966
#5  0x000000000053a99a in init_modules () at sr_module.c:995
#6 0x0000000000531151 in main (argc=1, argv=0x7fffd2fad8f8) at main.c:2519
(gdb)


Jan


Olle E. Johansson schreef op 2015-03-09 17:41:
On 09 Mar 2015, at 17:16, Jan Hazenberg <je...@cyberchaos.nl> wrote:

Hello,

I have a issue on kamailio 4.2.3 when using the db_cluster module. I have the following config:

#!define DBURL "cluster://cls1"

# ----- db_cluster params -----
modparam("db_cluster", "connection",
            "con1=>mysql://kamailio:kamailiorw@10.121.0.120/kamailio")
modparam("db_cluster", "connection",
            "con2=>mysql://kamailio:kamailiorw@10.121.0.121/kamailio")
modparam("db_cluster", "connection",
            "con3=>mysql://kamailio:kamailiorw@10.121.0.122/kamailio")
modparam("db_cluster", "cluster", "cls1=>con1=9r8r;con2=9r8r;con3=9r8r")
modparam("db_cluster", "inactive_interval", 180)
modparam("db_cluster", "max_query_length", 5)

# ----- sqlops params -----
modparam("sqlops","sqlcon","ca=>cluster://cls1")


When i start kamailio it fails with:

Mar 9 17:11:49 localhost kamailio[31063]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Mar 9 17:11:49 localhost kamailio[31063]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Mar 9 17:11:49 localhost kamailio[31063]: INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 Mar 9 17:11:49 localhost kamailio[31063]: INFO: permissions [parse_config.c:251]: parse_config_file(): file not found: /usr/local/etc/kamailio/permissions.allow Mar 9 17:11:49 localhost kamailio[31063]: INFO: permissions [permissions.c:608]: mod_init(): default allow file (/usr/local/etc/kamailio/permissions.allow) not found => empty rule set Mar 9 17:11:49 localhost kamailio[31063]: INFO: permissions [parse_config.c:251]: parse_config_file(): file not found: /usr/local/etc/kamailio/permissions.deny Mar 9 17:11:49 localhost kamailio[31063]: INFO: permissions [permissions.c:617]: mod_init(): default deny file (/usr/local/etc/kamailio/permissions.deny) not found => empty rule set Mar 9 17:11:49 localhost kernel: kamailio[31063]: segfault at 80 ip 00007f7f4f9ffddc sp 00007fffde2f88a0 error 4 in db_cluster.so[7f7f4f9ec000+28000] Mar 9 17:11:50 localhost kamailio: ERROR: <core> [daemonize.c:315]: daemonize(): Main process exited before writing to pipe


Could this be a bug or is this a configuration issue? I tested the dbnodes and they seem to respond fine to any query's i send.

Configurations should never create segmentation faults, so it's
clearly a bug. Can you find the core dump file and produce a
backtrace?

/O
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Reply via email to