DevKinsta on Mac

DevKinsta Bug Reports
1

Q: Date/Time this occurred (Provide your time zone also)
A: Thu 22 Aug 22:03 (CEST)

Q: DevKinsta Version
A: 2.13.4

Q: OS Version
A: 14.6.1 (23G93)

Q: Docker Desktop Version
A: 4.33.0 (160616)

Q: Were any error codes or messages observed? If so, what were they?
A: DevKinsta: first DK0009, then just ‘errors’ before failing to start. DD: devkinsta_db keeps restarting.

Summary

This text will be hidden

Q: Detailed Description of the Problem
A: See last answer. Tried solution offered on ‘Troubleshooting - Error Codes - Kinsta® Docs’ page to no avail.

dockerD
dockerD2214×640 114 KB

2

Having the same issue. The DB just keeps restarting. Started with the update to DevKinsta 2.13.4.

My log from Docker shows repeating lines:

2024-08-22 17:38:43 2024-08-22 21:38:43+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-08-22 17:38:43 2024-08-22 21:38:43+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.17+maria~ubu2004 started.
2024-08-22 17:38:43 2024-08-22 21:38:43+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2024-08-22 17:39:44 2024-08-22 21:39:44+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.17+maria~ubu2004 started.
2024-08-22 17:39:44 2024-08-22 21:39:44+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-08-22 17:39:44 2024-08-22 21:39:44+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.17+maria~ubu2004 started.
2024-08-22 17:39:44 2024-08-22 21:39:44+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
3

Quick test (saw on another thread):

  • deleted db container.
  • restarted devkinsta app, and it recreates the container, but the problem still exists.
4

update #2.

  • I completely quit out of docker, and then it seems to work. So deleting the container AND completely quitting Docker seems to fix this issue.

update #3:

  • the problem reoccurs when I attempt to push a dev site to staging. I get the following error on a push:

Screenshot 2024-08-22 at 5.54.04 PM
Screenshot 2024-08-22 at 5.54.04 PM1496×948 83.1 KB

and then the DB container fails and it has to be completely recreated. This problem is reproducible.

The errors in main.log that pertain to this problem with the push are:

[2024-08-22 17:53:12.247] [error] SyntaxError: Unexpected non-whitespace character after JSON at position 1856
    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)
