On Mon, 9 Feb 2015, Florian Kluender wrote:
mysql -p icinga <
/usr/local/icinga/etc/modules/icinga-core/module/idoutils/db/mysql/upgrade/mysql-upgrade-1.7.0.sql
till
mysql -p icinga <
/usr/local/icinga/etc/modules/icinga-core/module/idoutils/db/mysql/upgrade/mysql-upgrade-1.12.0.sql
He asked for the password everytime. Seems to be ok.
Did the commands yield any output? Especially errors.
Get into the MySQL client and do the following:
select * from icinga_dbversion;
then
describe icinga_customvariables;
The database-version (the schema definition version) is stored in the
first table (icinga_dbversion) and that table should contain only one
row. Please post the output (there is nothing sensitive in it). In my
case, this is the entire exchange:
mysql> select * from icinga_dbversion;
+--------------+----------+---------+---------------------+---------------------+
| dbversion_id | name | version | create_time | modify_time
|
+--------------+----------+---------+---------------------+---------------------+
| 1 | idoutils | 1.11.6 | 2012-10-21 10:24:41 | 2014-10-06 18:34:19
|
+--------------+----------+---------+---------------------+---------------------+
1 row in set (0.04 sec)
mysql>
(That's my production system; my development one uses PostgreSQL and
is at 1.12.0.)
The second command will describe what columns are in the
icinga_customvariables table. If you have a column named "is_json"
then your updates worked because that column was added in 1.12.0.
Please post the output from the second one as well. This will yield
clues about what version of the schema is in play. Here's mine (note
the absense of the "is_json" column ("Field")):
mysql> describe icinga_customvariables;
+-------------------+---------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra
|
+-------------------+---------------------+------+-----+---------+----------------+
| customvariable_id | bigint(20) unsigned | NO | PRI | NULL |
auto_increment |
| instance_id | bigint(20) unsigned | YES | MUL | 0 |
|
| object_id | bigint(20) unsigned | YES | MUL | 0 |
|
| config_type | smallint(6) | YES | | 0 |
|
| has_been_modified | smallint(6) | YES | | 0 |
|
| varname | varchar(255) | YES | MUL | NULL |
|
| varvalue | text | YES | | NULL |
|
+-------------------+---------------------+------+-----+---------+----------------+
7 rows in set (0.03 sec)
mysql>
After that, it showed this in /var/log/messages:
Feb 9 14:10:22 icinga ido2db: IDO2DB 1.12.1 starting... (PID=7066)
Feb 9 14:10:22 icinga ido2db: Successfully connected to mysql database
Feb 9 14:10:22 icinga ido2db: Error: DB Version 1.6.0 does not match needed
schema version 1.12.0. Please check the upgrade docs!
Feb 9 14:10:22 icinga ido2db: Successfully disconnected from mysql database
Feb 9 14:10:37 icinga icinga: idomod: Still unable to connect to data sink.
8283 items lost, 5000 queued items to flush. Is ido2db running and
processing data?
No change? That's odd...
+------------------------------------------------+---------------------+
| Carl Richard Friend (UNIX Sysadmin) | West Boylston |
| Minicomputer Collector / Enthusiast | Massachusetts, USA |
| mailto:[email protected] +---------------------+
| http://users.rcn.com/crfriend/museum | ICBM: 42:22N 71:47W |
+------------------------------------------------+---------------------+
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
