Found it. The upgrade script was not able to find the correct database version
it seems. So I commented all if ($db->is_lower("2.14*")) until the correct
database version and ran the update again.
So: the upgrade script is wrong, or the database contains too much information
(why do you keep all schema_versions?)
Regards,
--
Toni Van Remortel
System Engineer @ Precision Operations NV
+32 3 451 92 20 - [email protected]
From:[email protected]
[mailto:[email protected]] On Behalf Of Toni Van Remortel
Sent:Thursday, August 27, 2009 5:08 PM
To:[email protected]
Subject:[opsview-users] Upgrade to 3.3 fails
Hi,
It seems that the upgrade procedure fails again on the database:
Setting up opsview-core (3.3.0.2987-1hardy1)
...
Database opsview detected - upgrading
...
Thu Aug 27 17:00:49 2009: Starting for opsview
Thu Aug 27 17:00:49 2009: DB at version
2.14.5
DBD::mysql::db do failed: Error on rename of
'./opsview/servicecheckdependencies' to './opsview/#sql2-130a-5a67e' (errno:
152) [for Statement "ALTER TABLE servicecheckdependencies DROP FOREIGN KEY
servicecheckdependencies_dependencyid_fk"] at
/usr/local/nagios/installer/upgradedb_opsview.pl line
1338.
Thu Aug 27 17:00:49 2009: Finished for
opsview
dpkg: error processing opsview-core
(--configure):
subprocess post-installation script returned error exit status 1
Database at version 2.14.5 ??? I'm upgrading from 3.1 !!
Please advise (again), as I had similar problems with the upgrade to 3.1.
--
Toni Van Remortel
System Engineer @ Precision Operations NV
+32 3 451 92 20 - [email protected]
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
