Bug #50083 error-log and syslog conflict in mysqld_safe is not reported to the log file
Submitted: 5 Jan 2010 9:45
Reporter: Oli Sennhauser Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: General Severity:S3 (Non-critical)
Version:>= 5.1.20 OS:Any
Assigned to: CPU Architecture:Any

[5 Jan 2010 9:45] Oli Sennhauser
When I configure in the [mysqld_safe] section error-log and syslog concurrently this is a conflict (currently).

As stated in this bug:


it is reported. Unfortunately to the wrong output channel. So I cannot see the conflict when I use any start/stop wrapper (for example mysql.server) as most customers possibly do.

How to repeat:
# my.cnf

log-error     = error.log

/etc/init.d/mysql start

Suggested fix:
Changing the mysqld_safe as follows helps:

364   if [ $want_syslog -eq 1 ]
365   then
366     # User explicitly asked for syslog, so warn that it isn't used
367     logging=file   <-- new!
368     log_error "Can't log to error log and syslog at the same time.  Remove all --log-error configuration options for --syslog to take effect."
369   fi