Hello XiboLand…those of you struggling to spin the newer versions of Xibo or attempting to migrate from an existing xibo version example, from version 3.3.12 to 4.0.0…. after you spin docker up, you get errors such as this…
Fatal Error - sorry this shouldn’t happen. SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for mysql failed: Name or service not known
well, after years of trying to switch to xibo v4 from xibo v3, i just gave it a final push and discovered the main problem behind it all. I once reported it here that I had issues using the v4.xx until i switch from MYSQL:8.xx to MYSQL:5.7
well, i decided to dig more into the problem with AI on the side, and i figured out that:
MYSQL version 8 does not work with my server’s cpu. this is why xibo could never connect.
xibo v4.x.x ships with MYSQL:8.0. if you server is old, you are in trouble…just run this command in your server as root
sudo docker logs mysql and the result below will explain
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
my old man (server) only supports x8g-64-v1 and MYSQL 8x doesnt work with that.
SOLUTION??…MariaDB supports older servers with 8x-64-v1 so all you need to do is, replace the cms-db or mysql image with mariadb…like this image: mysql:8.0 change to image: mariadb:10.6
backup you existing db and shared folder for safety. spin up the docker and you will smile at xibo within 5 minutes
i tested this with a fresh new xibo and just imported 1 layout with data. so i did not bring data from a previous xibo. i will try that and see…from mysql:5.7 to mariadb:10.6
my player connects and works fine, RSS feed and images all fine.
to run this command sudo docker logs mysql , replace mysql with your database container name. how to know your database container?, just type sudo docker container ls, then look at the line with 3306 port number and the container name is what you add to sudo docker logs YOUR CONTAINER NAME
Good Luck!
