I’m trying setting up 4.2.0 on docker and extracted everything from path directly. But my xibo_cms-db_1 and xibo_cms-xmr_1 are stuck in restarting stage.
errors as follows
For XMR :
error for xmr Operation not permitted (src/thread.cpp:269)
Aborted (core dumped)
For SQL :
[Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.41-1.el9 started.
[Note] [Entrypoint]: Switching to dedicated user ‘mysql’
[Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.41-1.el9 started.
[Note] [Entrypoint]: Initializing database files
[Warning] [MY-011068] [Server] The syntax ‘–skip-host-cache’ is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
[System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.41) initializing of server in progress as process 79
[ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
[ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
[ERROR] [MY-010119] [Server] Aborting
[System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.41) MySQL Community Server - GPL.
Could you please suggest me steps to resolve this? Or share me steps or configs to upgrade Xibo CMS from 2.3.9 to latest version. Thanks in advance
You need to do the upgrade in stages. You can’t go straight from 2.3 to 4.2. You also have likely 2 MySQL upgrades to do.
First need to down the containers and make sure you have a good backup. Then upgrade to Xibo 3.3.12. As part of that. you’ll need to make sure you upgrade from MySQL 5.6 to 5.7 by running mysqlupgrade. Notes on doing that are here:
Then once all is well and you’re on MySQL 5.7, you can upgrade to Xibo 4.2.0, and with it MySQL 8.0.
Hey Alex,
mysql has been upgraded to 5.7 but I’m still on 2.3.9. Can you share me image path of 3.3.12 to pull? or Shall I rename the containers in docker compose file and restart docker?
You’d need to upgrade to MySQL 5.7 and 3.3.12 at the same time. You can get the correct docker-compose file for 3.3.12 from the release download page:
Be sure to follow the guidance in the 2.3.10 release notes that I linked above to upgrade MySQL’s internal data structures to 5.7 otherwise subsequent upgrades will fail.
You’d replace docker-compose.yml with the fresh version from the 3.3.12 download, and then
docker-compose pull
docker-compose up -d
presuming you’re not using the remote-mysql or custom-ports variants of the files.
I don’t understand the question. I’ve linked you to the downloads for 3.3.12. You need to download the 3.3.12 release, and in there is the docker-compose.yml file you need to upgrade to 3.3.12.
