Stop readsb broken-pipe log spam from the aggregator decoder probe#104
Merged
Conversation
The decoder reachability probe did a bare connect+close on readsb's BEAST output, leaving queued bytes unread so readsb logged a broken-pipe error on every dashboard poll. Probe via nc -N (graceful shutdown+drain); fall back to the bare connect when nc lacks -N.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The aggregator status panel checks whether the local readsb decoder is reachable on every dashboard poll. It did this with a bare TCP connect-and-close to readsb's BEAST output port, which left readsb's queued bytes unread — so the kernel reset the connection and readsb logged a
Beast TCP output: Send Error: Broken pipeline on each poll, filling the journal whenever the web UI is open.The probe now closes the connection gracefully (shutdown-write, then drain until readsb closes its side), which readsb sees as a clean disconnect and logs nothing. It uses
nc -Nwhere available and falls back to the previous bare connect otherwise, so reachability detection is unchanged — only the log noise is gone.