Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently, the server only outputs a generic error when there is a network communication error. For example:
2024-02-20 5:13:36 57058502 [Warning] Aborted connection 57058502 to db: 'test' user: 'test' host: '10.1.2.3' (Got an error reading communication packets)
To debug this, we have to go through a checklist of possible causes and use trial and error to debug. It would be more helpful if the error message specified exactly what the error was.