Q: Date/Time this occurred (Provide your time zone also)
A: Feb 8 2023
Q: DevKinsta Version
**A: Version 2.9.0 (2.9.0.6039) **
Q: OS Version
A: 12.6
Q: Docker Desktop Version
**A: 3.6.0 (3.6.0.5487) **
Q: Were any error codes or messages observed? If so, what were they?
A: when just trying to pull database from live server
Q: Detailed Description of the Problem
**A: pulling the database constantly give me this error
**
Hello @monofrio 
Welcome to DevKinsta community!
Thank you for reaching us out!
That DK0029 error (during that process - pull/import site from MyKinsta) means DevKinsta is unable to create a MySQL dump on the remote / host server.
To check it further, please kindly check the main.log file on your computer (open it with your local text editor) and locate/search for “DK0029” .You can check here to see how to see/get that main.log file.
Similar to this case discussed here, if it’s showing something like this:
[error] Error - DK0029: MYSQL_DUMP_COMMON: Error (3): {mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' when dumping table `any_wp_table` at row: XXX
then you can then reach out to our support ( via chat from my.kinsta.com ) and please ask them to temporarily increase the " max_allowed_packet " value (let’s say to 64M) for the [mysqldump] section of your site in question (hosted on our Kinsta server).
In case you’re experiencing any issues to read the main.log , please send that main.log file to me (via DM/PM), so I can check and review that DK0029 error in there.
After that, you may want to give it a try to pull / import that site in question, and see if it’s no longer throwing DK0029 error message.
Cheers,
Agus
I did have the original error in my log, and had support increase but I’m I’m now coming up with this error code when pulling from live: Error DK0066
Error - DK0066: IMPORT_DB_DUMP: Error (1): VERROR 1153 (08S01) at line 1150: Got a packet bigger than ‘max_allowed_packet’ bytes
I resolved this by updating my.cnf file within the docker devkinsta_db database container. Added max_allowed_packet=64M and was able to pull the database down.
You will also need to install nano text editor into the local docker container to update the file.
example found here: How to Edit post_max_size in PHP Configuration - #3 by AlexM
Heya @monofrio ,
Thank you for your reply and update!
Yeah, I just checked and could see that you reached out to our support team and asked them to increase the max_allowed_packet to 64M on your r3 site (but you then got another error code DK0066).
The support engineer also provided you the link to our doc of that error code and confirmed that the Database of your site on the server side is running fine. So there was likely an issue on the DevKinsta side - and in this case, as you’ve already found out the issue (as also mentioned in the error message you shared, about IMPORT_DB_DUMP and max_allowed_packet), that you solved it by adding the max_allowed_packet=64M line to the /etc/mysql/my.cnf file within the devkinsta_db docker’s DB container on you local computer! 
Thank you for sharing your solution here for this case, and this should help other users in the future (in case they’re experiencing similar case).
Cheers,
Agus
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.