Deployment failing
jeet-gangele
PROOP

3 months ago

I have pushed small code change and deployment is failing

$20 Bounty

6 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 brody 3 months ago


fra
HOBBYTop 10% Contributor

3 months ago

Can you share some logs?


marcel030nl
PRO

3 months ago

I have the same, I pushed a small change and now my container crashed.

When I reverted to the previous version (another image on docker hub from last week) it still crashes. What changed on Railway end?


fra
HOBBYTop 10% Contributor

3 months ago

can you share logs?


marcel030nl
PRO

3 months ago

It mentions "AH00534: apache2: Configuration error: More than one MPM loaded."

Notice that I build a new image with my changes (UI changes, CSS) and now I reverted to the image that has been running smooth since last week. And now it's failing to start. Weird?


marcel030nl
PRO

3 months ago

I moved back

FROM php:8.4-apache

to

FROM php:8.3-apache

and added CMD rm -f /etc/apache2/mods-enabled/mpm_event.* /etc/apache2/mods-enabled/mpm_worker.* && \

a2enmod mpm_prefork 2>/dev/null || true && \

apache2-foreground

instead of CMD ["apache2-foreground"] as a work around. But what happened on railway?


fra
HOBBYTop 10% Contributor

3 months ago

I don't think is railway, as far as I can see you didn't use a tag in your dockerfile, this mean it always takes the latest version, I can see that php:8.4 has been updated 4 days ago:
https://hub.docker.com/layers/library/php/8.4-apache/images/sha256-63d1df5ea11815a071a46ba2633fada567fd41397d45fb133b78d6f3bb483123?context=repo

it might be they have changed something and now the image works in a different way compared to the previous version.


Loading...