[sr-dev] db_cluster problem with msilo module database clustering

[Juha Heinanen]

Daniel-Constantin Mierla writes:

> > 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