Hi,
I want to upgrade my xibo server (apache2 V1.8.12) to the new version but i am stuck on this page :
“The CMS is temporarily off-line as an upgrade is in progress. Please check with your system administrator for updates or refresh your page in a few minutes.”
Are there any additional steps required for an upgrade to V2?
Thank you.
I am having the same issue after upgrading to v2. I am running xibo with docker on ubuntu 16.04. When i go to my /opt/xibo directory where i have it installed and try to run the “php vendor/bin/phinx migrate” when i try to run this it says that it could not open the file vendor/bin/phins. Any help?
With Docker the migrations are run for you. You don’t need to run them manually.
If you get the logs from the cms-web container (docker-compose logs -f cms-web) you should see them having been run - or still running potentially - together with any errors.
So far it has taken almost 20 hours. Should it be taking this long? I can post the log out put.
cms-web_1 mysqldump: Got Error 1146 “table ‘cms.lktagedisplaygroup’ doesn’t exist when using LOCK TABLES” is the only error that it shows.
Warning: require(C:\wamp\www\xibo-cms\vendor\bin/…/app/phinx.php): failed to open stream: No such file or directory in C:\wamp\www\xibo-cms\vendor\bin\phinx on line 27
Fatal error: require(): Failed opening required ‘C:\wamp\www\xibo-cms\vendor\bin/…/app/phinx.php’ (include_path=’.;C:\php\pear’) in C:\wamp\www\xibo-cms\vendor\bin\phinx on line 27
So for the first error from mysqldump, I would assume you have a crashed or missing table. Did someone perhaps delete the idb file for that table from the shared/db folder?
Beyond that, the migrations fail saying that there is already a column “isDisplayNotification”. That should only happen if you’ve previously run upgrades in 1.8 that failed or partially completed.
To resolve, you’d need to fix the error with the missing table first. Once that is corrected, you’ll need to initially remove the column shown from the database and that should allow the migration to run.
in the shared/db/cms folder i can see both the .frm and the .idb files for the the table in question. as for the isDisplayNotification error there was an error with the database the last time we upgraded. We had to restore the db from an older backup.
You would need to use MySQL’s own routines to repair the table, or in the worst case drop it and recreate it based on the schema for the version of 1.8 that you are trying to upgrade from.
Then either you’re using an external database rather than the one provided by the containers, or you’re not inside the MySQL container.
If there’s corruption in your database, and it seems there is, then if you want us to look at it we may be able to do so on a paid basis. Otherwise I can only really offer you general guidance.
If you aren’t able to make it work, I’d suggest rolling back to your pre-upgrade backup and checking the status of the tables in the database at that point.