You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During a long duration APRS telemetry run of only a local faraday device using a Raspberry Pi 3 the APRS server stopped due to [Errno 32] Broken pipe.
Problem Explanation
I allowed a single Faraday (local) to log telemetry and upload to APRS but the APRS stopped after a few days. Investigating into why is stopped I noticed that the tmux screen running aprs.py was showing errors:
Summary
During a long duration APRS telemetry run of only a local faraday device using a Raspberry Pi 3 the APRS server stopped due to
[Errno 32] Broken pipe
.Problem Explanation
I allowed a single Faraday (local) to log telemetry and upload to APRS but the APRS stopped after a few days. Investigating into why is stopped I noticed that the tmux screen running
aprs.py
was showing errors:Simply CTRL+C stopping
aprs.py
and restarting theaprs.py
program fixed the issue and aprs.fi shows the Farday unit.Environment
Software
Hardware
Supporting Information
Below is an image of the noted error from the APRS TMUX screen:
Restarting only APRS made APRS properly update to the APRS-IS system:
EDIT (5/7/17):
It looks like this issue or another issue occurred within a few hours after restarting the APRS server... @kb1lqc @reillyeon
I can't start
aprs.py
event after resetting telemetry and new database or completely resetting all programs including proxy.The text was updated successfully, but these errors were encountered: