Hello,
the last commit should fix it, it was just pushed to master. An inverted condition was not properly done.
Cheers, Daniel
On 4/11/12 8:19 AM, Juha Heinanen wrote:
Juha Heinanen writes:
db_cluster worked with latest master. i'll try tomorrow what happens when connections stop/start working.
unfortunately in the working test last night my sip proxy was not configured to use db_cluster. now when i started tests again i noticed that db_cluster still does not work. it does not matter if priority 9 is used or not. no queries db queries are made with this db_cluster definition:
modparam("db_cluster", "cluster", "sip_proxy_cluster=>sip_proxy_con1=8s8s;sip_proxy_con2=7s7s")')
and sip proxy does not start because it cannot get table versions:
Apr 11 09:14:35 sip /usr/sbin/sip-proxy[16956]: ERROR:<core> [db.c:389]: error in db_query Apr 11 09:14:35 sip /usr/sbin/sip-proxy[16956]: ERROR:<core> [db.c:428]: querying version for table dialplan Apr 11 09:14:35 sip /usr/sbin/sip-proxy[16956]: ERROR: dialplan [dp_db.c:106]: error during table version check. Apr 11 09:14:35 sip /usr/sbin/sip-proxy[16956]: ERROR: dialplan [dialplan.c:200]: could not initialize data Apr 11 09:14:35 sip /usr/sbin/sip-proxy[16956]: ERROR:<core> [sr_module.c:939]: init_mod(): Error while initializing module dialplan (/usr/lib/sip-proxy/modules/dialplan.so)
-- juha