Hi!
I’ve got Xibo 2.0.1 docker installed on ubuntu 18.04, which was working just fine.
I needed to install php (outside docker), so I used the command
apt-get update && apt-get upgrade
After that I get the error
Fatal Error - sorry this shouldn't happen. SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name does not resolve
I’ve restarted Xibo and / or the server (without errors), but the SQL-error is still there.
I hope you can help me.
thanks!
The command
docker-compose logs
gives:
cms-db_1 | 2019-04-22 12:35:59 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-04-22 12:35:59 0 [Note] mysqld (mysqld 5.6.43) starting as process 1 …
cms-db_1 | 2019-04-22 12:35:59 1 [Note] Plugin ‘FEDERATED’ is disabled.
cms-db_1 | mysqld: Table ‘mysql.plugin’ doesn’t exist
cms-db_1 | 2019-04-22 12:35:59 1 [ERROR] Can’t open the mysql.plugin table. Please run mysql_upgrade to create it.
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Compressed tables use zlib 1.2.11
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Database was not shutdown normally!
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Starting crash recovery.
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Reading tablespace information from the .ibd files…
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Restoring possible half-written data pages
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: from the doublewrite buffer…
cms-db_1 | InnoDB: Doing recovery: scanned up to log sequence number 1600607
cms-db_1 | 2019-04-22 12:35:59 1 [Note] InnoDB: Starting an apply batch of log records to the database…
cms-db_1 | InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
cms-db_1 | InnoDB: Apply batch completed
cms-db_1 | 2019-04-22 12:36:00 1 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2019-04-22 12:36:00 1 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2019-04-22 12:36:00 1 [Note] InnoDB: 5.6.43 started; log sequence number 1600607
cms-db_1 | 2019-04-22 12:36:00 1 [Note] Server hostname (bind-address): ‘*’; port: 3306
cms-db_1 | 2019-04-22 12:36:00 1 [Note] IPv6 is available.
cms-db_1 | 2019-04-22 12:36:00 1 [Note] - ‘::’ resolves to ‘::’;
cms-db_1 | 2019-04-22 12:36:00 1 [Note] Server socket created on IP: ‘::’.
cms-db_1 | 2019-04-22 12:36:00 1 [Warning] Insecure configuration for --pid-file: Location ‘/var/run/mysqld’ in the path is accessible to all OS users. Consider choosing a different directory.
cms-db_1 | 2019-04-22 12:36:00 1 [ERROR] Fatal error: Can’t open and lock privilege tables: Table ‘mysql.user’ doesn’t exist
I’ve deleted the db directory. Now I’m live again (without data)
