Bug #81313 Error message when open_binlog fails has wrong filename
Submitted: 4 May 2016 17:28 Modified: 5 May 2016 4:43
Reporter: David Gow Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.6 git / 5.7 git OS:Linux
Assigned to: CPU Architecture:Any

[4 May 2016 17:28] David Gow 
Description:
When binlog_error_action is set to IGNORE_ERROR, the message logged when opening the binlog fails always reports that it cannot use the file "(null)" for logging, rather than providing the real binlog filename.

How to repeat:
Start the server with binlog enabled and binlog_error_action=IGNORE_ERROR on a read-only or full filesystem. The error message in the log should be of the form:

"Could not use (null) for logging (error 0). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it."

Note that the filename given is "(null)" rather than the log filename.

Suggested fix:
Do not free 'name' and set it to NULL before writing the error in https://github.com/mysql/mysql-server/blob/5.7/sql/binlog.cc#L4827
[4 May 2016 18:32] MySQL Verification Team 
https://bugs.mysql.com/bug.php?id=79298
[5 May 2016 4:43] MySQL Verification Team 
Hello David Gow,

Thank you for the report.
This is duplicate of Bug #79298

Thanks,
Umesh