[Bug 247413] databases/mariadb104-server: server won't start on clean install

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247413

            Bug ID: 247413
           Summary: databases/mariadb104-server: server won't start on
                    clean install
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: brnrd at freebsd.org
          Reporter: ports at thelanman.net
             Flags: maintainer-feedback?(brnrd at freebsd.org)
          Assignee: brnrd at freebsd.org

Created attachment 215774
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215774&action=edit
mariadb server.cnf

This is weird.

FreeBSD 11.3 installs on a AWS AMI. I use ansible to deploy configurations. I
have now replicated this on 2 clean installs that did not have MariaDB
installed at all and no filesystems outside of a basic UFS / . DB is running on
added ZFS disks. 

I have migrated my my.cnf into the new mysql/conf.d/server.cnf . My
/etc/rc.conf has:
mysql_enable="YES"
mysql_dbdir="/data/db/mysqldata"

On a clean install if I run:
/usr/local/etc/rc.d/mysql-server start

it's showing that it builds my new tables, etc...and log files and the mysql DB
get created. However, after about 5 seconds it exits. No MariaDB running. I can
run 'start' multiple times and the same thing.

If I run:
cd '/usr/local' ; /usr/local/bin/mysqld_safe --datadir='/data/db/mysqldata/'

it starts with no issue. I kill the processes. Now, the rc.d script works fine
and starts immediately.

I have attached my server.cnf. The other config files 2 are stock. It seems
running mysqld_safe sets something somewhere or caches something that the rc.d
script isn't picking up or setting?

Outside of adding the 'innodb_doublewrite', 'innodb_flush_method', and
'innodb_log_group_home_dir' options per the comments for ZFS I have been using
the same config more or less for years.

-- 
You are receiving this mail because:
You are the assignee for the bug.