• Resolved messiah2

    (@messiah2)


    Hi All,
    when I open the backup page, I see this warning:

    Mysqldump: The process “mysql -u ‘xxx’ -p’xxx’ -h ‘localhost’ ‘xxx’ –execute=”quit”” exceeded the timeout of 60 seconds.
    IMysqldump: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away

    Backup jobs seems to work fine and backup files are created, but I’m worried about database backup consistency.

    Is the backup process truncated by the timeout?
    How can I fix the timeout problem?

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    This indicates that the MySQLDump command is running into a timeout limit, but if your backups are working, it’s very likely the fallback php function is still working correctly.

    There are two options for correcting the timeout option, but the first is the most likely culprit, and it’s called max_execution_time. Assuming you are able to edit this option, you would usually do so in your php.ini file (some hosts have ways to do it differently). There is another timeout option tied directly to the MySQL command but I’m not sure that would even apply to MySQLDump. It’s worth checking with your host, though, if the problem persists.

    If the database backup is timing out, it’s also important to ensure your backups are complete. Unzip the backup files and compare the size against what is listed in the phpmyadmin or your MySQL manager for the database, and against the size of your files as listed in the file manager or via FTP.

    Let me know what you find out and if you need further help troubleshooting this, okay?

    Kat

    Thread Starter messiah2

    (@messiah2)

    Hi Kat,
    thanks for your reply.

    Actually, this is the value reported in my file “/etc/php5/apache2/php.ini”:

    max_execution_time = 30

    I don’t understand where to find the 60 seconds value

    exceeded the timeout of 60 seconds

    Thread Starter messiah2

    (@messiah2)

    I have also checked the output of “mysqldump” command and I have compared it with the backup file made by “BackUpWordPress”, and the size and the content are the same.

    At this time there is only that warning in the main backup page.

    Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    Interesting that the reported timeout limit is different, so it must be tied to something else within your php settings somewhere. I would recommend upping the max_execution_time to at least 120 if possible as that will also keep all the backups from coming close on that limit, which is fairly low.

    It’s good that the backups you have are complete, and I’ll take note of the error and see if we can improve error handling as a result. If you have further issues don’t hesitate to check back with me 😀

    Kat

    Thread Starter messiah2

    (@messiah2)

    it was necessary to change this mysql variable: “net write timeout”.

    Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    Interesting – I’m making a note of that. What did you end up changing yours to and what was it set at originally?

    Thanks,
    Kat

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Mysqldump timeout’ is closed to new replies.