2 years ago
These are the build logs
Attempt #1 failed with service unavailable. Continuing to retry for 4m59s
Attempt #2 failed with service unavailable. Continuing to retry for 4m58s
Attempt #3 failed with service unavailable. Continuing to retry for 4m56s
Attempt #4 failed with service unavailable. Continuing to retry for 4m52s
Attempt #5 failed with service unavailable. Continuing to retry for 4m44s
Attempt #6 failed with service unavailable. Continuing to retry for 4m28s
Attempt #7 failed with service unavailable. Continuing to retry for 3m58s
Attempt #8 failed with service unavailable. Continuing to retry for 3m28s
Attempt #9 failed with service unavailable. Continuing to retry for 2m58s
Attempt #10 failed with service unavailable. Continuing to retry for 2m28s
Attempt #11 failed with service unavailable. Continuing to retry for 1m58s
Attempt #12 failed with service unavailable. Continuing to retry for 1m28s
Attempt #13 failed with service unavailable. Continuing to retry for 58s
Attempt #14 failed with service unavailable. Continuing to retry for 28s
1/1 replicas never became healthy!
Healthcheck failed!
ⓘ Deployment information is only viewable by Project members and Railway admins.
8 Replies
2 years ago
Here are the build logs and deployment logs
Attachments
2 years ago
Sorry for the inconvenience, this has now been fixed, please try deploying a new Odoo template.
Status changed to Solved Railway • almost 2 years ago
2 years ago
It's up and running thanks but where can I find my login credentials, in the environment variables they are not present
2 years ago
Thanks for the support, I think you can close this thread
2 years ago
If I recall correctly Odoo may need more memory than the trial plan allows for, if Odoo crashes again it would likely be because of the lack of memory, you would need to upgrade to the Hobby plan.