[MDEV-8374] Debian: mysqld_safe Can't log to error log and syslog at the same time Created: 2015-06-25  Updated: 2015-11-17  Resolved: 2015-07-16

Status: Closed
Project: MariaDB Server
Component/s: Platform Debian, Scripts & Clients
Affects Version/s: 10.0
Fix Version/s: 10.0.21, 10.1.6

Type: Bug Priority: Critical
Reporter: Sergey Vojtovich Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-9140 log_error variable not used after upg... Closed

 Description   

mariadb-server-10.0 depends on mysql-common.
mariadb-server-10.0 provides /etc/mysql/conf.d/mysqld_safe_syslog.cnf, which has "syslog" option.
mysql-common in debian repo provides /etc/mysql/my.cnf, which has "log_error=" option.
mysql-common in mariadb repo provides /etc/mysql/my.cnf, which has no "log_error=" option.

As a result default debian installation has both "log_error=" and "syslog" options, causing a warning and ignores intended "syslog".
Default installation from mariadb repo works well though.

There was an idea to add something like "disable_log_error" to mysqld_safe_syslog.cnf, but then how do we distinguish between default "log_error" and one specified by user?



 Comments   
Comment by Sergey Vojtovich [ 2015-06-30 ]

monty, please review fix for this bug.

Comment by Otto Kekäläinen [ 2015-07-03 ]

svoj Can you please link the commit you made to this issue so that it is easy to track and review? Thanks

Comment by Sergey Vojtovich [ 2015-07-03 ]

Done.

Comment by Michael Widenius [ 2015-07-15 ]

Patch approved

Generated at Thu Feb 08 07:26:41 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.