I have a nightly backup configured and have been receiving the following type of error message for the past several months, the details vary from night to night:
• 2:01:31 AM : ERROR: Failed to backup “p1370_capi_t3_prac” database with “Full” backup type: mysqldump: [Warning] Using a password on the command line interface can be insecure. mysqldump: Couldn’t execute ‘show create table capiprogress’: Got an error writing communication packets (1160)
The specific schema and table causing the error is different every evening. Sometimes multiple errors are reported, most evenings just one.
I never receive any errors when I manually run mysqldump.
The errors appear to be MySQL errors, but the MySQL error log doesn’t report any errors.
The symptoms you described — particularly the error:
Got an error writing communication packets (1160)
— are most likely related to a network issue.
It’s possible that you don’t encounter this error when running mysqldump manually because the problem only occurs under specific nighttime conditions.
Please note that SQLBackupAndFTP performs MySQL backups using standard mysqldump, without any special flags or advanced connection settings that could affect network behavior.
Thanks for your reply. It is possibly unrelated to the SQLBackupAndFTP program, howwever…
We have a nightly batch process for mysqldump that starts every night 30 minutes after the SQLBackupAndFTP backup job, and that batch process never fails.
The Windows Event Viewer contains an error message associated with the error withing SQLBackupAndFTP process, and the MySQL error log files are not reporting any errors. Are you sure this isn’t an issue for SQLBackupAndFTP?
is definitely generated by the mysqldump utility itself — not directly by SQLBackupAndFTP. You can verify this by searching for this exact message on the web.
In order to see the full commands (with all used parameters), click Tools –Advanced Log… and enable the Trace level. Next, perform a backup or restore and search for the substring “Mysqldump parameters” or “The MySQL command” in the logs. These lines will contain all executions of the
mysql.exe
and
mysqldump.exe
utilities.
These lines will show the exact command-line executions of mysql.exe and mysqldump.exe with all used parameters. That can help determine whether there’s anything unusual in the way the backup is triggered.
Let me know what you find, and I’d be happy to help analyze the log details.
