SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for cms-db failed: Temporary failure in name resolution

Get Help CMS Installation
1

To be completed by the original poster:

CMS Version

4.1.0

Installation Method

Cocker

Operating System

Ubuntu Linux 20.04.6

Issue

Server is on a sub domain, with ssl.
I’m running a xibo 4.1.0 installation.
The server runs normal for a few hours.
At random i get then: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for cms-db failed: Temporary failure in name resolution
Xibo is then gone.

When i reboot, everything runs then normal… till the sqlstate error appears.

Please help what to do.

3

Update :

I used this manual from the forum : Xibo CMS with Docker on Ubuntu 22.04

There is a problem with the configuration : cms_custom-ports.yml

version: “2.1”

services:
cms-db:
image: mysql:8.0
volumes:
- “./shared/db:/var/lib/mysql:Z”
restart: always
environment:
- MYSQL_DATABASE=cms
- MYSQL_USER=cms
- MYSQL_RANDOM_ROOT_PASSWORD=yes
mem_limit: 1g
env_file: config.env
cms-xmr:
image: [Package xibo-xmr · GitHub](http://ghcr.io/xibosignage/xibo-xmr:0.11)
ports:
- “65500:9505”
restart: always
mem_limit: 256m
env_file: config.env
cms-web:
image: [Package xibo-cms · GitHub](http://ghcr.io/xibosignage/xibo-cms:release-4.1.1)
volumes:
- “./shared/cms/custom:/var/www/cms/custom:Z”
- “./shared/backup:/var/www/backup:Z”
- “./shared/cms/web/theme/custom:/var/www/cms/web/theme/custom:Z”
- “./shared/cms/library:/var/www/cms/library:Z”
- “./shared/cms/web/userscripts:/var/www/cms/web/userscripts:Z”
- “./shared/cms/ca-certs:/var/www/cms/ca-certs:Z”
restart: always
environment:
- MYSQL_HOST=cms-db
- XMR_HOST=cms-xmr
- CMS_USE_MEMCACHED=true
- MEMCACHED_HOST=cms-memcached
env_file: config.env
ports:
- “65501:80”
mem_limit: 1g
cms-memcached:
image: memcached:alpine
command: memcached -m 15
restart: always
mem_limit: 100M
cms-quickchart:
image: ianw/quickchart
restart: always

Add the following lines.
Add the lines to the cms-db

networks:
default:
aliases:
- mysql

If not the mysql docker container keeps running into problems/restart etc.
After added this lines, the mysql docker container runs stable.

Xibo : Can you add this lines in the template files of cms_custom-ports.yml ??
[/quote]

4

The correct fix for this is to set MYSQL_HOST on the cms-web container, and we already do that in the release docker-compose files:

5

Hi Alex,

I have added only the networks lines tot cms-db (mysql container) in cms_cutom-ports.yml.
Without the conmtainer runs very unstable …
I used the github 4.1.0 version.

Greets,

Dennis

6

It’s co-incidental. No networks, defaults or aliases lines are required in the file.

7

Log from the mysql container.

2024-11-11T12:24:58.603282Z 0 [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.
2024-11-11T12:24:58.608286Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.39) starting as process 1
2024-11-11T12:24:58.632066Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-11-11T12:24:59.359324Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-11-11T12:25:00.355569Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2024-11-11T12:25:00.376071Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2024-11-11T12:25:00.839667Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-11-11T12:25:00.839883Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-11-11T12:25:00.854974Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2024-11-11T12:25:01.041721Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.39'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2024-11-11T12:25:01.041806Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock

Could --skip-host-cache do this ?

8

No. That option is set by the mysql container itself, not us, so it’s unrelated. There’s no errors or anything that shows me a problem in that log - other than it did crash recovery which suggests that the container was killed rather than stopped previously.

9

Thanks alex for the reply :wink: