You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the error stack trace, this is a PostgreSQL database connection issue. The main error is InterfaceError: connection already closed, indicating that the code is trying to use a database connection that has already been closed. The main possible causes are:
Database connection timeout
Database connection unexpectedly closed
Incorrect connection pool configuration
Connection management issues in asynchronous environments
uvicorn.error: Exception in ASGI h11_impl.py:411
application
Hi @thinker007 , do you mind sharing a bit about your hosting environment? I'm guessing your instance has been running for a while? Is it on your own machine, or in a separate cloud?
Unfortunately, this is an issue we've been tracking for a while. It's going to require a bit of refactoring to address it. In the meantime, restarting the service is usually sufficient for avoiding the problem. In the longer term, we're going to have to update our ORM or API layer completely so that we don't encounter this problem. There's a discussion here which highlights some of the technical issues.
After running for 9 days we got this error
From the error stack trace, this is a PostgreSQL database connection issue. The main error is InterfaceError: connection already closed, indicating that the code is trying to use a database connection that has already been closed. The main possible causes are:
Database connection timeout
Database connection unexpectedly closed
Incorrect connection pool configuration
Connection management issues in asynchronous environments
uvicorn.error: Exception in ASGI h11_impl.py:411
application
The text was updated successfully, but these errors were encountered: