I recently upgraded my receiver (added inline amp and raised antenna) which vastly increased my range and count. I also started using PiAware, which seems to have caused fr24feed to stop working. I tried searching on both forums for a solution, but only found conflicting or ambiguous information.
For example, in the fr24 "Read this first!" post it says "If you have any questions related to the feeding software or about feeding Flightradar24
-> http://forum.flightradar24.com/threa...tware-thread!)"
But if you click on the link, you discover that it is "closed". Similarly, other links suggest using software that has been officially deprecated, or not clearly identified. For example, 'dump1090-mutability' is advised (without explanation), but there seems to be more than one version floating around.
So, if you're simply using a Raspberry PI (note: not "PIE") with an R820T(2) dongle, with the latest FR24 "apt-get" version feeder (with MLAT), how do I get it to run nicely with PiAware? Currently it's installed but not working. I'm getting these errors:
/var/log/fr24feed.log
2015-12-18 21:11:21 | [main][i]Terminating on user request
2015-12-18 21:11:21 | [main][i]Terminating worker threads
2015-12-18 21:11:21 | [master][i]Terminating on request
2015-12-18 21:11:22 | [reader][i]Terminating on request
2015-12-18 21:11:22 | [feed][n]busy
2015-12-18 21:11:22 | [feed][n]disconnected
2015-12-18 21:11:22 | [feed][x]Feeding thread terminated
2015-12-18 21:11:22 | [mlat][i]Pinging the server
2015-12-18 21:11:22 | [mlat][i]Stats 0/0
2015-12-18 21:11:24 | [httpd][d]Master thread terminated
/var/log/syslog
Dec 20 07:40:01 raspberrypi /usr/sbin/cron[2241]: (*system*fr24feed_updater) WRONG FILE OWNER (/etc/cron.d/fr24feed_updater)
It would help immensely if there was a single, authoritative thread to answer and fix these issues.
Thanks.
EDIT: The fr24feed.log entry above was from the wrong day. Here's the most recent, captured when I had temporarily stopped PIAWARE and restarted FR24FEED, which had been working fine before I installed PIAWARE.
...
2015-12-20 10:23:55 | [mlat][i]Pinging the server
2015-12-20 10:23:55 | [mlat][i]Stats 0/0
2015-12-20 10:23:59 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --net --net-http-port 80 --raw --mlat)
2015-12-20 10:23:59 | [reader][i][0]Connected to the receiver, authenticating
2015-12-20 10:23:59 | [reader][i][0]Authenticated, processing messages
2015-12-20 10:23:59 | [reader][i][0]Connection terminated
2015-12-20 10:23:59 | [main][i]Terminating child process 18913 with SIGETERM
2015-12-20 10:24:01 | [feed][n]ping 4
2015-12-20 10:24:05 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --net --net-http-port 80 --raw --mlat)
2015-12-20 10:24:05 | [reader][i][0]Connected to the receiver, authenticating
2015-12-20 10:24:05 | [reader][i][0]Authenticated, processing messages
2015-12-20 10:24:05 | [reader][i][0]Connection terminated
2015-12-20 10:24:05 | [main][i]Terminating child process 18914 with SIGETERM
...
So it looks like the two softwares are somehow sharing resources and interfering with each other, hopefully unintentionally. Somewhat surprising, since each should be running its own copy of dump1090. (
For example, in the fr24 "Read this first!" post it says "If you have any questions related to the feeding software or about feeding Flightradar24
-> http://forum.flightradar24.com/threa...tware-thread!)"
But if you click on the link, you discover that it is "closed". Similarly, other links suggest using software that has been officially deprecated, or not clearly identified. For example, 'dump1090-mutability' is advised (without explanation), but there seems to be more than one version floating around.
So, if you're simply using a Raspberry PI (note: not "PIE") with an R820T(2) dongle, with the latest FR24 "apt-get" version feeder (with MLAT), how do I get it to run nicely with PiAware? Currently it's installed but not working. I'm getting these errors:
/var/log/fr24feed.log
2015-12-18 21:11:21 | [main][i]Terminating on user request
2015-12-18 21:11:21 | [main][i]Terminating worker threads
2015-12-18 21:11:21 | [master][i]Terminating on request
2015-12-18 21:11:22 | [reader][i]Terminating on request
2015-12-18 21:11:22 | [feed][n]busy
2015-12-18 21:11:22 | [feed][n]disconnected
2015-12-18 21:11:22 | [feed][x]Feeding thread terminated
2015-12-18 21:11:22 | [mlat][i]Pinging the server
2015-12-18 21:11:22 | [mlat][i]Stats 0/0
2015-12-18 21:11:24 | [httpd][d]Master thread terminated
/var/log/syslog
Dec 20 07:40:01 raspberrypi /usr/sbin/cron[2241]: (*system*fr24feed_updater) WRONG FILE OWNER (/etc/cron.d/fr24feed_updater)
It would help immensely if there was a single, authoritative thread to answer and fix these issues.
Thanks.
EDIT: The fr24feed.log entry above was from the wrong day. Here's the most recent, captured when I had temporarily stopped PIAWARE and restarted FR24FEED, which had been working fine before I installed PIAWARE.
...
2015-12-20 10:23:55 | [mlat][i]Pinging the server
2015-12-20 10:23:55 | [mlat][i]Stats 0/0
2015-12-20 10:23:59 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --net --net-http-port 80 --raw --mlat)
2015-12-20 10:23:59 | [reader][i][0]Connected to the receiver, authenticating
2015-12-20 10:23:59 | [reader][i][0]Authenticated, processing messages
2015-12-20 10:23:59 | [reader][i][0]Connection terminated
2015-12-20 10:23:59 | [main][i]Terminating child process 18913 with SIGETERM
2015-12-20 10:24:01 | [feed][n]ping 4
2015-12-20 10:24:05 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --net --net-http-port 80 --raw --mlat)
2015-12-20 10:24:05 | [reader][i][0]Connected to the receiver, authenticating
2015-12-20 10:24:05 | [reader][i][0]Authenticated, processing messages
2015-12-20 10:24:05 | [reader][i][0]Connection terminated
2015-12-20 10:24:05 | [main][i]Terminating child process 18914 with SIGETERM
...
So it looks like the two softwares are somehow sharing resources and interfering with each other, hopefully unintentionally. Somewhat surprising, since each should be running its own copy of dump1090. (
Comment