-
Notifications
You must be signed in to change notification settings - Fork 504
Loosing DB-connection on long inactivity #8959
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
Comments
It looks like we also saw "Internal Exception: org.postgresql.util.PSQLException: This connection has been closed" at #4416 but other than that, I'm not sure what's going on. @sergejzr you don't happen to be running AWS RDS are you? Somewhat recently we added some monitoring suggestions: https://guides.dataverse.org/en/5.11.1/admin/monitoring.html#aws-rds I guess I'm curious if you're doing any monitoring in particular for PostgreSQL and if you're seeing any spikes or patterns. |
I have no idea why this happens (lots of options), but maybe merging #8915 and activation of connection validation might help? |
Hi Philipp @pdurbin , |
@sergejzr sounds good. I don't think we have a way to reproduce this issue. Are you ok with closing it? You'd be very welcome to open a fresh one in the future, of course! |
What steps does it take to reproduce the issue?
We did not access the running dataverse for several weeks (due to illness and vacations). In the meantime the DB connection got lost and only a server restart helped.
on 4 or more weeks on inactivity
Any page

What happens?
Database connection gets lost and the whole site crashes. Only a server restart fixed the issue
To whom does it occur (all users, curators, superusers)?
anyone
What did you expect to happen?
Dataverse could catch lost connection exception and try to reconnect (at least several times).
Which version of Dataverse are you using?
v. 5.10.1 build 907-b844672
Any related open or closed issues to this bug report?
Any database issues, however I could not find exactly that one.
Screenshots:
The text was updated successfully, but these errors were encountered: