Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jun 2020 12:19:45 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 247413] databases/mariadb104-server: server won't start on clean install
Message-ID:  <bug-247413-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247413

            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@freebsd.org
          Reporter: ports@thelanman.net
             Flags: maintainer-feedback?(brnrd@freebsd.org)
          Assignee: brnrd@freebsd.org

Created attachment 215774
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D215774&action=
=3Dedit
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 runnin=
g on
added ZFS disks.=20

I have migrated my my.cnf into the new mysql/conf.d/server.cnf . My
/etc/rc.conf has:
mysql_enable=3D"YES"
mysql_dbdir=3D"/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 mysq=
l 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=3D'/data/db/mysqldat=
a/'

it starts with no issue. I kill the processes. Now, the rc.d script works f=
ine
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 r=
c.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 us=
ing
the same config more or less for years.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247413-7788>