Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.11
-
None
-
FreeBSD 11.1-RELEASE-p4 amd64
build from port databases/mariadb102-server
Description
Steps to reproduce on FreeBSD 11.1 amd64 box
cd /usr/ports/databases/maraidb102-server |
make install |
select only INNODB engine and GSSAPI_NONE |
service mysql-server onestart
|
killall -HUP mysqld
|
head /var/db/mysql/ibdata1 |
You will see a "Status information" here, instead of error_log file. It breaks database completely, mysqld will hung or crash in seconds depending on load
On production server also error_log file will be flooded with gigs of binary data which I think are actual data should be written into ibdata1
10.2.10 is not affected, 10.2.11 on Ubuntu 16.04 from official repo also isn't affected
Attachments
Issue Links
- duplicates
-
MDEV-14889 Server fails to start because of aria_log_control-file
- Closed
- is duplicated by
-
MDEV-14337 mysqld_safe may suppress error messages with --log-output=file
- Closed
-
MDEV-14644 MariaDB 10.2.11 breaks binary logging after nightly log cycle
- Closed
- relates to
-
MDEV-14488 logging not happening on spider branch builds
- Closed