In the MariaDB 10.2.7 package, WSREP=ON functioned properly. In MariaDB 10.2.9, MariaDB exits execution very early on with no warnings/errors, and virtually no logs. This is specific to the FreeBSD port as MariaDB 10.2.9 is functioning properly on Debian Linux. `root@database:/var/db/mysql # service mysql-server start Starting mysql.` `cat database.err 171006 10:54:34 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql` That is the entire log, and then the process is terminated. Running `mysqld_safe` manually results in the following `root@database:/var/db/mysql # mysqld_safe 171006 11:18:01 mysqld_safe unknown option '--lc_messages_dir=/usr/local/share/mysql' 171006 11:18:01 mysqld_safe unknown option '--lc_messages=en_US' 171006 11:18:01 mysqld_safe Logging to '/var/db/mysql/database.err'. 171006 11:18:01 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql/var/db/mysql` `root@database:/var/db/mysql # cat database.err 171006 11:18:01 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql 171006 11:18:01 mysqld_safe WSREP: Running position recovery with --disable-log-error --pid-file='/var/db/mysql/mariadb-63-recover.pid' 2017-10-06 11:18:01 34426872832 [Note] /usr/local/libexec/mysqld (mysqld 10.2.9-MariaDB-log) starting as process 32515 ... 2017-10-06 11:18:01 34426872832 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2017-10-06 11:18:01 34426872832 [Note] InnoDB: Uses event mutexes 2017-10-06 11:18:01 34426872832 [Note] InnoDB: Compressed tables use zlib 1.2.8 2017-10-06 11:18:01 34426872832 [Note] InnoDB: Number of pools: 1 2017-10-06 11:18:01 34426872832 [Note] InnoDB: Using generic crc32 instructions 2017-10-06 11:18:01 34426872832 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M 2017-10-06 11:18:01 34426872832 [Note] InnoDB: Completed initialization of buffer pool 2017-10-06 11:18:01 34426872832 [Note] InnoDB: Highest supported file format is Barracuda. 2017-10-06 11:18:02 34426872832 [Note] InnoDB: 128 out of 128 rollback segments are active. 2017-10-06 11:18:02 34426872832 [Note] InnoDB: Creating shared tablespace for temporary tables 2017-10-06 11:18:02 34426872832 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2017-10-06 11:18:02 34426872832 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2017-10-06 11:18:02 34426872832 [Note] InnoDB: Waiting for purge to start 2017-10-06 11:18:02 34426872832 [Note] InnoDB: 5.7.19 started; log sequence number 1620300 2017-10-06 11:18:02 34426872832 [Warning] InnoDB: Skipping buffer pool dump/restore during wsrep recovery. 2017-10-06 11:18:02 34426872832 [Note] Plugin 'FEEDBACK' is disabled. 2017-10-06 11:18:02 34426872832 [Note] Server socket created on IP: '0.0.0.0'. 2017-10-06 11:18:02 34426872832 [Note] WSREP: Recovered position: 00000000-0000-0000-0000-000000000000:-1`
This is because mysqld_safe is mistakenly redirecting error log. https://jira.mariadb.org/browse/MDEV-14063
This ticket can be closed since the issue was fixed upstream.