I have piaware-jessie-sd-card-2.1-5 installed on an RPi B+ and all seems to be working fine… Except that after several hours, I can no longer receive the feed, but I can ssh into the Pi and get the following:
pi@piaware:~ $ sudo piaware-status
dump1090 is not running.
faup1090 is not running.
piaware is running.
no program appears to be listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is connected to FlightAware.
got ‘couldn’t open socket: connection refused’
maybe dump1090 is NOT producing data on port 30005.
After rebooting the Pi, it seems to work fine… But a few hours later, we repeat the above.
Any ideas why this is happening?
In searching the forum, I read some opinions that the power supply may be failing… Which reminded me that the power supply I’m using on this B+ is actually designed for the Pi3.
Is the red light on your RPi flashing? (It should be solid red while powered up.)
If so defiantly replace your power supply with a higher amperage one or move your dongle and/or any other USB accessories to a powered USB hub.
Run the command “dmesg” to view your kernel message buffer and look for errors as stated above.
Check system log files for possible system errors.
/var/log/syslog
/var/log/messages
Not sure what I’m looking at here, but maybe something jumps out at you? Should I send the entire dmesg report?
Last few lines of the log read:
05/12/2016 18:07:45 9984 msgs recv’d from dump1090 (285 in last 5m); 9981 msgs sent to FlightAware
05/12/2016 18:09:40 lost connection to dump1090 via faup1090
05/12/2016 18:09:40 reconnecting to dump1090
05/12/2016 18:09:40 no ADS-B data program seen listening on port 30005 for 0 seconds, next check in 6$
05/12/2016 18:10:40 no ADS-B data program seen listening on port 30005 for 60 seconds, next check in $
05/12/2016 18:11:40 no ADS-B data program seen listening on port 30005 for 120 seconds, next check in$
05/12/2016 18:12:40 no ADS-B data program seen listening on port 30005 for 180 seconds, next check in$
The power supply I’m using was included with the Canakit I bought for a PiR 3 - which is supposedly provides more power than the B+ Pi I’m using requires.
Is there a “good” power supply I should get?
I run a CanaKit 5V 2.5A and it works just fine for me. Mine is actually running a RPi2, two SDR dongles, and a WiFi dongle connected directly to the RPi and an external hard drive which is powered separately of course with no problems. No keyboard or mouse is present as well which would cut back on some of the drain. One of the tell tale signs of a bad or underpowered power supply is if the red light is solid or not. Keep in mind amperage is the big thing to look for when powering more than just the RPi itself.
Did you happen to see anything in /var/log/syslog or var/log/messages?
My red light is solid, both while piaware has crashed and while it’s running. I have the same power supply you do and the only dongles are a WiFi and the receiver. The receiver seems a little cheesy, but it’s what many seem to be using. Might it be the receiver?
Nothing stuck out in syslog, but the following was in messages…
snip…
May 11 04:52:10 piaware rsyslogd-2007: action ‘action 17’ suspended, next retry is Wed May 11 04:53:40 2016 [try rsyslog.com/e/2007 ]
May 11 04:58:20 piaware rsyslogd-2007: action ‘action 17’ suspended, next retry is Wed May 11 04:59:50 2016 [try rsyslog.com/e/2007 ]
May 11 05:02:35 piaware rsyslogd-2007: action ‘action 17’ suspended, next retry is Wed May 11 05:04:05 2016 [try rsyslog.com/e/2007 ]
May 11 05:04:31 piaware rsyslogd-2007: action ‘action 17’ suspended, next retry is Wed May 11 05:06:01 2016 [try rsyslog.com/e/2007 ]
May 11 05:05:16 piaware rsyslogd: [origin software=“rsyslogd” swVersion=“8.4.2” x-pid=“357” x-info=“http://www.rsyslog.com”] exiting on signal 15.
May 11 05:05:29 piaware rsyslogd: [origin software=“rsyslogd” swVersion=“8.4.2” x-pid=“354” x-info=“http://www.rsyslog.com”] start
May 11 05:05:29 piaware kernel: 0.000000] Booting Linux on physical CPU 0x0
May 11 05:05:29 piaware kernel: 0.000000] Initializing cgroup subsys cpuset
May 11 05:05:29 piaware kernel: 0.000000] Initializing cgroup subsys cpu
May 11 05:05:29 piaware kernel: 0.000000] Initializing cgroup subsys cpuacct
May 11 05:05:29 piaware kernel: 0.000000] Linux version 4.1.19+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #858 Tue Mar 15 15:52:03 GMT 2016
May 11 05:05:29 piaware kernel: 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
May 11 05:05:29 piaware kernel: 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
May 11 05:05:29 piaware kernel: 0.000000] Machine model: Raspberry Pi Model B Plus Rev 1.2
snip…
