We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I got many 500 internal server error when navigating throw the Aleph UI.
I found that sometimes, when the postgres stack reboot, it may cause the SQLAlchemy session to be invalid.
Precision, I only reproduce this bug using an aleph stack with oauth
Aleph version Aleph v4.0.2
Discourse subject
The only way I found to fix this error is to add the option pool_pre_ping in the SQLAlchemy initialization.
pool_pre_ping
SQLAlchemy
The text was updated successfully, but these errors were encountered:
With some debugging, we just found that this solution fix our problem (issue #4002) Solution: #4002 (comment)
Just set your ALEPH_DATABASE_URI and FTM_DATABASE_URI env vars (even if they just point to the defaults)
ALEPH_DATABASE_URI
FTM_DATABASE_URI
Sorry, something went wrong.
It seems after multiple days of tests that #4002 is not the solution. I keep having several 500 errors
Successfully merging a pull request may close this issue.
I got many 500 internal server error when navigating throw the Aleph UI.
I found that sometimes, when the postgres stack reboot, it may cause the SQLAlchemy session to be invalid.
Precision, I only reproduce this bug using an aleph stack with oauth
Aleph version
Aleph v4.0.2
Discourse subject
The only way I found to fix this error is to add the option
pool_pre_ping
in theSQLAlchemy
initialization.The text was updated successfully, but these errors were encountered: