a year ago
Attempt #1 failed with service unavailable. Continuing to retry for 4m49s
Attempt #2 failed with service unavailable. Continuing to retry for 4m48s
Attempt #3 failed with service unavailable. Continuing to retry for 4m46s
Attempt #4 failed with service unavailable. Continuing to retry for 4m42s
Attempt #5 failed with service unavailable. Continuing to retry for 4m34s
Attempt #6 failed with service unavailable. Continuing to retry for 4m18s
Attempt #7 failed with service unavailable. Continuing to retry for 3m48s
Attempt #8 failed with service unavailable. Continuing to retry for 3m18s
Attempt #9 failed with service unavailable. Continuing to retry for 2m48s
Attempt #10 failed with service unavailable. Continuing to retry for 2m18s
Attempt #11 failed with service unavailable. Continuing to retry for 1m48s
Attempt #12 failed with service unavailable. Continuing to retry for 1m18s
Attempt #13 failed with service unavailable. Continuing to retry for 48s
Attempt #14 failed with service unavailable. Continuing to retry for 18s
1/1 replicas never became healthy!
Healthcheck failed!
i am stuck in this issue for hours
I am trying to deploy a nodejs project(Typescript)
ⓘ Deployment information is only viewable by project members and Railway employees.
1 Replies
a year ago
You would want to check your deploy logs to figure out why your service hasn't started.
Took a quick look, you should not be using nodemon in production.