Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Not a Bug
-
10.2.18
-
None
Description
Hi!
This issue MDEV-7110 has been fixed, it seems, in 10.1.6 – but on MariaDB 10.2.18 log_bin_basename is still not recognized:
2019-03-11 18:08:17 139891721672896 [ERROR] /usr/sbin/mysqld: unknown variable 'log_bin_basename=geo-master'
|
I wonder if the fix was somehow applied only to 10.1 branch, and not to trunk/master?..
One more quicktest (notice lack of log_bin_basename):
$ mysqld --version; mysqld --verbose --help | grep basename
|
mysqld Ver 10.2.18-MariaDB-log for Linux on x86_64 (MariaDB Server)
|
--log-basename=name Basename for all log files and the .pid file. This sets
|
'datadir'/'log-basename'-bin or 'datadir'/mysql-bin will
|
be used (the later if --log-basename is not specified).
|
We strongly recommend to use either --log-basename or
|
not specified then 'datadir'/'log-basename'.err or the
|
log-basename geo-master
|
This is a simple bug, but it forces us to use log_basename instead, and consequently script up a kludge to reset back log_error, the slow log, pid file locations... back to their previous values once we set up replication.
Attachments
Issue Links
- relates to
-
-
- Closed
-