[2024-08-22 17:53:12.248] [error] Chunk value:  {"status":"exec_die","id":"b7adf6354a17b7a2261ba1c6f6216b3d44635d3f36f4109e31c04959e6ef8c36","from":"kinsta/devkinsta_fpm:1.3.6","Type":"container","Action":"exec_die","Actor":{"ID":"b7adf6354a17b7a2261ba1c6f6216b3d44635d3f36f4109e31c04959e6ef8c36","Attributes":{"desktop.docker.io/binds/0/Source":"/Users/kristopherlagreca/DevKinsta/public","desktop.docker.io/binds/0/SourceKind":"hostFile","desktop.docker.io/binds/0/Target":"/www/kinsta/public/","desktop.docker.io/binds/1/Source":"/Users/kristopherlagreca/DevKinsta/private","desktop.docker.io/binds/1/SourceKind":"hostFile","desktop.docker.io/binds/1/Target":"/www/kinsta/private/","desktop.docker.io/binds/2/Source":"/Users/kristopherlagreca/DevKinsta/logs","desktop.docker.io/binds/2/SourceKind":"hostFile","desktop.docker.io/binds/2/Target":"/www/kinsta/logs/","desktop.docker.io/binds/3/Source":"/Users/kristopherlagreca/DevKinsta/logs","desktop.docker.io/binds/3/SourceKind":"hostFile","desktop.docker.io/binds/3/Target":"/var/log/fpm/","desktop.docker.io/binds/5/Source":"/Users/kristopherlagreca/DevKinsta/kinsta","desktop.docker.io/binds/5/SourceKind":"hostFile","desktop.docker.io/binds/5/Target":"/kinsta","desktop.docker.io/binds/7/Source":"/Users/kristopherlagreca/DevKinsta/wp","desktop.docker.io/binds/7/SourceKind":"hostFile","desktop.docker.io/binds/7/Target":"/www/kinsta/wp/","desktop.docker.io/binds/8/Source":"/Users/kristopherlagreca/DevKinsta/temp","desktop.docker.io/binds/8/SourceKind":"hostFile","desktop.docker.io/binds/8/Target":"/www/kinsta/temp/","execID":"2ab08d78e68cc02109e2a131b7ff8de913579c93df38c63a2a37a1506cd35d8c","exitCode":"0","image":"kinsta/devkinsta_fpm:1.3.6","name":"devkinsta_fpm","org.opencontainers.image.ref.name":"ubuntu","org.opencontainers.image.version":"20.04","vendor":"kinsta"}},"scope":"local","time":1724363592,"timeNano":1724363592246354929}
{"status":"exec_die","id":"b7adf6354a17b7a2261ba1c6f6216b3d44635d3f36f4109e31c04959e6ef8c36","from":"kinsta/devkinsta_fpm:1.3.6","Type":"container","Action":"exec_die","Actor":{"ID":"b7adf6354a17b7a2261ba1c6f6216b3d44635d3f36f4109e31c04959e6ef8c36","Attributes":{"desktop.docker.io/binds/0/Source":"/Users/kristopherlagreca/DevKinsta/public","desktop.docker.io/binds/0/SourceKind":"hostFile","desktop.docker.io/binds/0/Target":"/www/kinsta/public/","desktop.docker.io/binds/1/Source":"/Users/kristopherlagreca/DevKinsta/private","desktop.docker.io/binds/1/SourceKind":"hostFile","desktop.docker.io/binds/1/Target":"/www/kinsta/private/","desktop.docker.io/binds/2/Source":"/Users/kristopherlagreca/DevKinsta/logs","desktop.docker.io/binds/2/SourceKind":"hostFile","desktop.docker.io/binds/2/Target":"/www/kinsta/logs/","desktop.docker.io/binds/3/Source":"/Users/kristopherlagreca/DevKinsta/logs","desktop.docker.io/binds/3/SourceKind":"hostFile","desktop.docker.io/binds/3/Target":"/var/log/fpm/","desktop.docker.io/binds/5/Source":"/Users/kristopherlagreca/DevKinsta/kinsta","desktop.docker.io/binds/5/SourceKind":"hostFile","desktop.docker.io/binds/5/Target":"/kinsta","desktop.docker.io/binds/7/Source":"/Users/kristopherlagreca/DevKinsta/wp","desktop.docker.io/binds/7/SourceKind":"hostFile","desktop.docker.io/binds/7/Target":"/www/kinsta/wp/","desktop.docker.io/binds/8/Source":"/Users/kristopherlagreca/DevKinsta/temp","desktop.docker.io/binds/8/SourceKind":"hostFile","desktop.docker.io/binds/8/Target":"/www/kinsta/temp/","execID":"d6b2469e24e2983e0d80c4bd071bde89dca084eb04e8b46ea1db404ff95470f2","exitCode":"0","image":"kinsta/devkinsta_fpm:1.3.6","name":"devkinsta_fpm","org.opencontainers.image.ref.name":"ubuntu","org.opencontainers.image.version":"20.04","vendor":"kinsta"}},"scope":"local","time":1724363592,"timeNano":1724363592246535262}

[2024-08-22 17:53:12.249] [info]  [terminalExec] Child process exited with code 0
[2024-08-22 17:53:12.249] [info]  [terminalExec] Child process exited with code 0
[2024-08-22 17:53:12.250] [info]  [NGINXConfigEditor] Loading content into editor: 
[2024-08-22 17:53:12.252] [info]  [NGINXConfigEditor] Loading content into editor: 
[2024-08-22 17:53:12.258] [info]  [PhpIniEditor] Loading content into editor: 
[2024-08-22 17:53:12.258] [info]  [PhpIniEditor] Loading content into editor: 
[2024-08-22 17:53:12.260] [info]  [editGlobalPhpIni] Getting content from  /www/kinsta/public/wells-college-association/.user.ini
[2024-08-22 17:53:12.260] [info]  [dockerUtil/getContainer] Get 'devkinsta_fpm' Docker container
[2024-08-22 17:53:12.282] [info]  [containerExec] Command 'test -f /www/kinsta/public/wells-college-association/.user.ini && echo $?' on devkinsta_fpm finished with exit code 0
[2024-08-22 17:53:12.326] [info]  [PhpIniEditor] Loading content into editor: 
[2024-08-22 17:54:11.142] [info]  [cancelSiteMaintenanceMode] Cancelling maintenance mode for site environment with id 9eaa022a-31bb-48c4-9232-9ccd4aebeab2.
[2024-08-22 17:54:11.180] [info]  [ProgressIndicator] { isFailed: false, isOpen: true }
[2024-08-22 17:54:11.203] [info]  [ProgressIndicator] { isFailed: false, isOpen: true }
[2024-08-22 17:55:11.338] [warn]  [cancelSiteMaintenanceMode] Request timed out, but the operation is most likely successful.
[2024-08-22 17:55:11.341] [info]  [ipc/sync/cancel] Push site sync canceled
[2024-08-22 17:55:11.380] [info]  [ProgressIndicator] { isFailed: false, isOpen: true }
5

