Segmentation fault in cms_web (first run) [SOLVED]

Howdy.

I’m attempting a first installation, and I’m getting a segmentation fault from the cms_web container.

Docker version 18.03.0-ce, build 0520e2
on Ubuntu 17.10.

cms-db_1   | 2018-07-03 16:50:13 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-07-03 16:50:13 0 [Note] mysqld (mysqld 5.6.40) starting as process 1 ...
cms-db_1   | 2018-07-03 16:50:13 1 [Note] Plugin 'FEDERATED' is disabled.
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Memory barrier is not used
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Using Linux native AIO
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: Waiting for purge to start
cms-db_1   | 2018-07-03 16:50:13 1 [Note] InnoDB: 5.6.40 started; log sequence number 1626007
cms-db_1   | 2018-07-03 16:50:13 1 [Note] Server hostname (bind-address): '*'; port: 3306
cms-db_1   | 2018-07-03 16:50:13 1 [Note] IPv6 is available.
cms-db_1   | 2018-07-03 16:50:13 1 [Note]   - '::' resolves to '::';
cms-db_1   | 2018-07-03 16:50:13 1 [Note] Server socket created on IP: '::'.
cms-db_1   | 2018-07-03 16:50:13 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   | 2018-07-03 16:50:13 1 [Warning] 'proxies_priv' entry '@ root@e31c832e8ba7' ignored in --skip-name-resolve mode.
cms-db_1   | 2018-07-03 16:50:13 1 [Note] Event Scheduler: Loaded 0 events
cms-db_1   | 2018-07-03 16:50:13 1 [Note] mysqld: ready for connections.
cms-db_1   | Version: '5.6.40'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
cms-web_1  | Waiting for MySQL to start - max 300 seconds
cms-web_1  | MySQL started
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | New install
cms-web_1  | Provisioning Database
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Configuring Database Settings
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Setting up Maintenance
cms-web_1  | Protected Maintenance
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Segmentation fault (core dumped)
cms-web_1  | Segmentation fault (core dumped)

Just kidding!

I should have read the instructions. This error results from my having failed to set a MYSQL_PASSWORD in the config.env file. Just like the directions say.

Future newbies, beware!

1 Like