To be completed by the original poster:
CMS Version
2.3.10
Installation Method
Docker
Operating System
Ubuntu 20.04.6 LTS
Issue
I’m trying to update an old Xibo installation from 2.3.10 to the latest. I know I need to go to 2.3.16 first, then 3.3.7, then 4.0.0. I am inexperienced when it comes to Ubuntu, so am just ‘getting by!’
So I’m stopping the containers and removing the old tar file, downloading and extracting the 2.3.16 release and then running a pull and an up -d using the commands below.
cd /opt/xibo
docker-compose stop
rm xibo-docker.tar.gz
wget -O xibo-docker.tar.gz https://github.com/xibosignage/xibo-cms/releases/download/2.3.16/xibo-docker.tar.gz
tar --strip-components=1 -zxvf xibo-docker.tar.gz
docker-compose pull
docker-compose up -d
Using docker-compose logs-f cms-web, it sits there for the full 300 seconds trying to start the MySQL container
Running docker-compose logs-f cms-db, the first error I see is…
[Warning] InnoDB: Retry attempts for writing partial data failed
[ERROR] InnoDB: Write to file ./ibtmp failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quote exceeded.
Once the 300 seconds has been reached, the cms-web log says…
ERROR 2005 (HY000): Unknown MySQL server host ‘mysql’ (-3)
New install
The ERROR 2005 then repeats itself.
I guess because it can’t connect to the database it is treating it as a new install?
I’ve researched the ./ibtmp error, and have tried restarting the mysql container to clear this file down, and also have tried restarting the mysql service from within the container and neither help.
This is a VM and I’ve taken a snapshot so I’m able to return it back to a working 2.3.10 install, but I’ve tried various release versions between 2.3.10 and 2.3.16 with the same results.
I updated the OS on this VM to the latest 20.04 LTS release (20.04.6) last week and updated all packages (so docker is on the latest release, too). I’ve restored a backup clone of this VM from prior to this, incase it’s the latest .6 release or latest docker causing the issue and this behaves exactly the same.
Feeling very out of my depth now so would appreciate any help anyone can give!
Thanks