| Previous | Next |
| EAFNOSUPPORT | ENOPOLICY |
ECONNABORTED
ECONNABORTED indicates that a connection was terminated while the operating system was still handling it. Servers often encounter it from accept() when a client disconnects or a network condition removes a queued connection before application code obtains the new socket. It can also be reported by other connection-oriented operations.
For a listener, this does not normally mean that the listening socket is broken. The Linux accept() documentation specifically lists it as an error for an aborted connection and notes that Linux can surface pending network errors from the new connection differently from BSD systems. Robust server loops should classify it as an event for the individual attempt, preserve useful telemetry, and continue accepting unless a broader resource or configuration problem is visible.
What to capture
- Whether the error came from
accept(),connect(), read, or write. - The peer address if it was available, plus listener backlog and connection-rate metrics.
- Nearby timeout, proxy, TLS, and firewall events that could explain why the client disappeared.
Do not report the request as successfully handled merely because a connection reached the accept queue; application-level completion still requires its own protocol acknowledgement.
Linux accept(2) · BSD errno descriptions · POSIX connect()
Looking for a different code? Search another status or error code.