Several time per day I see these log messages that state dump1090 is not producing data and a attempt to restart is performed. After that things return to normal for a few hours, then it happens again. Should I be as concerned as I am?
…Tom
04/08/2015 14:26:17 lost connection to faup1090, reconnecting…
04/08/2015 14:26:18 no ADS-B data program is serving on port 30005, next check in 60s
04/08/2015 14:26:57 no ADS-B producer program seen for 307 seconds (or since piaware started), will attempt to start it next check after 360 seconds…
04/08/2015 14:26:57 no ADS-B producer (dump1090, modesmixer, etc) appears to be running or is not listening for connections on port 30005, next check in 5m
04/08/2015 14:27:18 no ADS-B data program is serving on port 30005, next check in 60s
04/08/2015 14:27:27 93942 msgs recv’d from dump1090 (54 in last 5m); 93941 msgs sent to FlightAware
04/08/2015 14:28:19 no ADS-B data program is serving on port 30005, next check in 60s
04/08/2015 14:29:19 no ADS-B data program is serving on port 30005, next check in 60s
04/08/2015 14:30:19 no ADS-B data program is serving on port 30005, next check in 60s
04/08/2015 14:31:19 no ADS-B data program is serving on port 30005, next check in 60s
04/08/2015 14:31:49 seconds since last message or startup (335) less than threshold for action (3600), waiting…
04/08/2015 14:31:50 no ADS-B producer program seen for 600 seconds, trying to start it…
04/08/2015 14:31:50 attempting to start dump1090 using ‘/etc/init.d/fadump1090.sh start’…
Starting dump1090 server: dump1090004/08/2015 14:31:50 dump1090 start appears to have been successful
04/08/2015 14:32:19 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
04/08/2015 14:32:19 i see dump1090 serving on port 10001
04/08/2015 14:32:19 connecting to dump1090 on port 10001…
04/08/2015 14:32:20 piaware is connected to dump1090 on port 10001
Are you running wireless? There has been a few feeders that have trouble with wifi connection dropping out due to it going into sleep mode or something similar.
Not wireless, cat5 right to the router. I’ve tried a new 2amp power supply for the RPi2 as well as moving the dongle to a powered USB hub, but the dump1090 failures continue. Are there dump1090 logs that might provide a clue?
Here are my mem and disk stats. I don’t think that’s the issue looking at the available memory and disk space. Do you think trying a different (larger) SD card would be worth a try?
You need to find out why dump1090 is dying (note that it’s not listening at all when piaware starts complaining).
Check the dump1090 logs.
Check dmesg for USB disconnects or out-of-memory-killer complaints.
If you have exposed the dump1090 webserver to the internet at large, stop doing that.
Can you expand on “Check the dump1090 logs.” I am unfamilar with the dump1090 command line.
dmesg doesn’t show anything out of the ordinary.
I do have the localaddress:8080 exposed through the router and I will disable this exposure.
One side note; after many days of dump1090 fails, oddly enough there have been none so far today. and nothing has changed in my setup and the unit has not been rebooted.
Dump1090 will write to stderr. I’m not sure where the flightaware scripts stash that but that’s what I mean by logs, there may be something useful there.
That said, if you had the webserver exposed that is the most likely explanation. There are some unfixed crash bugs in dump1090’s webserver which can be triggered fairly easily by e.g. anyone scanning for webservers.
OK, its been more than 24 hours since the last failure of dump1090. And I am not sure why. I haven’t attempted any changes or reboots. I haven’t even had time to get home and close the web-server’s exposure to the net through the router.
I have the same problem here too. I’m using a Sandisk ultra 16g and I’ve expanded the file system. Had it happen running wireless and also when connected to Ethernet port on router. I’ll check logs maybe tonight to see if anything obvious is going on.
I am using a 8G Class 10 Kingston, but have a Sandisk Ultra 16G on-hand that I thought I would try, if the failures continue. But, I have not seen a failure for about 28 hours now.
