I haven't used the group functionality at all, saw it that Jan added
very long time ago (iirc), but didn't spend time to understand what implies.
However, if you get a core dump, we can look at the backtrace and see
where it crashes.
Cheers,
Daniel
On 20/01/15 23:52, Juha Heinanen wrote:
with latest master, i tried to add [group] to mysql
db_urls and sqlops
urls, eg.
modparam("mtree", "db_url",
"mysql://user:pass@[sip_proxy]127.0.0.1/sip_proxy")
and in my.cfg the group was defined like this:
[sip_proxy]
ssl-ca=/etc/mysql/ca-cert.pem
ssl-cert=/etc/mysql/client-cert.pem
ssl-key=/etc/mysql/client-key.pem
the result was that when i start kamailio, it starts to run out of mysql
connections and dumps core no matter how high i set max_connections in
my.cfg:
Jan 21 00:47:33 siika /usr/bin/sip-proxy[30612]: ERROR: db_mysql [km_my_con.c:114]:
db_mysql_new_connection(): driver error: Too many connections
Jan 21 00:47:33 siika /usr/bin/sip-proxy[30612]: ERROR: <core> [db.c:314]:
db_do_init2(): could not add connection to the pool
Jan 21 00:47:33 siika /usr/bin/sip-proxy[30612]: ERROR: mtree [mtree_mod.c:346]:
mi_child_init(): failed to connect to database
Jan 21 00:47:33 siika /usr/bin/sip-proxy[30612]: ERROR: <core> [sr_module.c:900]:
init_mod_child(): Error while initializing module mtree
(/usr/lib/sip-proxy/modules/mtree.so)
without the [group] kamailio starts fine and does not complain about too
many connections.
is this a bug in group handling or something else?
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda