Fresh Xibo Docker Install - mysql database won’t start

Icttechie · March 19, 2018, 4:04pm

Hi I’ve been trying to setup a fresh install of Xibo using docker for windows toolbox on server 2012 r2. It all installed ok I edited the files as suggested in the documentation as we have another web server using port 80. However the MySQL instance won’t start. When running the command docker ps -a everything else is up but MySQL keeps saying restarting. When we connect to docker via the web we get a fatal error sqlstate[hy000] [2002] php_network_getaddresses error.

Anybody come across this before?
Thanks

alex · March 20, 2018, 9:50am

Try adding

command: --innodb_use_native_aio=0

To the cms-db service definition in your docker-compose file.

You’ll need to down the containers prior to that, and the delete the contents of shared/db before bringing them back up.

Icttechie · March 28, 2018, 7:51am

Hi Appologies for the delay in replying. This has done the trick. Thank you very much.

mykac · November 8, 2019, 1:52pm

Hi Alex,

After few working days now I am getting this error “Fatal Error - sorry this shouldn’t happen. SQLSTATE[HY000] [1130] Host ‘172.19.0.4’ is not allowed to connect to this MySQL server”

This is output of command “docker ps -a”

CONTAINER ID IMAGE COMMAND CREATED STATUS

   PORTS                               NAMES

ee0fd69db9f0 xibosignage/xibo-cms:release-2.1.2 “/entrypoint.sh” 8 minutes ago Up 5 minutes

   0.0.0.0:80->80/tcp                  xibo_cms-web_1

427252796d1d xibosignage/xibo-xmr:release-0.7 “/entrypoint.sh” 8 minutes ago Up 6 minutes

   0.0.0.0:9505->9505/tcp, 50001/tcp   xibo_cms-xmr_1

4f5dc2b0638b mysql:5.6 “docker-entrypoint.s” 8 minutes ago Up 6 minutes

  3306/tcp                            xibo_cms-db_1

72de972ba423 hello-world “/hello” 2 hours ago Exited (0) 2 hours

ago hungry_johnson

40b6001b7f87 hello-world “/hello” 3 days ago Exited (0) 3 days

ago eloquent_cori

This is output of command “docker-compose logs” after “docker-compose down” and “docker-compose up -d”

cms-web_1 | Waiting for MySQL to start - max 300 seconds

cms-web_1 | MySQL started

cms-web_1 | Updating settings.php

cms-web_1 | ERROR 1130 (HY000): Host ‘172.19.0.4’ is not allowed to connect to this MySQL server

cms-web_1 | New install

cms-web_1 | Provisioning Database

cms-web_1 | ERROR 1130 (HY000): Host ‘172.19.0.4’ is not allowed to connect to this MySQL server

cms-web_1 | Phinx by CakePHP - https://phinx.org. 0.9.2

cms-web_1 |

cms-web_1 | using config file .varwwwcmsphinx.php

cms-web_1 | using config parser php

cms-web_1 | using migration paths

cms-web_1 | - /var/www/cms/db/migrations

cms-web_1 | warning no environment specified, defaulting to: production

cms-web_1 | using adapter mysql

cms-web_1 | using database cms

cms-web_1 |

cms-db_1 | 2019-11-08 13:05:22+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.6.46-1debian9 started.

cms-db_1 | 2019-11-08 13:05:24+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’

cms-db_1 | 2019-11-08 13:05:25+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.6.46-1debian9 started.

cms-db_1 | 2019-11-08 13:05:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_

defaults_for_timestamp server option (see documentation for more details).

cms-db_1 | 2019-11-08 13:05:29 0 [Note] mysqld (mysqld 5.6.46) starting as process 1 …

cms-db_1 | 2019-11-08 13:05:29 1 [Note] Plugin ‘FEDERATED’ is disabled.

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: Using atomics to ref count buffer pool pages

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: The InnoDB memory heap is disabled

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: Memory barrier is not used

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: Compressed tables use zlib 1.2.11

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: Using Linux native AIO

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: Not using CPU crc32 instructions

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: Completed initialization of buffer pool

