The occasional ECONNRESET
The article discusses a technical issue involving a TCP connection reset error, known as ECONNRESET, occurring between two services on the same machine. The author provides a detailed examination of the behavior of both the server and client during data transmission, highlighting the conditions under which the error arises. The article sets the stage for further exploration of the issue in a subsequent part.
- ▪Two services are running on the same machine, with one opening a listening TCP socket and the other connecting to it.
- ▪The client experiences an ECONNRESET error while trying to read data from the socket, despite no other errors being logged.
- ▪The issue appears to be triggered when the client sends data to the server before attempting to receive data.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Movq |
| Canonical URL | https://movq.de/blog/postings/2026-05-05/1/POSTING-en.html |
| Publication time | Sun, 17 May 2026 17:09:36 +0000 |
| Retrieval time | 2026-05-17T17:33:20.866Z |
| Last seen | 2026-05-17T17:33:20.866Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
blog - git - desktop - contact The occasional ECONNRESET (part 1/2) 2026-05-05 Two services running on the same machine. One of them opens a listening TCP socket bound to localhost, the other one connects to that. They exchange data. Every now and then, the service that initiated the connection gets an ECONNRESET while reading data from the socket -- but no other errors show up in the logs, no crashes, nothing. What's going on? A reproducer in the "lab" What tcpdump sees What strace ./server sees What strace ./client --spam sees A first hypothesis The real-life scenario Next steps Go on to part 2. A reproducer in the "lab" Let's start with the "server", i.e. the service that opens the listening socket.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Movq.
Discussion
0 commentsMore from Movq
