a year ago
I have tried redeployment and rollback but it always fails in Network Healcheck
Error: healthcheck failure
Pushing [=====================> ] 33.01MB/75.53MB 530d58a932a2
Layer already exists 66f0b79a05aa
Pushing [=======================> ] 35.24MB/75.53MB 530d58a932a2
Pushed 28473ff54ca8
Pushing [========================> ] 36.85MB/75.53MB 530d58a932a2
Pushing [=========================> ] 38.53MB/75.53MB 530d58a932a2
Layer already exists fb79d2807a48
Layer already exists 3406bbfac350
Pushing [==========================> ] 40.75MB/75.53MB 530d58a932a2
Pushing [============================> ] 42.98MB/75.53MB 530d58a932a2
Layer already exists def31a062fe8
Pushing [=============================> ] 44.65MB/75.53MB 530d58a932a2
Layer already exists 931b7ff0cb6f
Pushing [===============================> ] 46.88MB/75.53MB 530d58a932a2
Pushing [================================> ] 48.55MB/75.53MB 530d58a932a2
Pushing [=================================> ] 50.22MB/75.53MB 530d58a932a2
Pushing [=================================> ] 51.34MB/75.53MB 530d58a932a2
Pushing [===================================> ] 53.01MB/75.53MB 530d58a932a2
Pushing [====================================> ] 54.68MB/75.53MB 530d58a932a2
Pushing [=====================================> ] 56.35MB/75.53MB 530d58a932a2
Pushing [======================================> ] 58.02MB/75.53MB 530d58a932a2
Pushing [=======================================> ] 60.25MB/75.53MB 530d58a932a2
Pushing [=========================================> ] 62.48MB/75.53MB 530d58a932a2
Pushing [==========================================> ] 64.15MB/75.53MB 530d58a932a2
Pushing [===========================================> ] 65.8MB/75.53MB 530d58a932a2
Pushing [============================================> ] 67.47MB/75.53MB 530d58a932a2
Pushing [==============================================> ] 69.7MB/75.53MB 530d58a932a2
Pushing [===============================================> ] 71.93MB/75.53MB 530d58a932a2
Pushing [================================================> ] 73.57MB/75.53MB 530d58a932a2
Pushing [=================================================> ] 75.22MB/75.53MB 530d58a932a2
Pushing [==================================================>] 76.07MB 530d58a932a2
Pushed 530d58a932a2
219db22e-abd4-4ef4-b49f-1cc4eca63217: digest: sha256:4a550edd84b7ba50802fdd59bf2912f4997ca658642a3fbf121a99ee964b6dd0 size: 3253
Publish time: 9.71 seconds
====================
Starting Healthcheck
====================
Path: /web/health
Retry window: 5m0s
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 status 502. Continuing to retry for 4m52s
Attempt #5 failed with status 500. Continuing to retry for 4m40s
Attempt #6 failed with status 500. Continuing to retry for 4m20s
Attempt #7 failed with status 500. Continuing to retry for 3m46s
Attempt #8 failed with status 500. Continuing to retry for 3m12s
Attempt #9 failed with status 500. Continuing to retry for 2m39s
Attempt #10 failed with status 500. Continuing to retry for 2m5s
Attempt #11 failed with status 500. Continuing to retry for 1m32s
Attempt #12 failed with status 500. Continuing to retry for 58s
Attempt #13 failed with status 500. Continuing to retry for 24s
1/1 replicas never became healthy!
Healthcheck failed!
ⓘ Deployment information is only viewable by project members and Railway employees.
9 Replies
a year ago
Did this issue happen recently? Did you change anything within your project? We will need more information to debug here.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
It failed on Thursday or Friday, when you had the problem on your servers, from then on it no longer worked, the application has been running for 2 months and had not failed, a month ago it was updated but it continued to work correctly, I created a new environment and there it does load, but I don't have all the data that is in it.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Hi there,
The Healthcheck is failing, but the deployment steps succeed. Please try to remove the Healthcheck by setting the Healthcheck Path to blank.
Regards,
Christian
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
its deployment but I do not have access to the application via http: https://odoo-production-7854.up.railway.app/
Attachments
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Had a quick look at the deploy logs. It looks like there are a number of errors related to the modules you use in Odoo. Did you make any configuration changes, or changes to the modules you use in Odoo, recently?
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
No changes as such, I have been adding information to the CRM, and I only changed the password that came by default, but that has been going on for more than 10 days and it worked perfectly,
When it failed, the apps were paused because I had set a usage limit and increased it, I tried to deploy them, but there was a failure on their servers and it couldn't be done, the next day I deployed Typebot, but Chatwoot gave me the same error as Odoo, I waited until Saturday Since I thought it was probably part of the same failure of their servers, on Saturday I was able to deploy Chatwoot but not Odoo, which continues with the same failure
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Since the TorreyStore environment works as expected, this is not likely to be an issue related to Railway's platform, but rather to be a configuration issue or an issue with a module.
Assuming `TorreyStore` is your staging environment, and given that it works and you've been able to deploy to it and you can reach your staging URL, you can try to sync to the Production environment from `TorreyStore` by clicking the Sync button in the top right of the canvas. That will allow you to copy the configuration to rule out any service configuration to be at fault here.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
Hello, I have synchronized everything and all the instances have crashed, but then I redeployed and it came back to life, thank you very much for all the help, now I just backup the data and we continue adding more.
Thanks and regards
Status changed to Awaiting Railway Response Railway • about 1 year ago
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved christian • about 1 year ago