So, I am trying to catch my Xibo install to the current version. I tried to upgrade from 1.7.1 straight to 1.7.7 this morning and got stuck when doing the database upgrade. When the database upgrade starts my CPU sits between 20% and 30% utilization on the mysqld.exe process and never completes. I let it run for over an hour this morning. I decided to try smaller steps than 1.7.1 -> 1.7.7. I successfully upgraded from 1.7.1 -> 1.7.3, 1.7.3 -> 1.7.4, 1.7.4 -> 1.7.5. This is running on Windows server 2012r2 running on an ESXi server so I am using snapshots for backups between upgrades and can easily roll back when one fails.
Trying to upgrade from 1.7.5 to 1.7.6 to 1.7.7 causes the same issue that I was seeing this morning with the database upgrade never completing.
Considering that I completed three upgrades successfully I can’t see that there would be any permissions problems or anything of that like causing issues.
The upgrade step to 1.7.6 performs these 3 SQL statements:
ALTER TABLE `version` ENGINE=InnoDB;
ALTER TABLE `transition` ENGINE=InnoDB;
ALTER TABLE `session` ENGINE=InnoDB;
ALTER TABLE `log` ENGINE=InnoDB;
It seems likely that one of these statements is causing you an issue - my money would be on either the session or log statements.
We did encounter a problem with the session statement which we thought we had fixed in 1.7.7 (it was a code fix to allow that upgrade step to run). This problem did not occur when upgrading to 1.7.6, so that may not be your issue.
I’d try these things:
Run TRUNCATE TABLE log before the upgrade
if that doesn’t work, edit /install/database/91.sql and delete those 4 statements. Once the upgrade completes run them manually in a MySQL window.