Hi Michael,
Thank you for your reply and update! Usually by uninstalling and re-installing everything from scratch should work fine.
actually deleted the whole folder by accident hope thats not a problem.
That’s OK, I went ahead and have re-created that “private” folder in your Live site’s root folder (that got deleted by accident previously).
COuldnt delet the backup.sql as some tool seems to produce this automatically.
Indeed that backup.sql file was created (dumped/imported from your existing database on the server side) automatically as the part of the process when importing site from MyKinsta to your local computer (DevKinsta). That backup.sql file on the ~/public folder could be deleted via SSH / SFTP , but when you try to import the site again, that file will be re-created.
I’ve also checked that main.log file you provided (note: I moved it to our internal note/non-public access as it contains sensitive information) and so far noticed the following:
[2023-10-09 17:10:14.915] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-10-09 17:10:15.122] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-10-09 17:10:15.487] [info] [terminalExec] Child process exited with code 0
[2023-10-09 17:11:35.933] [info] [containerExec] Command ‘chown -R www-data:www-data /www/kinsta/public/space44’ on devkinsta_fpm finished with exit code 0
from the part of the log above, it looks like the live site’s files have been downloaded completely to your local computer and no issue with it (as you mentioned that it showed fully downloaded 4.57Gb/4.57Gb).
Then the log continued to show the following import database process (from that dumped /public/space44/backup.sql file which has been downloaded to your local container on your computer ),
but somehow the process couldn’t be completed and returned with DK0066 error code, when it was in the process of importing the backup.sql file to your local docker’s container on your computer:
[2023-10-09 17:11:35.938] [info] [importBackupToDb] Import db
[2023-10-09 17:11:35.940] [info] [dockerUtil/getContainer] Get ‘devkinsta_fpm’ Docker container
[2023-10-09 17:25:07.331] [info] [containerExec] Command ‘mysql -h devkinsta_db -u root -p****** SPACE44 < “/www/kinsta/public/space44/backup.sql”’ on devkinsta_fpm finished with exit code 1
[2023-10-09 17:25:07.354] [error] Error - DK0066: IMPORT_DB_DUMP: Error (1): SERROR 2013 (HY000) at line 38387927: Lost connection to MySQL server during query
[2023-10-09 17:25:07.418] [error] [ipcMainStep] Error in operation SITE_CREATION, step rsync: Error - DK0066: IMPORT_DB_DUMP: Error (1): SERROR 2013 (HY000) at line 38387927: Lost connection to MySQL server during query
As far as I could see, there’s no issue with your Live site’s database on our server (and there’s no timed out issue during the DB dump process into that backup.sql file - that’s stored in your ~/public folder), and as we can see above, the DB import process actually failed (DK0066) during the DB Dumped file import process to your local computer (Docker’s container) / not on the server side.
I suspect it might be because of your database is too large (as I noticed via phpMyAdmin tool, your live site’s database size is about ~10 GB), and somehow the import process on your local computer/container then timed out (lost connection to MySQL server during query). And from the above error message, the DB Import lost the connection when it tried to read the line 38387927 (that’s really huge lines, more than 38 million or so).
I also noticed the following large tables (with millions of rows), perhaps when possible if any old data can be deleted/removed to reduce unwanted large DB’s tables/rows as much as possible (may want to consult with your web programmers/developers first to assist you with that database tables’ optimization)
that way, your database size could be reduced significantly and the DB (.sql) then may be able to be imported properly to your local computer’s DB container.
Also, for testing purpose (and to compare the result), can you please also try to import your other site (that’s small in size, i.e: “sebastian” site perhaps that’s around ~1GB) to your local computer with DevKinsta, and see if the site import process could be completed properly without any errors ?
If that other site’s import process could be completed just fine, then most likely the issue here is really something due to the DB size issue as mentioned above (with your “SPACE44” site) which may need to be optimized first.
regards,
Agus
. Can you please let us know if rebooting your Mac solves the issue?
