-
-
Notifications
You must be signed in to change notification settings - Fork 590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pantheon ddev pull fails after download, during import. #670
Comments
Wow, that looks like it's trying to use a different database than "db" in the "db" container. Please check to see that the settings.php is in fact loading settings.local.php, where we overload it, and that the settings.local.php has our contents in it - it should say #ddev-generated in there. But I'm thinking that all happens after the db is loaded. One thing to try is to rm -r .ddev, and then do the I'm happy to take a look if it's appropriate to share with my pantheon account, randy at randyfay.com |
Well - I think you're on the right track because the settings.php doesn't have anything about the settings.local.php, nor is there a settings.local.php (did I mention this is a Drupal 7 site?) Still make sense to remove .ddev and re-config it? -mike |
It doesn't do any harm to do re-config. Doesn't do any harm to study it from the settings.php end either. I'm pretty baffled by that error message though. Almost sounds like you have a pantheon dump that is specifying a particular database name. One thing I'd try is doing a new archive/dump/backup of both files and db on Pantheon's end. |
At what point should the settings.local.php appear? During the Once it was complete, I did a I checked, and it looks like the DB was imported, so I manually created a settings.local.php file and now everything appears to be working. One caveat that may explain the weirdness: this site has some SQL views that get created via a custom drush command. I have had issues importing this database previously (I didn't think about that until today). It might make sense to just close this issue, as it is entirely possible the site's DB SQL views are to blame. |
It actually appears after the import of the db, and I don't think you're getting that far. sql views sounds like a great culprit! Again, if it's possible and you're willing to share the db or the pantheon site, I'll try it. I wonder if we need some extra permissions for the views? Is it possible the views refer to a different db? Thanks for all your work on this. |
My client isn't keen on sharing the codebase - sorry. The SQL Views have always been a bit of a pain to deal with - including some weird permission stuff. Would it explain the settings.local.php not being generated as well? |
Yes, the failure to load means that ddev never gets to the point where it generates the settings.local.php. It's a lot to ask, but if you know how to put together a random database that generates this, I'd love to figure out how to solve this. But it does seem like you've got it here. We can close this when it works for you, but my inexperience with sql views makes me insecure about the reason for this failure. Glad it's working for you though! |
I wish I could say that I had to the time to put together a quick DB for you, but I'm pretty swamped for the next few weeks... :( I can tell you that we have a drush command to create the SQL views that looks something like this:
Hopefully that's enough to get you going. |
Thanks! |
My bet is that this will be solved in #693 |
Closing this one unless we hear otherwise, assuming #693 solves it. Note that this was a D7 site though, which by default would not have the include of settings.local.php, which could cause this kind of breakage. Happy to reopen! |
Howdy! I just recreated this issue. It's (almost) exactly the same (The line that the error occurs on differs from the original poster's issue.):
Docker is running. I'm certain that the DB's name is "pantheon" – Pantheon's Connection Info > Database > DB Name says so. My organization is willing and able to share access to our Pantheon site/database/etc. In the meantime, I'm working through the notes above (and suggestions in other articles) to see if I can get the local copy of the site working correctly. Extra info that may or may not be relevant: We did not set up the Pantheon site ourselves. Instead we hired Kalamuna to migrate an existing site from Blackmesh to Pantheon. Part of that included getting CiviCRM to work correctly. That involved setting up some symbolic links or somesuch. Version:Mac OS 10.13.4 TexVet-Leistiko-iMac:texvet jonathanleistiko$ ddev version TexVet-Leistiko-iMac:texvet jonathanleistiko$ docker version Server: Complexity Rating: 2? |
@texvetadmin thanks for the report. If there's any possibility of sharing the pantheon site with me for debugging it would be marvelous. randy (at) randyfay.com. Does yours have any SQL views in it? |
I just shared our Pantheon site with you. |
Thanks for that! I'm able to recreate the issue. The problem line is
Since we GRANT ALL to the db user, I'm studying to try to figure out what we're missing here. |
Please try this @texvetadmin:
I see that you have a huge db and files there. If you want to just import the db you can If this works for you (works for me) we'll consider that as just a routine change. I do note these complaints on the file import, but neither macOS tar nor gnu-tar does any better on the tarball provided by pantheon:
|
I'm giving your recommended commands a go now. I'm up to "ddev pull" |
Short answer: It worked. Thank you! Longer answer: It failed. Boo! But it's totally an issue specific to the files. There's a file with a file name that's too long. I have to track it down and delete it.
I have little doubt that once I track that down (and other ridiculous files like that one), it'll work just fine. |
Opened drud/mariadb-local#55 to solve this generally. BTW @texvetadmin I don't think those long filenames actually cause a failure that would be in your way; take a look and see if most everything you need isn't there in sites/default/files. Mostly with big sites like that having every single one of the files is a waste. People have requested a |
Closing this as a duplicate of [https://github.com//issues/852](Use mysql root user for imports #852) (which was formerly https://github.com/drud/mariadb-local/issues/55). I'm pretty sure that when we start importing using the root-privileged mysql user this will be solved. |
@texvetadmin @ultimike I think both of your problems should be fixed in today's v0.19.0 release, and hope you'll be able to try it out and confirm. @texvetadmin thanks to your generosity in sharing your pantheon project I was already able to give a quick run on yours and it worked out fine. Thanks for that! |
What happened (or feature request):
I tried to do a ddev pull, got the following error:
I had just done a ddev start on an existing codebase that I hadn't used DDEV for previously.
What you expected to happen:
The pull to be complete.
How to reproduce this:
I could share the project with someone, I suppose...
Version: Please include the output of
ddev version
,docker version
and the project's .ddev/config.yaml.Anything else do we need to know:
Nothing comes to mind.
Related source links or issues:
I saw #466, but it doesn't sound like the same thing.
Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)
The text was updated successfully, but these errors were encountered: