7 months ago
My functional storefront was not active for the last few weeks to prevent unnecessary costs while launching the company. This back-end has been healthy and functional without issue to this point. I redeploy a previously functional back-end and receive the following message:
"====================
Starting Healthcheck
====================
Path: /health
Retry window: 12m0s
Attempt #1 failed with service unavailable. Continuing to retry for 11m49s
Attempt #2 failed with service unavailable. Continuing to retry for 11m38s
Attempt #3 failed with service unavailable. Continuing to retry for 11m26s
Attempt #4 failed with service unavailable. Continuing to retry for 11m12s
Attempt #5 failed with service unavailable. Continuing to retry for 10m54s
Attempt #10 failed with service unavailable. Continuing to retry for 8m28s
Attempt #11 failed with service unavailable. Continuing to retry for 7m48s
Attempt #12 failed with service unavailable. Continuing to retry for 7m8s
Attempt #13 failed with service unavailable. Continuing to retry for 6m28s
Attempt #14 failed with service unavailable. Continuing to retry for 5m48s
Attempt #16 failed with service unavailable. Continuing to retry for 4m31s
Attempt #17 failed with service unavailable. Continuing to retry for 3m51s
Attempt #18 failed with service unavailable. Continuing to retry for 3m10s
Attempt #19 failed with service unavailable. Continuing to retry for 2m30s
Attempt #20 failed with service unavailable. Continuing to retry for 1m50s
Attempt #21 failed with service unavailable. Continuing to retry for 1m10s
Attempt #22 failed with service unavailable. Continuing to retry for 30s
1/1 replicas never became healthy!
Healthcheck failed!"
What caused my previously healthy back-end to become unhealthy and fail the healthcheck? Nothing in my project has changed.
1 Replies
7 months ago
Hello,
Did you check the deploy logs for that failed deployment? looks like some issue with meilisearch -
https://railway.com/project/f7cf2c1f-8ef6-4d41-96ec-f7de14481e6c/service/6d6217a3-cbf7-490e-9805-016fa7defebc?environmentId=fdac6f8a-de44-444b-bb35-26b3cd4d6a43&id=db0aa95a-7aee-4394-96a5-0757c5aad526#deploy
Going forward it's good to remember that you can always check the deploy logs during a failing health check for clues!
Best,
Brody
Status changed to Awaiting User Response Railway • 7 months ago
Status changed to Solved brody • 7 months ago