cms-db_1 | 2019-11-08 13:05:29 1 [Note] InnoDB: Highest supported file format is Barracuda.

cms-db_1 | 2019-11-08 13:05:30 1 [Note] InnoDB: 128 rollback segment(s) are active.

cms-db_1 | 2019-11-08 13:05:30 1 [Note] InnoDB: Waiting for purge to start

cms-db_1 | 2019-11-08 13:05:30 1 [Note] InnoDB: 5.6.46 started; log sequence number 1626027

cms-db_1 | 2019-11-08 13:05:30 1 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authenti

cation plugins will not work.

cms-db_1 | 2019-11-08 13:05:30 1 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentica

tion plugins will not work.

cms-db_1 | 2019-11-08 13:05:30 1 [Note] Server hostname (bind-address): ‘*’; port: 3306

cms-db_1 | 2019-11-08 13:05:30 1 [Note] IPv6 is available.

cms-db_1 | 2019-11-08 13:05:30 1 [Note] - ‘::’ resolves to ‘::’;

cms-db_1 | 2019-11-08 13:05:30 1 [Note] Server socket created on IP: ‘::’.

cms-db_1 | 2019-11-08 13:05:30 1 [Warning] Insecure configuration for --pid-file: Location ‘/var/run/mysqld’ in the pa

th is accessible to all OS users. Consider choosing a different directory.

cms-db_1 | 2019-11-08 13:05:30 1 [Warning] ‘user’ entry ‘root@2b050af89174’ ignored in --skip-name-resolve mode.

cms-db_1 | 2019-11-08 13:05:30 1 [Warning] ‘user’ entry ‘@2b050af89174’ ignored in --skip-name-resolve mode.

cms-db_1 | 2019-11-08 13:05:30 1 [Warning] ‘proxies_priv’ entry ‘@ root@2b050af89174’ ignored in --skip-name-resolve m

ode.

cms-db_1 | 2019-11-08 13:05:30 1 [Note] Event Scheduler: Loaded 0 events

cms-web_1 | [InvalidArgumentException]

cms-db_1 | 2019-11-08 13:05:30 1 [Note] mysqld: ready for connections.

cms-web_1 | There was a problem connecting to the database: SQLSTATE[HY000] [1130] Host

cms-web_1 | ‘172.19.0.4’ is not allowed to connect to this MySQL server

cms-db_1 | Version: ‘5.6.46’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)

cms-web_1 |

TARGET] [-d|–date DATE] [-x|–dry-run]

cms-web_1 |

cms-web_1 | Configuring Database Settings

cms-web_1 | ERROR 1130 (HY000): Host ‘172.19.0.4’ is not allowed to connect to this MySQL server

cms-web_1 | Setting up Maintenance

cms-web_1 | Protected Maintenance

cms-web_1 | ERROR 1130 (HY000): Host ‘172.19.0.4’ is not allowed to connect to this MySQL server

cms-web_1 | Importing ca-certs

cms-web_1 | cp: can’t stat ‘/var/www/cms/ca-certs/*.pem’: No such file or directory

cms-web_1 | cp: can’t stat ‘/var/www/cms/ca-certs/*.crt’: No such file or directory

cms-web_1 | WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

cms-web_1 | Configuring Maintenance

cms-web_1 | Removing web/install/index.php from production container

cms-web_1 | Starting cron

cms-web_1 | Starting webserver

cms-web_1 | AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using 172.19.0.4. Se

t the ‘ServerName’ directive globally to suppress this message

PS C:\xibo>

I am always getting this error.

Please help

mykac · November 8, 2019, 3:12pm

Never mind. I managed to resolve it.

First of all I have to move it in c:User/Xibo (I had c:Xibo), but then Mysql start restarting.
Then I put
command: “–innodb_use_native_aio=0”
but on the top of cms-db service definition in my docker-compose file instead on the bottom, first line under
image: mysql:5.6
And finally mysql stop restarting
Now everything working