Bug #79225 binlog range in error is incorrect
Submitted: 11 Nov 2015 9:26 Modified: 11 Nov 2015 10:09
Reporter: Daniël van Eeden (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:5.7.9/5.6/5.5/5.1 OS:Any
Assigned to: CPU Architecture:Any

[11 Nov 2015 9:26] Daniël van Eeden
Description:
Error:
Can't generate a unique log-filename ../log/binlog.(1-999)

This is ER_NO_UNIQUE_LOGFILE

This suggests that the binlog number is between 1 and 999, but it can be much larger.

How to repeat:
Inspect sql/share/errmsg-utf8.txt:2292 (ER_NO_UNIQUE_LOGFILE)

Suggested fix:
Change to the actual range or something like (1 - <max>)
[11 Nov 2015 10:09] MySQL Verification Team
Thank you for the bug report.