Database Reference
In-Depth Information
LOG: unexpected EOF on client connection
This error occurs when your application does not disconnect the Postgres database appro-
priately. It indicates that there was a connection loss between the application and the data-
base; this states that the connection was not clear and the problem still remains. The fol-
lowing example illustrates this situation:
app[postgres]: LOG: could not receive data from client:
Connection reset by peer app[postgres]: LOG: unexpected EOF
on client connection
heroku[router]: at=error code=H13 desc="Connection closed
without response" method=GET path=/crash
host=alphabeta.herokuapp.com dyno=web.1 connect=1ms
service=10ms status=503 bytes=0
heroku[web.1]: Process exited with status 1
heroku[web.1]: State changed from up to crashed
The recommended solution for this problem is to analyze the logs relating to your applica-
tion and identify the causes of this connection loss. Usually, this error is related to the code
that implements the database connection.
