I read the upgrade guide before I upgraded and modified a few of the settings that applied to my environment but missed the part about needing to add the nagios user to the nagcmd group. I reverted my VM to before the upgrade, added the nagios user to nagcmd, did a "mysqlcheck -A -r -u root -p" which found some errors and fixed them, then did the upgrade to 3.7 and all is working now.
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Ton Voon Sent: Thursday, April 29, 2010 12:41 PM To: Opsview Users Subject: Re: [opsview-users] 3.7 Database Upgrade Fails Due To Incorrect KeyFile On 29 Apr 2010, at 17:27, Gordon Terrell wrote: I tried upgrading my CentOS 5.4 host running Opsview 2.14 to 3.7.0 Community Edition You missed out the bit of documentation about upgrading from 2.14: http://docs.opsview.org/doku.php?id=opsview3.0:upgrading_from_2.14 2.14 to 3.0 is a big step so there's some extra tasks that are needed. and it failed because of incorrect key file for table './runtime/nagios_hostchecks.MYI'. I tried running upgradedb.pl manually as the nagios user and got the same error. Any ideas? Below is the output from the upgrade process: Thu Apr 29 11:54:27 2010: DB at version 3.0.0 Converting tables to Innodb - this could take a long time DBD::mysql::db do failed: Incorrect key file for table './runtime/nagios_hostchecks.MYI'; try to repair it [for Statement "DELETE FROM `nagios_hostchecks` WHERE start_time <= ?"] at /usr/local/nagios/installer/upgradedb_runtime.pl line 121. This looks like a mysql problem. Run a repair on the table and then run the upgrade script again: http://docs.opsview.org/doku.php?id=opsview-community:mysql#fixing_damag ed_database_tables Ton
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
