3 months ago
Please revert to yesterday. Something happened today! i'm not able to deploy WP instances anymore, evenb working ones crash at redeploy.
Error: More than one MPM loaded...
Pinned Solution
3 months ago
This doesn't depend on Railway, have a look to this thread:
https://station.railway.com/questions/urgent-all-wordpress-sites-deployed-to-07dee2ef#c00z
5 Replies
3 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open itsrems • 3 months ago
3 months ago
Me neither, my backend isnt working and ive tried with different options and dns configs and nothing works, its or else a 404 error o a dns problem, or a not secure webpage.
3 months ago
This doesn't depend on Railway, have a look to this thread:
https://station.railway.com/questions/urgent-all-wordpress-sites-deployed-to-07dee2ef#c00z
3 months ago
hey @applicantsream @alexxdf28-hue
so this is actually a wordpress specific issue not railways fault. the MPM error youre seeing is because wordpress pushed an update that broke a bunch of deployments
@fra already linked the main thread about it but basically what happened is wordpress core update changed some apache config and now multiple MPM modules are trying to load at once which crashes everything
quick fix options:
pin your wordpress version to before the update (like 6.7.0 or whatever was stable yesterday)
check the dockerfile or build settings and make sure only one MPM module is loading
you might need to explicitly disable the extra MPM in your apache config
# add this to your apache config
LoadModule mpm_prefork_module modules/mod_mpm_prefork.so
# and make sure mpm_event and mpm_worker arent loading
the thread fra posted has more details and other people who got it working. this hit a ton of wp deployments today so youre not alone
let me know if you need help with the specific fix or want me to walk through the dockerfile changes
Status changed to Open itsrems • 3 months ago
3 months ago
Thanks @fra, that thread lead me to the right direction!
I used this as startup-command and issue has been resolved!
/bin/bash -lc " a2dismod mpm_event 2>/dev/null || true; a2dismod mpm_worker 2>/dev/null || true; a2enmod mpm_prefork 2>/dev/null || true; exec docker-entrypoint.sh apache2-foreground "
gtg backup!
anarchistmanifesto
hey @applicantsream @alexxdf28-hueso this is actually a wordpress specific issue not railways fault. the MPM error youre seeing is because wordpress pushed an update that broke a bunch of deployments@fra already linked the main thread about it but basically what happened is wordpress core update changed some apache config and now multiple MPM modules are trying to load at once which crashes everythingquick fix options:pin your wordpress version to before the update (like 6.7.0 or whatever was stable yesterday)check the dockerfile or build settings and make sure only one MPM module is loadingyou might need to explicitly disable the extra MPM in your apache config# add this to your apache config LoadModule mpm_prefork_module modules/mod_mpm_prefork.so # and make sure mpm_event and mpm_worker arent loadingthe thread fra posted has more details and other people who got it working. this hit a ton of wp deployments today so youre not alonelet me know if you need help with the specific fix or want me to walk through the dockerfile changes
3 months ago
i actually managed to fix it abt an hour ago since it was cloudflare's issue.
Status changed to Open chandrika • 3 months ago
Status changed to Solved chandrika • 3 months ago
