Hello @Daniel_Martin 
I will try to answer to your 2 cases reported above as follow:
I looked at devkinstad_fpm trying to see the tables using the wp db commands but it couldnt’ access the db. Reason: ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
I’m still not sure yet if there’s something broken in that local WP site you just imported (so that it couldn’t connect to the local database server), or if the local DB server is not running properly.
Anyway, to check and test if the local DB server is actually running (and to check if the actual database and its tables in question are there or not), you could also check in the “devkinsta_db” docker’s container, with the “root” user and its password manually by doing the following:
-
On your Docker Desktop, click on the “devkinsta_db” container
-
Then, click on the “Inspect” tab, and locate for the
MYSQL_ROOT_PASSWORD, and copy the password shown there (e.g.: in your text editor or something). -
Then, click on the “Exec” tab, and there, type:
mysql -u root -p -
When you’re prompted to Enter the password, you can paste the password you’ve copied before (from step 2 above) - and see if you are able to login with it.
-
If you’re able to login with that mysql root user/password, you will be able to perform mysql command line ( such as:
show databases;to list all databases you have, then followed by:use yourdatabasenamehere;to use/change to that specific local database, and then you can type:show tables;that will show the existing tables in that database). Like the following screenshot I took from my Windows 11 machine for example:
Hopefully with the above, you will be able to see the DB’s tables you’re looking for (or if you just want to check them - via that SQL command lines on the devkinsta_db container)
And regarding the error in the main.log you shared before:
[2023-12-12 14:00:29.340] [warn] [terminalExec] Error: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1861) [generator=3.2.7]
[2023-12-12 14:00:29.479] [info] [terminalExec] Child process exited with code 23
[2023-12-12 14:00:29.481] [error] [downloadSite] Error while downloading files Error: Encountered an error in child process 1844: 23. rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1861) [generator=3.2.7]
[2023-12-12 14:00:29.522] [error] [ipcMainStep] Error in operation SITE_CREATION, step rsync: Error: Encountered an error in child process 1844: 23. rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1861) [generator=3.2.7]
I’m still unsure yet, but this could be caused by various issues, such as for example: broken symlinks (that are pointing to invalid paths/non-existing files/paths) - as I had noticed before with other customer/user here, CHMOD or files/folders permission issue, and/or something like that which was causing the import process to fail in DevKinsta (and returned with “Something bad happened” error).
If you could please share the most recent (newest) full main.log file to us, we may be able to check and review further and see what may be causing the error.
Also, could you please update you profile in this Community and set your MyKinsta Account URL
that will help us easily to open your correct MyKinsta account control panel when we need to check something on the server side when needed.
PS: About the last reply you had:
This may not be important but looking at our database on kinsta it uses latin1_swedish_ci instead of utf8mb3_general_ci
I don’t think that DB/tables’ collation is something that would cause the “Something bad happened” error above. We can take a look in your full main.log file for sure though.
Best regards,
Agus