PiAware running, dump1090 stopped

FlightAware ADS-B Flight Tracking
1

Folks,

This is curiosity rather than a problem at this stage.

My Pi Zero has been feeding PiAware and also FR24 for quite some time, today an email advised of no data being sent.

Pi still running, able to SSH in, PiAware service still running but appears dump1090 had stopped.

Small section of PiAware log file follows;

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Apr 22 21:42:30 raspberrypi piaware[416]: 319435 msgs recv’d from dump1090-fa (31 in last 5m); 318865 msgs sent to FlightAware
Apr 22 21:44:28 raspberrypi piaware[416]: mlat-client(19330): Beast-format results connection with ::1:30104: connection lost
Apr 22 21:44:28 raspberrypi piaware[416]: mlat-client(19330): Lost connection to localhost:30005
Apr 22 21:44:28 raspberrypi piaware[416]: mlat-client(19330): Reconnecting in 30.0 seconds
Apr 22 21:44:28 raspberrypi piaware[416]: lost connection to dump1090-fa via faup1090
Apr 22 21:44:28 raspberrypi piaware[416]: faup1090 exited normally
Apr 22 21:44:28 raspberrypi piaware[416]: reconnecting to dump1090-fa
Apr 22 21:44:30 raspberrypi piaware[416]: no ADS-B data program seen listening on port 30005 for 2 seconds, next check in 60s
Apr 22 21:44:58 raspberrypi piaware[416]: mlat-client(19330): Connection to localhost:30005 lost: [Errno 111] Connection refused
Apr 22 21:44:58 raspberrypi piaware[416]: mlat-client(19330): Reconnecting in 0.5 seconds
Apr 22 21:44:58 raspberrypi piaware[416]: mlat-client(19330): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection re$
Apr 22 21:44:59 raspberrypi piaware[416]: mlat-client(19330): Connection to localhost:30005 lost: [Errno 111] Connection refused
Apr 22 21:44:59 raspberrypi piaware[416]: mlat-client(19330): Reconnecting in 30.0 seconds
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Any obvious reason connection would be refused?

Geoff

2

It’s in your title, dump1090-fa isn’t running.
Debug commands · wiedehopf/adsb-wiki Wiki · GitHub

3

Perhaps I could have worded the last sentence of my post better and ask if any obvious reason dump1090, which had been running fine for months, would stop running?

I know if router shuts down for some reason Pi reconnects when network available again, thought dump1090 responded in a similar way.

Bookmarked the link you sent, shall try that is any other issues.

Geoff

4

Hardware problems is the obvious reason - dying power supply or dongle.
Look at the dump1090 logs; it’s not possible to diagnose much from a vague “dump1090 stopped” description.

5

That is why I posted a partial log file. I couldn’t see anything obvious as to why it failed.

Been working fine since restart though albeit not too many aircraft.

Geoff

6

Wrong log though - it’s the dump1090 log messages that are interesting if it is dump1090 that is having problems.

1 Like
7

Ah right, good point.

Geoff

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.