9 Apr
2012
9 Apr
'12
5:38 p.m.
Hello,
msilo was missing few db set table before doing the queries -- it was
fine without db_cluster, but with it there are two layers and the table
name has to be refreshed in order to propagate completely.
I did a commit to msilo for now, I will check other modules as well.
Let me know if works now.
Cheers,
Daniel
On 4/9/12 1:36 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
--
Daniel-Constantin Mierla
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/
> Apr 7 18:18:02 sip
/usr/sbin/sip-proxy[30210]: ERROR:<core> [db_query.c:127]: error while submitting
query
> Apr 7 18:18:02 sip /usr/sbin/sip-proxy[30210]: ERROR: db_cluster [dbcl_api.c:274]:
invalid mode #000 (0)
> Apr 7 18:18:02 sip /usr/sbin/sip-proxy[30210]: ERROR: msilo [msilo.c:1066]: failed
to query database
>
> this is with unmodified db_cluster module when all db connections are
> working ok.
daniel,
i turned on mysql logging and got this:
90 Query select id,src_addr,dst_addr,body,ctype,inc_time,extra_hdrs from location
where username='jh' AND domain='test.fi' AND snd_time=0 order by id
that is, msilo query looks otherwise ok, but table is wrong! it should
be silo, not location. i have NOT set db_table msilo module variable.
after the above select, there is update on location table. could table
name be somehow overridden by previous or next query in case of
db_cluster?
with same msilo table, queries work ok when db_cluster is not in use.
-- juha