6/20/25 - DK0029 - Can’t create mysql dump

DevKinsta Bug Reports
1

Q: Date/Time this occurred (Provide your time zone also)
A: 2025-06-20 06:36 EST

Q: DevKinsta Version
A: 2.13.4.8833

Q: OS Version
A: macOS Sequoia 15.5

Q: Docker Desktop Version
A: 4.41.2 (191736)

Q: Were any error codes or messages observed? If so, what were they?
A: DK0029 - Can’t create mysql dump

Q: Detailed Description of the Problem
A: I’m trying to push changes I made to the local version of a Wordpress multisite installation to the staging environment (where I pulled the site from yesterday).

What I’ve tried so far:

  • Waiting and trying again later, as suggested in the Kinsta help doc for this error
  • Totally quitting and restarting DevKinsta
  • Confirming I am able to login via SSH
  • Running docker exec -it devkinsta_fpm /bin/rm /root/.ssh/known_hosts command

Logs

[2025-06-20 06:36:38.449] [error] SyntaxError: Unexpected non-whitespace character after JSON at position 622
    at JSON.parse (<anonymous>)
    at docker_handleDockerEventData (/Applications/DevKinsta.app/Contents/Resources/app.asar/main.prod.js:2:180714)
    at IncomingMessage.<anonymous> (/Applications/DevKinsta.app/Contents/Resources/app.asar/main.prod.js:2:516680)
    at IncomingMessage.emit (node:events:513:28)
    at IncomingMessage.emit (node:domain:489:12)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:297:9)
    at IncomingMessage.push (node:internal/streams/readable:234:10)
    at HTTPParser.parserOnBody (node:_http_common:131:24)
    at Socket.socketOnData (node:_http_client:542:22)
[2025-06-20 06:36:38.462] [error] Chunk value:  {"status":"exec_start: /bin/sh -c mysql -u root -p[retracted] -e \"SHOW DATABASES;\"","id":"db0b7b3735e3c74bba50c4356117e7945b2fdbbe769a87d0a53f5036df9720af","from":"kinsta/devkinsta_db:1.3.6","Type":"container","Action":"exec_start: /bin/sh -c mysql -u root -p[retracted] -e \"SHOW DATABASES;\"","Actor":{"ID":"db0b7b3735e3c74bba50c4356117e7945b2fdbbe769a87d0a53f5036df9720af","Attributes":{"execID":"f28a54a526fc03d86df719a00e07fbef5e50948f7017f42fbe7a3a4b15391bb7","image":"kinsta/devkinsta_db:1.3.6","name":"devkinsta_db","vendor":"kinsta"}},"scope":"local","time":1750415798,"timeNano":1750415798446851052}
2

Hello there :waving_hand:

Can you please check the following:

  • check wp-config.php and confirm that DOMAIN_CURRENT_SITE isn’t set to undefined or wrong domain
  • are you able to access the database via Adminer (in DevKinsta)?

If both of the above are OK, please paste the complete main.log file here and we’ll redact it for privacy after we download it because the current error you posted is not specific enough to draw any conclusions.

Kind regards!

3

Hi Vladimir,

To answer your questions:

  1. yes, it’s set correctly
  2. yes, i can see the database in DevKinsta Adminer

Logs attached.

main.log [redacted]

5

Can you please try the following as well:

  • Close DevKinsta (make sure it’s shut down)
  • Open Docker and delete containers only (not volumes) that start with devkinsta_ (don’t delete other containers not related to DevKinsta if you have them)
  • Start DevKinsta again, it should recreate containers
  • Try to push local to staging again

Let me know if that returns the same error.

6

Thank you. I deleted the containers while DevKinsta wasn’t running, and I’m getting the same result.

There was a password set on this environment, and I also tried removing that in case that was the issue. Same result.

Attached is my latest log file.

main.log [redacted]

9

Thank you for your reply @juliaset! We are escalating this with our development team to find out more information about what could be causing this error to occur. We will keep you updated.

In the meantime, please let us know if you have any questions.

Best regards

11

Hello @juliaset :waving_hand:

I’m sorry to hear none of the suggested methods worked.

I would like to try to replicate this issue locally, can I download your staging site on my devKinsta?