This one with carrieroute tables ...
With a clean database I get ...
May 24 16:27:11 [30535] INFO:core:init_mod: initializing module carrierroute May 24 16:27:11 [30535] INFO:carrierroute:mod_init: use database as configuration sourceMay 24 16:27:11 [30535] ERROR:core:db_check_table_version: invalid version 2 for table carrierfailureroute found, expected 3 (check table structure and table "version") May 24 16:27:11 [30535] ERROR:carrierroute:carrierroute_db_init: during table version check.
If I manualy set carrierfailureroute table version to 3 (UPDATE version SET table_version = 3 where table_name = 'carrierfailureroute';) I get the opposite error:
May 24 16:30:31 [30594] INFO:core:init_mod: initializing module carrierroute May 24 16:30:31 [30594] INFO:carrierroute:mod_init: use database as configuration sourceMay 24 16:30:31 [30594] ERROR:core:db_check_table_version: invalid version 3 for table carrierfailureroute found, expected 2 (check table structure and table "version") May 24 16:30:31 [30594] ERROR:carrierroute:carrierroute_db_init: during table version check. May 24 16:30:31 [30594] ERROR:core:init_mod: failed to initialize module carrierroute
It have no sense ... any clue what's happening ?
On Sonntag, 24. Mai 2009, Raúl Alexis Betancor Santana wrote:
ERROR:core:db_check_table_version: invalid version 2 for table carrierfailureroute found, expected 3 (check table structure and table "version")
If I manualy set carrierfailureroute table version to 3 (UPDATE version SET table_version = 3 where table_name = 'carrierfailureroute';) I get the opposite error:
ERROR:core:db_check_table_version: invalid version 3 for table carrierfailureroute found, expected 2 (check table structure and table "version")
It have no sense ... any clue what's happening ?
Hi Raúl ,
this is indeed really strange. This are the values in the code:
/* table version */ const unsigned int carrierroute_version = 3; /* table version */ const unsigned int carrierfailureroute_version = 2;
and the corresponding entries in the version table.
+---------------+---------------------+ | table_version | table_name | +---------------+---------------------+ | 3 | carrierroute | | 2 | carrierfailureroute | +---------------+---------------------+
I just tested it (1.5.x) again, loads without any problems.
May 25 10:19:35 ca ../kamailio[13376]: INFO:carrierroute:mod_init: use database as configuration source May 25 10:19:35 ca ../kamailio[13376]: INFO:carrierroute:load_route_data_db: carrier 'carrier1' (id 1) has 3 domains [..]
Perhaps you've done some changes to the cr module? Just guessing what could be the reason for this problem..
Henning
On Monday 25 May 2009 09:23:09 Henning Westerholt wrote:
On Sonntag, 24. Mai 2009, Raúl Alexis Betancor Santana wrote:
ERROR:core:db_check_table_version: invalid version 2 for table carrierfailureroute found, expected 3 (check table structure and table "version")
If I manualy set carrierfailureroute table version to 3 (UPDATE version SET table_version = 3 where table_name = 'carrierfailureroute';) I get the opposite error:
ERROR:core:db_check_table_version: invalid version 3 for table carrierfailureroute found, expected 2 (check table structure and table "version")
It have no sense ... any clue what's happening ?
Hi Raúl ,
this is indeed really strange. This are the values in the code:
/* table version */ const unsigned int carrierroute_version = 3; /* table version */ const unsigned int carrierfailureroute_version = 2;
and the corresponding entries in the version table.
+---------------+---------------------+
| table_version | table_name |
+---------------+---------------------+
| 3 | carrierroute | | 2 | carrierfailureroute |
+---------------+---------------------+
I have the same on a new fresh "kamdbctl create" database, but ... I get lot of errors about fields that doesn't exist on carrierfailureroute table, apart from the errors about versions.
Perhaps you've done some changes to the cr module? Just guessing what could be the reason for this problem..
I'm trying to upgrade from 1.3.2 to 1.5.1, thats all.
I will do a fresh full install on a new virtual machine and let you know what I get.
Regards
P.D.: Do not CC me, i'm on the list, so simply reply to the list.
On Montag, 25. Mai 2009, Raúl Alexis Betancor Santana wrote:
I have the same on a new fresh "kamdbctl create" database, but ... I get lot of errors about fields that doesn't exist on carrierfailureroute table, apart from the errors about versions.
Perhaps you've done some changes to the cr module? Just guessing what could be the reason for this problem..
I'm trying to upgrade from 1.3.2 to 1.5.1, thats all.
I will do a fresh full install on a new virtual machine and let you know what I get.
Hi Raul,
do you was able to get a bit more details about this problem?
Cheers,
Henning
On Friday 29 May 2009 09:39:59 Henning Westerholt wrote:
On Montag, 25. Mai 2009, Raúl Alexis Betancor Santana wrote:
I have the same on a new fresh "kamdbctl create" database, but ... I get lot of errors about fields that doesn't exist on carrierfailureroute table, apart from the errors about versions.
Perhaps you've done some changes to the cr module? Just guessing what could be the reason for this problem..
I'm trying to upgrade from 1.3.2 to 1.5.1, thats all.
I will do a fresh full install on a new virtual machine and let you know what I get.
Hi Raul,
do you was able to get a bit more details about this problem?
Cheers,
Hi Henning,
I have reinstalled all from scratch and now I don't have any problem with the table version, maybe was my fault because I was working with more than one DB at the same time.
Best regards
-
Henning Westerholt -
Raúl Alexis Betancor Santana