restore backup mysql timeout

[jackc]

when restoring a backup, if you have a large database, there could be a timeout error resulting restore error, would like to see if it can be improved.

example:
a user backup has the following DBs

user_1 10MB
user_2 20MB
user_3 2GB
user_4 1MB
user_5 9MB

so when restoring database user_3, it may take up to 2 minutes import the sql file into the database.
if you have optimized my.cnf for your mysql server, and set the wait_timeout value less than 2 minutes, you will receive error of "mysql server gone away" when restoring database user_4 and user_5, resulting unsuccessful backup restoration.

for some reason DA seems to use the same mysql connection all the way when restoring DBs, so I would like to see if using seperate mysql connections for each DB restore possible.

 

[DirectAdmin Support]

Hello,

I'll add it to the versions system and look at the issue.

John

 

[jackc]

hi, new version solved the database restore timeout problem, but the database users still facing this same issue, so after restoration, the databases are restored, but the users would be missing, showing 0 users. and there are not errors showing on log.

 

[scsi]

You have to increase your interactive_timeout setting in your my.cnf file.

 

[jackc]

the idea of this fix is not to increase the timeout value besides it has nothing to do with interactive_timeout.
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

 

[scsi]

Says you....i had the same problem the other day and it does not happen anymore...anyways whatever..