On 29 Apr 2010, at 14:09, Ispas Paul wrote:
Can you run /usr/local/nagios/installer/upgradedb.pl and capture the
output? This should be run as part of the upgrade.
{blade}[r...@nms ~]# /usr/local/nagios/installer/upgradedb.pl
Thu Apr 29 16:02:40 2010: Starting for opsview
Thu Apr 29 16:02:40 2010: DB at version 3.6.0
Creating CONFIGUREVIEW and CONFIGURESAVE access and adding to all
roles with ADMINACCESS
Updated database to version 3.6.1
Thu Apr 29 16:02:40 2010: DB at version 3.7.0
Adding extra columns to notificationmethods
DBD::mysql::db do failed: Table 'contact_variables' already exists
[for Statement "
CREATE TABLE contact_variables (
contactid int NOT NULL,
name varchar(128) NOT NULL,
value TEXT NOT NULL,
PRIMARY KEY (contactid, name),
INDEX (contactid),
CONSTRAINT contact_variables_contactid_fk FOREIGN KEY
(contactid) REFERENCES contacts(id) ON DELETE CASCADE
) ENGINE=InnoDB;
"] at /usr/local/nagios/installer/upgradedb_opsview.pl line 1806.
Thu Apr 29 16:02:40 2010: Finished for opsview
upgrade failed at /usr/local/nagios/installer/upgradedb.pl line 35.
Have you restored the opsview db and tried to reinstall? The upgrade
says that a table already exists. This happens if you have an Opsview
data that has been upgraded (to create the new table), but you then do
a restore (which leaves the existing table there) followed by another
upgrade.
If you are going to do a restore, can you drop the opsview database
first, and then restore from the db backup file. This way the table
will definitely not be there and so not halt the upgrade.
Do you have any output during the restore? That first failure is what
I want to stop occuring.
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
