On Fri, Mar 7, 2014 at 12:59 AM, Gunnar Beutner <gunnar.beut...@netways.de>wrote:
> That's a bug (https://dev.icinga.org/issues/5721) which I've just fixed > in the Git repository. Can you re-test this using the snapshot RPMs please? > I've moved over from the release repository to the snapshot repository. Once there, I did a: yum remove icinga2.x86_64 icinga2-common.x86_64 (which also removed icinga2-ido-mysql), followed by a: yum install icinga2-0.0.7-snapshot201403071522.el6.x86_64 icinga2-ido-mysql-0.0.7-snapshot201403071522.el6.x86_64 icinga2-common-0.0.7-snapshot201403071522.el6.x86_64 I'm now getting the following error in the log: [2014-03-07 10:35:55 -0800] <WQ #3> critical/db_ido_mysql: Exception during database operation: /home/abuild/rpmbuild/BUILD/icinga2-abuild/components/db_ido_mysql/idomysqlconnection.cpp(290): Throw in function icinga::IdoMysqlResult icinga::IdoMysqlConnection::Query(const icinga::String&) Dynamic exception type: N5boost16exception_detail10clone_implIN6icinga14database_errorEEE std::exception::what: std::exception [PN6icinga10StackTraceE] = (0) libdb_ido_mysql.so: icinga::IdoMysqlConnection::Query(icinga::String const&) (+0x501) [0x7f34c5372971] (??:0) (1) libdb_ido_mysql.so: icinga::IdoMysqlConnection::Reconnect() (+0xa79) [0x7f34c5376869] (??:0) (2) libbase.so: icinga::WorkQueue::WorkerThreadProc() (+0x56f) [0x7f34c698a9af] (??:0) (3) libboost_thread-mt.so.5: thread_proxy (+0x77) [0x3b99a0ad47] (??:0) (4) /lib64/libpthread.so.0() [0x307e0079d1] (5) libc.so.6: clone (+0x6d) [0x37c28e8b6d] (??:0) [PN6icinga12ContextTraceE] = (0) Reconnecting to MySQL IDO database 'ido-mysql' [PN6icinga16errinfo_message_E] = Data too long for column 'agent_version' at row 1 [PN6icinga23errinfo_database_query_E] = INSERT INTO icinga_conninfo (instance_id, connect_time, last_checkin_time, agent_name, agent_version, connect_type, data_start_time) VALUES (1, NOW(), NOW(), 'icinga2 db_ido_mysql', 'v0.0.7-54-g14d8f8a', 'INITIAL', NOW()) I took a look at the mysql schema and it still says that agent_version is varchar(16). Should I alter the table or is there a different solution?
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
