-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial db migration failure causes trotto app to return 500 internal server error #63
Comments
Thank you for submitting this, @kentoku24! I think a lazy retry could work well. Did you try any of these solutions in your own branch? |
Im seeing the same issue. @kentoku24 , were you able to get it working? |
After trying one of the suggested fix im still getting the same error. Im not sure whats going on. Below is my repro case. this is my app.yml: Docker-compose: db: networks: Logs During Start UP go-links_web: When i go to the site: Web logs; go-links_web: |
Is there an update on the above issue? |
Hi @swapnachagam! We will work on this next week and provide examples around configuring this with docker-compose. |
The symptom and steps to reproduce:
Root cause:
When trotto app and postgres instance are written in one docker-compose file,
both are launched almost simultaneously.
Solution:
a: add health check to trotto instance, so it will eventually restarted, and DB migration after restart should success.
b: add retry capability to the initial database migration process.
c: inform users to make sure to launch database prior to trotto instance.
The text was updated successfully, but these errors were encountered: