Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Long Duration APRS Failed - [Errno 32] Broken pipe #199

Closed
kb1lqd opened this issue May 7, 2017 · 1 comment
Closed

Long Duration APRS Failed - [Errno 32] Broken pipe #199

kb1lqd opened this issue May 7, 2017 · 1 comment
Assignees
Labels

Comments

@kb1lqd
Copy link
Contributor

kb1lqd commented May 7, 2017

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:

2017-05-07 05:53:43,321 - APRS - INFO - Tracking 1 Faraday stations...
2017-05-07 05:53:43,322 - APRS - ERROR - SendPosition
2017-05-07 05:53:43,323 - APRS - ERROR - [Errno 32] Broken pipe
2017-05-07 05:53:43,324 - APRS - ERROR - Sendtelemetry
2017-05-07 05:53:43,324 - APRS - ERROR - [Errno 32] Broken pipe
2017-05-07 05:53:43,325 - APRS - ERROR - SendTelemLabels
2017-05-07 05:53:43,326 - APRS - ERROR - [Errno 32] Broken pipe
2017-05-07 05:53:43,327 - APRS - ERROR - SendParameters
2017-05-07 05:53:43,328 - APRS - ERROR - [Errno 32] Broken pipe
2017-05-07 05:53:43,329 - APRS - ERROR - SendEquations
2017-05-07 05:53:43,329 - APRS - ERROR - [Errno 32] Broken pipe

Simply CTRL+C stopping aprs.py and restarting the aprs.py program fixed the issue and aprs.fi shows the Farday unit.

Environment

Software

commit 2ba04caff9affb0376eb4997a92933ba993c56a5
Merge: 71086e8 6340882
Author: Bryce Salmi <[email protected]>
Date:   Sun Apr 30 13:02:29 2017 -0700

    Merge pull request #196 from FaradayRF/kb1lqc-patch-1

    Quick Fix To Update Proxy.py To sys.exit(1)

Hardware

  • REV D1 Faraday units
  • Raspberry Pi 3

Supporting Information

Below is an image of the noted error from the APRS TMUX screen:

image

Restarting only APRS made APRS properly update to the APRS-IS system:

image

EDIT (5/7/17):

It looks like this issue or another issue occurred within a few hours after restarting the APRS server... @kb1lqc @reillyeon

image

I can't start aprs.py event after resetting telemetry and new database or completely resetting all programs including proxy.

image

@kb1lqd
Copy link
Contributor Author

kb1lqd commented Sep 28, 2017

PR #271 (and possibly #273) looks to have fixed this issue.

@kb1lqd kb1lqd closed this as completed Sep 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants