Skip to content
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

BUG: SQLAlchemy error #4088

Open
zzzepezzz opened this issue Jan 3, 2025 · 2 comments
Open

BUG: SQLAlchemy error #4088

zzzepezzz opened this issue Jan 3, 2025 · 2 comments
Labels
bug Things that should work, but don’t triage These issues need to be reviewed by the Aleph team

Comments

@zzzepezzz
Copy link

zzzepezzz commented Jan 3, 2025

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.

@zzzepezzz zzzepezzz added bug Things that should work, but don’t triage These issues need to be reviewed by the Aleph team labels Jan 3, 2025
@zzzepezzz
Copy link
Author

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)

@zzzepezzz
Copy link
Author

It seems after multiple days of tests that #4002 is not the solution. I keep having several 500 errors

@zzzepezzz zzzepezzz reopened this Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Things that should work, but don’t triage These issues need to be reviewed by the Aleph team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant