What we've done
We're in the process of updating our prod instance to 3.2, and we've updated our extensions locally to work for 3.2.
We've also managed to install 3.2 on an older version of our database (the difference at the moment is not clear, though more information may be provided later when we finish looking into it)
Anyway, we've copied over the mysql database from our prod 3.0.3 instance, and we tried running the wizard.
On the unattended wizard, at the 40% step it just crashes with no output.
On the GUI wizard, at the 40% step we are given this error message:
If you have any ideas of how we should go about allowing iTop 3.2 to use this db, it would be appreciated. We will continue testing with older versions of the db and hopefully find something.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes - the issue we recently reported was also related to the update but we sorted that one out. Yes, we followed the instructions & unzipped everything correctly.
Here is the entire setup.log, hopefully that gives some more info?
It seems that division by zero happens when "priv_change" is detected to have 0 records ("There is a total of 0 records in priv_change."), and the error happens at this line in the itop source code:
Hey - unfortunately we are not able to get the other version of the DB that worked back. We have tried a fresh install with an empty database, and it worked successfully, but with the production database it always gives us this division by zero error. Is it because we are copying the database without the activity log?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have two versions of backups from our prod db - one without and one with priv_change table.
We tried running the setup WITH the contents of priv_change, and it crashed on 60% this time:
Moduleitop-structure:errorwhencallingmoduleinstallerclassStructureInstallerforAfterDatabaseCreationhandler:ModulelId=itop-structure,ModuleInstallerClass=StructureInstaller,ModuleInstallerHandler=AfterDatabaseCreation,ExceptionClass=MySQLException,ExceptionMessage=FailedtoissueSQLquery:query=INSERTINTO`priv_action_newsroom`(`id`,`title`,`message`,`icon_data`,`icon_mimetype`,`icon_filename`,`icon_downloads_count`,`priority`,`test_recipient_id`,`recipients`,`url`)VALUES('3','$this->friendlyname$','You have been mentioned by $current_contact->friendlyname$','','','',0,'3',0,'SELECT Person WHERE id = :mentioned->id','$this->url()$'),mysql_errno=1062,mysql_error=Duplicateentry'3'forkey'PRIMARY'
Edit:
We ran a query to drop the contents of priv_action_newsroom, and the setup worked successfully. I'm not sure why there was duplicate entry, but things seem to be working properly.
Last edit: Jacques Dancause 2024-12-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey there! Hope you're well.
What we've done
We're in the process of updating our prod instance to 3.2, and we've updated our extensions locally to work for 3.2.
We've also managed to install 3.2 on an older version of our database (the difference at the moment is not clear, though more information may be provided later when we finish looking into it)
Anyway, we've copied over the mysql database from our prod 3.0.3 instance, and we tried running the wizard.
On the unattended wizard, at the 40% step it just crashes with no output.
On the GUI wizard, at the 40% step we are given this error message:
We also have an error.log, the last few errors are as follows (replaced some sensitive info with stars):
If you have any ideas of how we should go about allowing iTop 3.2 to use this db, it would be appreciated. We will continue testing with older versions of the db and hopefully find something.
Seeing you reported another issue recently as well: did you just grab the iTop 3.2.0 community package; and unzip everything correctly?
Yes - the issue we recently reported was also related to the update but we sorted that one out. Yes, we followed the instructions & unzipped everything correctly.
Here is the entire setup.log, hopefully that gives some more info?
It seems that division by zero happens when "priv_change" is detected to have 0 records ("There is a total of 0 records in priv_change."), and the error happens at this line in the itop source code:
Last edit: Jacques Dancause 2024-11-28
Hey - unfortunately we are not able to get the other version of the DB that worked back. We have tried a fresh install with an empty database, and it worked successfully, but with the production database it always gives us this division by zero error. Is it because we are copying the database without the activity log?
Without what activity log exactly?
We have two versions of backups from our prod db - one without and one with priv_change table.
We tried running the setup WITH the contents of priv_change, and it crashed on 60% this time:
Edit:
We ran a query to drop the contents of priv_action_newsroom, and the setup worked successfully. I'm not sure why there was duplicate entry, but things seem to be working properly.
Last edit: Jacques Dancause 2024-12-02