0

I was developing a site for a migration on Acquia's free tier, but it turned out there wasn't enough space for all of the files. Since I can no longer use local development/acquia for development, I decided to migrate it all over to another host that I use.

Did my normal process of installing a clean site on the new server, and then copying the modules, themes, and file folders from the old dev site to the new dev site, and then importing the full database dump from the old database into the new database.

Boom, site is up and running. I go to clear the caches on the new dev site to finalize the migration and am met with the angry error "The mysite.com page isn’t working. mysite.com is currently unable to handle this request. HTTP ERROR 500".

After re-importing a few times and clearing the cache tables one at a time, I've learned that the cache_discovery table in particular is the culprit. Clearing all of the other cache tables works fine, but when I clear this one the site throws that error.

Anybody know what might be happening here? I never encountered anything like this in D7 and this is my first D8 build, so I'm not sure how to proceed.

Improve this question

2 Answers 2

Reset to default
2

Did my normal process of installing a clean site on the new server, and then copying the modules, themes, and file folders from the old dev site to the new dev site,

In D8 all information from annotations and yaml files are newly discovered on a cache rebuild. And your mix from the clean site install and the copied files did not fit together. This could be one file, which is left over from an older core or module version and you get this problem. So the solution is, to copy complete site archives or when updating remove the old code completely before replacing it.

Improve this answer
1
  • Yeah I guess the process just doesn't work for D8. Not sure why I did it that way anyway since the site archive makes way more sense. I had the feeling it was something to do with some of the yaml files, so it's good to hear that.
    – Mrweiner
    Commented Nov 18, 2016 at 8:58
1

Not sure what was wrong with the config above, but instead of going that route I just transferred over the entire site archive and it's now working. If you have this issue, just transfer a site archive instead.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.