-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
500 error on fresh install (PHP Warning: preg_match_all(): Allocation of JIT memory failed) #5094
Comments
Try deleting the vendor directory and adding the composer.json file from the repo and then running composer update. |
Hi Luke, Just did that and then it throws the following error:
What do you make of that? |
See wikimedia/composer-merge-plugin#184. If you can, downgrade to Composer 1.x, if not then just remove that part of the composer.json file (note that this means that running composer update from your project root to pull in your plugin dependencies will not work) |
Thanks Luke... When I remove the vendor folder now and run
After this, the site doesn't load at all anymore (always 500 errors). |
Remove vendor folder & the modules folder and then run it again. |
Thank you, Luke. Now it fails with the following message:
Also, now the site is again dead... |
@maartenmachiels remove the parts of composer.json referencing the tests directory. |
Thank you Luke. This is what the terminal outputs after doing this:
The site itself is running on PHP 7.3.18, but it seems the PHP version of the terminal is on PHP 5.4. As this is a shared environment, I don't really have control over it. The site is back up again now, but the intermittent issues persist. This is what is present in the logs after the
Upon investigating the logs, I do see another error message. It is far less frequent, but it is there:
It sucks but I cannot set any specific PHP settings as this is a shared hosting environment. I can ask the provider to set that for me though, but that would be tomorrow. What do you think? |
@maartenmachiels honestly, I would move to a different host. Otherwise your best bet would be to find the PHP 7.3 executable on the server and run composer through that so that it downloads the right version of the dependencies for your server. |
Thanks for your advice Luke, I will contact the provider tomorrow and see if we can get that done... I will post my findings here as soon as I can. |
Update: problem solved! I just got off the phone with the provider. They set Even without running any further composer commands, the site now works without error. It seems that this one error triggered the other errors regarding unfound dependencies. I hope this can help others who might encounter the same issue. Thanks for your support, Luke! |
Hi,
I recently moved a site to a shared server that has roughly the same configuration as my previous server did. The problem is that every so often, an error 500 appears, intermittently and without a clear cause. As a test, I tried to do a clean install, but the errors seem to persist.
This is the stack trace:
When I Google these errors, it states that I should run the command
composer dump-autoload
in the project root, but of course there is no composer file in the root.Also, I think it's so strange that the problem is intermittent and happens in random pages and that it happens also with a clean install. Do you guys have a clue what might be wrong here?
Thanks in advance for helping me out.
The text was updated successfully, but these errors were encountered: