Xibo MYSQL error

[wardag21]

Following an installation of Xibo on windows 2016 server 64bit running docker, we have come across an issue accessing the CMS default page via internet explorer.

Fatel Error - sorry this shouldn’t happen. SQLSTATE[HY000] [2002] php_network_getaddress: getaddrinfo failed: Try again

we can see from the docker ps command that the MySQL is constantly restarting every 60 seconds

anyone come across this previously ?

[wardag21]

cms-db_1 | 2018-10-22 23:52:37 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 | 2018-10-22 23:52:37 0 [Note] mysqld (mysqld 5.6.41) starting as process 1 …
cms-db_1 | 2018-10-22 23:52:37 1 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Plugin ‘FEDERATED’ is disabled.
cms-db_1 | mysqld: Table ‘mysql.plugin’ doesn’t exist
cms-db_1 | 2018-10-22 23:52:37 1 [ERROR] Can’t open the mysql.plugin table. Please run mysql_upgrade to create it.
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2018-10-22 23:52:37 1 [Note] InnoDB: Restoring page 0 of tablespace 0
cms-db_1 | 2018-10-22 23:52:37 1 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
cms-db_1 | 2018-10-22 23:52:37 1 [ERROR] InnoDB: space header page consists of zero bytes in data file ./ibdata1
cms-db_1 | 2018-10-22 23:52:37 1 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
cms-db_1 | 2018-10-22 23:52:37 1 [ERROR] Plugin ‘InnoDB’ init function returned error.
cms-db_1 | 2018-10-22 23:52:37 1 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
cms-db_1 | 2018-10-22 23:52:37 1 [ERROR] Unknown/unsupported storage engine: InnoDB
cms-db_1 | 2018-10-22 23:52:37 1 [ERROR] Aborting
cms-db_1 |
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Binlog end
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘partition’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘PERFORMANCE_SCHEMA’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_SYS_DATAFILES’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLESPACES’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN_COLS’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_SYS_FIELDS’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_SYS_COLUMNS’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_SYS_INDEXES’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLESTATS’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLES’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_FT_INDEX_TABLE’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_FT_INDEX_CACHE’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_FT_CONFIG’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_FT_BEING_DELETED’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_FT_DELETED’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_FT_DEFAULT_STOPWORD’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_METRICS’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_BUFFER_POOL_STATS’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE_LRU’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX_RESET’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_CMPMEM_RESET’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_CMPMEM’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_CMP_RESET’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_CMP’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_LOCK_WAITS’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_LOCKS’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘INNODB_TRX’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘BLACKHOLE’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘ARCHIVE’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘MRG_MYISAM’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘MyISAM’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘MEMORY’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘CSV’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘sha256_password’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘mysql_old_password’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘mysql_native_password’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] Shutting down plugin ‘binlog’
cms-db_1 | 2018-10-22 23:52:37 1 [Note] mysqld: Shutdown complete
cms-db_1 |
cms-db_1 | 2018-10-22 23:53:39 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 | 2018-10-22 23:53:39 0 [Note] mysqld (mysqld 5.6.41) starting as process 1 …
cms-db_1 | 2018-10-22 23:53:39 1 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
cms-db_1 | 2018-10-22 23:53:39 1 [Note] Plugin ‘FEDERATED’ is disabled.
cms-db_1 | mysqld: Table ‘mysql.plugin’ doesn’t exist
cms-db_1 | 2018-10-22 23:53:39 1 [ERROR] Can’t open the mysql.plugin table. Please run mysql_upgrade to create it.
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2018-10-22 23:53:39 1 [Note] InnoDB: Restoring page 0 of tablespace 0
cms-db_1 | 2018-10-22 23:53:39 1 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
cms-db_1 | 2018-10-22 23:53:39 1 [ERROR] InnoDB: space header page consists of zero bytes in data file ./ibdata1
cms-db_1 | 2018-10-22 23:53:39 1 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
cms-db_1 | 2018-10-22 23:53:39 1 [ERROR] Plugin ‘InnoDB’ init function returned error.
cms-db_1 | 2018-10-22 23:53:39 1 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
cms-db_1 | 2018-10-22 23:53:39 1 [ERROR] Unknown/unsupported storage engine: InnoDB
cms-db_1 | 2018-10-22 23:53:39 1 [ERROR] Aborting
cms-db_1 |

[DanBW]

Thank you for the screenshots and error logs. In the below link is a possible fix for the issue you are experiencing:

Ok, using docker for windows - and now?

Some installations of Docker on Windows have issues with the MySQL containers starting properly. The resolution is as follows. Down the existing containers (docker-compose down, adding -f as appropriate) Delete the shared/db directory completely. Edit the compose file you’re using and add command: --innodb_use_native_aio=0 to the cms-db service definition. Then bring the containers up per the guide.

If the fix does not resolve the issue, please let me know.

Many Thanks.

[wardag21]

Thanks Dan

i found this link yesterday

Fresh Xibo Docker Install - mysql database won’t start

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. [image] Anybody come acro…

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.

looks like the recommended action has done the trick, we are all operational now

[JohnA]

I may have been the only person that did not know where to add this command, but this is where it should go inside your docker-compose.yml file. (the # is a comment. Remove # it to use the command)

services:
  mysql:
    image: mysql:5.7
    # command: "--innodb_use_native_aio=0",
    # command: '--ignore-db-dir=lost+found'
    ports:

The above came from: https://github.com/docker-library/mysql/issues/365#issuecomment-364848383