3.3.7
Docker
Ubuntu 24.04 LTS
Upgrading to 4.0.15 from the current 3.3.7. The DB container fails to start. It appears that the upgrade process is not upgrading the existing DB, just trying to read it and fails. It is stuck in a ‘Restarting’ condition.
Rolling back to 3.3.7 and the system runs successfully.
I have tried several times but get the same result. How do I force the DB upgrade as part of the 4.0.15 upgrade?
Check the logs for the MySQL container. Perhaps it’s an old MySQL 5.6 install that has been upgraded to MySQL 5.7 but mysql_upgrade hasn’t been run? It has to be done manually there - see Xibo CMS 2.3.10 Released - #2 by alex
Once you get on to 4.0.15 you should check the notes about the upgrade from MySQL 8.0 to 8.4 too. See MySQL 8.0 - 8.4 Upgrade Notes (mysql_native_password)
Alex,
Thank you for getting back to me. It is appreciated.
Unfortunately, the MySQL command does not work as it is trying to start the daemon as root and this is being blocked by security. I have had a dig around but have not been able to find a workaround for it.
That sounds like it’s running on something that isn’t Docker then, as there shouldn’t be any restrictions on what I’ve suggested. In that case, you might need to either export the data from MySQL and re-import it in to a MySQL 5.7 container clean, or move the data to a less-restrictive host, do the database upgrade there, and then move the data back again.
Alex,
Sorted the DB access. I had to add the ‘-u mysql’ to the command to start the mysql daemon. I was able to run the update command. This has resolved the issue with the DB docker sitting in restarting mode.
Now on to the next issue, the xmr docker sitting in restarting mode!!
Thanks for your assistance with the DB. It is greatly appreciated.
Alex,
I have success. After a lot of faffing around, I found I had to add:
security_opt:
- seccomp:unconfined
This had to go into the docker-compose.yml for both the xml and db.
I now have 4.0.15 up and going. On to getting it fully up to date.