I’m looking into the error right now in the main.log.
I am getting this error after the dowload is complete.
Encountered an error in child process 7244: 23. rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1816) [generator=3.2.3]
What’s the OS/platform you’re working on? Would you be able to try creating a new site in DevKinsta, then send your full main.log in a DM so we can have a look?
There may be some specific rsync or other errors that could help narrow it down.
If you would like to DM me the log and sitename you’re trying to import, I can take a look and try to identify if that’s the case and which symlink may be the issue.
The log isn’t complete, I’m guessing due to the number of entries from the rsync process. There should be a rotated main.log.old file that has additional lines from the start.
However, it may not be required. Looking at your site files I see what I suspect is causing the problem.
Look in your ~/public directory and you’ll see “index.html.ovh.old” which is a broken symlink and serves no true purpose at this point.
Try deleting that from your site in MyKinsta and attempt to create the site again in DevKinsta.
Let me know how that goes!
@Maor_Benzvi I’m trying to see if I can reproduce this on a test site by setting incorrect root credentials.
I’m using Ubuntu so there are some differences, waiting for a Windows install to complete so I can better reflect your environment.
We’ve seen it once happen before though I’m not certain how it happened in this instance.
This case isn’t exactly the same as yours but does have what I think could help correct the database problem. https://community.kinsta.com/t/cant-connect-to-database/1061/4
If you’re able to open the docker console to the db container, checking the available databases and updating either the permissions or password for root is easy enough.
As I mentioned in my last message it could be caused by the failed first import.
@oluisrael11 Welcome! Typically the “something bad happened” error will have additional details in the main.log file that can help.
It can often be a permission issue where DevKinsta is running as the user rather than administrator, and doesn’t have access to update the hosts file.
Are you using Windows as well?
If so, try running DevKinsta as Administrator by right clicking its icon and selecting run as admin from the context menu that opens.
If you would like to open another thread and send me your main.log I’d be happy to take a look and continue the conversation there more in-depth.
Hi @Maor_Benzvi
If you could send me an updated version of your main.log from the successful site create yesterday, we may be able to identify more about the blank tables.
Having the tables but no rows within may indicate a problem with one of the early values being imported.
With the site having been imported into MyKinsta successfully, I wouldn’t suspect a corrupt table but it is possible.
I’ll share this with our dev team as well and see if they may have some additional thoughts, though the log would be really helpful.