| Bug #71783 | mysqldump silently quits when it encounters an error. | ||
|---|---|---|---|
| Submitted: | 20 Feb 2014 21:21 | Modified: | 21 Apr 2016 18:13 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: mysqldump Command-line Client | Severity: | S2 (Serious) |
| Version: | 5.6.17, 5.7.4 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[21 Apr 2016 18:13]
Paul DuBois
Posted by developer: Noted in 5.6.31, 5.7.13 changelogs. mysqldump failed silently with no error message when it encountered an error while executing FLUSH LOGS.
Description: mysqldump silently fails without any error message, and without completing a backup. For example, --flush-logs causes server to return an error, you'll not get an indication of failure, just an empty backup. How to repeat: Read the code. Assume mysql_refresh fails (it can, for various reasons). if (flush_logs || opt_delete_master_logs) { if (mysql_refresh(mysql, REFRESH_LOG)) goto err; verbose_msg("-- main : logs flushed successfully!\n"); }