1 Oct
2018
1 Oct
'18
8:38 a.m.
This was related to adding support for UNSIGNED types. So far we had
only signed types in DB API, but latest MySQL version is inserting 0
without any error when the actual value is a signed negative value.
Should be fixed now in latest master, try with it and see if all fine now.
Cheers,
Daniel
On 01.10.18 07:43, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
I just pushed a patch for it, can you test and
see if all goes fine with
your config?
cfg_rpc module error is now gone, but got another one:
Oct 1 08:37:19 char /usr/bin/sip-proxy[26419]: ERROR: <core> [db.c:419]:
db_table_version(): invalid type (8) or nul (0) version columns for lcr_rule
Oct 1 08:37:19 char /usr/bin/sip-proxy[26419]: ERROR: <core> [db.c:447]:
db_check_table_version(): querying version for table lcr_rule
Oct 1 08:37:19 char /usr/bin/sip-proxy[26419]: ERROR: lcr [lcr_mod.c:687]: mod_init():
error during table version check
Oct 1 08:37:19 char /usr/bin/sip-proxy[26419]: ERROR: <core>
[core/sr_module.c:890]: init_mod(): Error while initializing module lcr
(/usr/lib/x86_64-linux-gnu/sip-proxy/modules/lcr.so)
Earlier master K from sept 17 starts OK, so I don't think there is
anything wrong in the db.
-- Juha