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

[Daniel-Constantin Mierla]

Hello,

On 4/7/12 5:20 PM, Juha Heinanen wrote:
> when using db_cluster, msilo module m_dump() function generates these
> errors:
> Apr  7 18:18:02 sip /usr/sbin/sip-proxy[30210]: ERROR: db_mysql [km_dbase.c:122]: driver error on query: Unknown column 'src_addr' in 'field list'
> 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_mysql [km_dbase.c:122]: driver error on query: Unknown column 'src_addr' in 'field list'

the error is thrown from mysql module. db_cluster does not have any 
direct relation with the real db connector structure, it just calls 
appropriate functions from other db modules.

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

Have you tried with mysql directly. I expect the msilo tables structure 
changed, but schema was not properly updated (or version not increased).

>
> is there some bug in msilo db usage or in db_cluster module?  where
> does invalid mode #000 come from?
This is like no selecting algorithm is provided. I will check, since it 
should not happen at runtime, supposed to be detected at startup, but it 
might be a side effect of the next db layer failure.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/