Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 06 Oct 2017 18:22:19 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 222836] databases/mariadb102-server: Galera no longer works
Message-ID:  <bug-222836-13@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 222836
           Summary: databases/mariadb102-server: Galera no longer works
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: brnrd@freebsd.org
          Reporter: freebsd@darkain.com
             Flags: maintainer-feedback?(brnrd@freebsd.org)
          Assignee: brnrd@freebsd.org

In the MariaDB 10.2.7 package, WSREP=3DON functioned properly. In MariaDB 1=
0.2.9,
MariaDB exits execution very early on with no warnings/errors, and virtuall=
y 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=3D/usr/local/share/mysql'
171006 11:18:01 mysqld_safe unknown option '--lc_messages=3Den_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=3D'/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 instruct=
ions
2017-10-06 11:18:01 34426872832 [Note] InnoDB: Initializing buffer pool, to=
tal
size =3D 2G, instances =3D 8, chunk size =3D 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 forma=
t is
Barracuda.=20
2017-10-06 11:18:02 34426872832 [Note] InnoDB: 128 out of 128 rollback segm=
ents
are active.
2017-10-06 11:18:02 34426872832 [Note] InnoDB: Creating shared tablespace f=
or
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`

--=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-222836-13>