a year ago
Attempt #1 failed with service unavailable. Continuing to retry for 1m37s
Jun 29 11:54:38
Attempt #2 failed with service unavailable. Continuing to retry for 1m29s
Jun 29 11:54:50
Attempt #3 failed with service unavailable. Continuing to retry for 1m17s
Jun 29 11:54:54
Attempt #4 failed with service unavailable. Continuing to retry for 1m13s
Jun 29 11:55:02
Attempt #5 failed with service unavailable. Continuing to retry for 1m5s
Jun 29 11:55:18
Attempt #6 failed with service unavailable. Continuing to retry for 49s
Jun 29 11:55:48
Attempt #7 failed with service unavailable. Continuing to retry for 19s
Jun 29 11:55:48
Jun 29 11:55:48
1/1 replicas never became healthy!
Jun 29 11:55:48
Healthcheck failed!
2 Replies
a year ago
Can you share more about your service that is failing the healthcheck? What does it do?
a year ago
If your application does not start in 5 minutes then the healthcheck fails https://docs.railway.com/reference/healthchecks
The default timeout on healthchecks is 300 seconds (5 minutes). If your application fails to serve a
200status code during this allotted time, the deploy will be marked as failed.
This is what is happening in your errors