I’m no expert, but I thinks I read somewhere in the community posts that deleting the container would not solve a problem like this.

There seems to be something wrong the the db, Docker logs show stuff like this:
2024-08-23 00:09:28 2024-08-22 22:09:28+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2024-08-23 00:10:19 2024-08-22 22:10:19+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.17+maria~ubu2004 started.
2024-08-23 00:10:19 2024-08-22 22:10:19+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2024-08-23 00:10:19 2024-08-22 22:10:19+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.17+maria~ubu2004 started.
2024-08-23 00:10:19 2024-08-22 22:10:19+00:00 [Note] [Entrypoint]: MariaDB upgrade not required

Not using a paid version to employ Docker Debug, but I don’t know if that would do any good either.

The image hierarchy shows says that critical vulnerabilities were found in base image from
mariadb:10.5, 10.5-focal, 10.5.17, 10.5.17-focal, 10.5.18, 10.5.18-focal and in the entire kinsta/devkinsta_db image.

I’m prepared to build everything again if need be, but is there an easier way to solve the problem?

DevKinsta can’t start and just shows me this:

dk2
dk21103×702 141 KB

6

Hello @klagreca2 and @mudguts :wave:

We’re very sorry for the inconvenience. Our team is aware of the issue and currently working on it.

The currently available solution is to open Docker, and delete all containers, volumes and images related to DevKinsta. Upon relaunching DevKinsta the updated images will be pulled, the new containers created and the volumes will be recreated. DevKinsta should then be able to launch. This will however result in the loss of all local site’s databases. This means all post/page content, and site configuration of all local sites that exist under your DevKinsta installation will be permanently deleted.

Our development team is looking into additional options to see if there is a way to resolve the issue while preserving data.

One thing you can try however is to delete all containers and images related to DevKinsta within Docker, but preserve the volumes. Then, try relaunching DevKinsta to see if that helps allow it to load. The database information should be preserved as that is stored within the devkinsta_db_dat volume.

Please let us know if this helps! We will also provide another update as soon as possible once we have more details to share regarding this matter.

We appreciate your patience while our team continues to look into solutions.

7

Thanks for the advice, Vladimir.

Tried the second option first, but DevKinsta came to a halt at the last stage of launching and just said ‘errors’ again.
Then I deleted everything.
All gone, but at least DevKinsta works again. Perhaps @klagreca2 has had better luck.

Would any backups I saved help me rebuild, do you think?

8

I’m sorry that this caused a loss of local data for you. Can you please tell me what is the format of backups you have so I can assess whether a functional restore is possible?

9

Yes. I’ve used different plugins for this: UpdraftPlus (to Google Drive), Duplicator, and All-in-One WP Migration (both to local hard drive). All are test sites.

10

:wave:

I’m not an expert in using those plugins but you should be able to select local files from your machine and use them to restore the site. I don’t see an obstacle in that process. Depending on your operating system and whether it can communicate with devKinsta filesystem, you might be able to extract and manually copy the files to restore sites and then import database(s) manually via phpMyAdmin or wp-cli.

11

I managed to restore one of the test sites using a package I’d created with Duplicator Lite. It worked perfectly by overwriting the newly created DevKinsta’s database.
However, if I want to restore another backed-up site to another ‘new’ DevKinsta site, it looks like I’ll have to add a new database (database name, user name, and password). Can that be done in Adminer, and if so, how?
Hope this isn’t too much to ask.

12

My fears were uncalled for, Vladimir. By creating a new site in DevKinsta a new database is also created, though it looks like the user name and password are the same.
I repeated the process of replacing the contents of the new site’s folder with a different backup I had made with Duplicator, and it worked! That is, I have already restored two of the sites I deleted to get DevKinsta to launch again.
So, all good. Thanks again for your support.

13

Hi @mudguts! Thank you for your reply!

I am glad to see that Vladimir was able to assist you with this matter!

If you do have any questions in the future please don’t hesitate to open a new thread on the forum!

Best regards