Flightradar24 decoder/feeder BETA testing (Win/RPi/Linux/OSX)

[StDt]

When the OSX feeder app does not feed any more it looks like the following screenshot:

Bildschirmfoto 2015-01-27 um 22.24.37.png

I have to quit the app manually and restart it, then start feeding again.

[blort]

@Wolli

Thanks for the reply, but I can ping the feeder from the Linux Computer that is connecting / attempting to connect with fr24. Several months ago fr24 worked fine using the NAT router that I have right now. I haven't made any changes to the router in over 2 years. The same Linux computer has successfully interacted with a number of other web sites. It's just the FR24 feeder that is having problems. I'm concerned that my key is no longer valid and I would like to find a way to verify if the key is valid or not without having to use the FR24 feeder. Does anyone know how to do that?

Blort

[Wolli]

@blort: It was just an idea. Sometimes firewalls just block some ports and not the whole communication to a server. However, you might wait for Piotr's response here or contact FR24 on their contact page. Good luck, -Wolli-

[piopawlu]

@blort: Can you please try to add the following line:
export FR24AUTHIP=83.140.21.89 in the /etc/init.d/fr24feed in the start() function just below the log message?

I am working on the OSX issue,, but no eta on next release just yet.

[piopawlu]

There's a new RPi build, as well as Windows build 1.0.11-5, no major changes just fixes really:
1. Autodetection of dump1090 running and or PiAware on signup + autoconfig option
2. DNS lookup check to decide whether to use libc based or "ping" based lookups
3. More timing fixes
4. Automatically disable RAW/BS when "--net" argument detected in procargs.
5. On Windows it will no longer ask for COM/baudrate for SBS1

Next build will bring an ***optional*** auto-update feature that will let you get the latest build as soon as available and you can decide whether you want to receive both testing or just "stable" releases. Packages will be digitally signed and verified before extracting. This option will initially be available only for Linux, later Windows and finally OSX.

[toString]

Many thanks. Hopefully this will resolve my issue. I look forward to the auto-update feature as well.

This is the first upgrade I've done - do I just follow the steps as per the manual for the first install, or is the procedure different if you already have it installed and running?

[piopawlu]

All you need to do is the "dpkg -i" step, afterwards start the service again. I will include this information in the next manual release.

[toString]

Thanks again!
So for reference to others for now - I did this:

wget http://feed.flightradar24.com/raspberry-pi/fr24feed_1.0.11-5_armhf.deb
sudo dpkg -i fr24feed_1.0.11-5_armhf.deb
sudo service fr24feed start

[piopawlu]

Looks good :-)

[toString]

Sadly doesn't appear to have fixed my problem. I'm having to constantly keep an eye on it:

2015-01-28 16:17:06 | [feed][n]ping 20
2015-01-28 16:17:21 | [reader][w][0]Global timeout exceeded, 65971 msgs, 0 resyncs, reconnecting
2015-01-28 16:17:21 | [reader][i][0]Connection terminated
2015-01-28 16:17:21 | [main][i]Terminating child process 2260 with SIGETERM
2015-01-28 16:17:26 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
2015-01-28 16:17:26 | [reader][i][0]Connected to the receiver, authenticating
2015-01-28 16:17:26 | [reader][i][0]Authenticated, processing messages
2015-01-28 16:17:26 | [reader][i][0]Connection terminated
2015-01-28 16:17:26 | [main][i]Terminating child process 2564 with SIGETERM
2015-01-28 16:17:32 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
2015-01-28 16:17:32 | [reader][i][0]Connected to the receiver, authenticating
2015-01-28 16:17:32 | [reader][i][0]Authenticated, processing messages
2015-01-28 16:17:32 | [reader][i][0]Connection terminated
2015-01-28 16:17:32 | [main][i]Terminating child process 2565 with SIGETERM
2015-01-28 16:17:37 | [feed][n]ping 21
2015-01-28 16:17:38 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
2015-01-28 16:17:38 | [reader][i][0]Connected to the receiver, authenticating
2015-01-28 16:17:38 | [reader][i][0]Authenticated, processing messages
2015-01-28 16:17:38 | [reader][i][0]Connection terminated
2015-01-28 16:17:38 | [main][i]Terminating child process 2566 with SIGETERM
2015-01-28 16:17:43 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
2015-01-28 16:17:43 | [reader][i][0]Connected to the receiver, authenticating
2015-01-28 16:17:43 | [reader][i][0]Authenticated, processing messages
2015-01-28 16:17:43 | [reader][i][0]Connection terminated
2015-01-28 16:17:43 | [main][i]Terminating child process 2567 with SIGETERM
2015-01-28 16:17:49 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
2015-01-28 16:17:49 | [reader][i][0]Connected to the receiver, authenticating
2015-01-28 16:17:49 | [reader][i][0]Authenticated, processing messages
2015-01-28 16:17:49 | [reader][i][0]Connection terminated
2015-01-28 16:17:49 | [main][i]Terminating child process 2568 with SIGETERM
2015-01-28 16:17:50 | [stats][i]sent 16 bytes
2015-01-28 16:17:54 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
2015-01-28 16:17:54 | [reader][i][0]Connected to the receiver, authenticating
2015-01-28 16:17:54 | [reader][i][0]Authenticated, processing messages
2015-01-28 16:17:54 | [reader][i][0]Connection terminated
2015-01-28 16:17:54 | [main][i]Terminating child process 2569 with SIGETERM 

[blort]

@piopawlu

The export FR24AUTHIP=83.140.21.89 correction fixed.

Thanks,

Blort

[piopawlu]

@toString, sorry I will make yet another build today that will do that...
@blort, can you try the latest build without that export line?

[toString]

Thank you piopawlu.

Is it just me that is reporting this? Makes me wonder that my pi or usb stick is faulty?

[eshabi]

Seems like latest Windows build fails to terminate on my Windows 7 machine.
Console is still on after termination messages are displayed, and trying to close it is causing the process to crash.

2015-01-29 10:50:38 | [feed][i]sent 4 AC in 1 packet
2015-01-29 10:50:44 | [feed][i]sent 4 AC in 1 packet
2015-01-29 10:50:44 | [feed][n]syncing stream
2015-01-29 10:50:48 | [reader][i][0]Connection terminated
2015-01-29 10:50:48 | [reader][i]Terminating on request
2015-01-29 10:50:52 | [master][i]Terminating on request
2015-01-29 10:50:54 | [main][i]Terminating worker threads
2015-01-29 10:50:54 | [feed][n]busy
2015-01-29 10:50:54 | [feed][n]disconnected
2015-01-29 10:50:54 | [feed][x]Feeding thread terminated
2015-01-29 10:50:54 | [main][i]Terminated successfully

[Wolli]

Seems like latest Windows build fails to terminate on my Windows 7 machine.
Console is still on after termination messages are displayed, and trying to close it is causing the process to crash.

Exactly the same happens on my machine (Win Vista SP2). This should be fixed, although I would personally rate this bug as not critical (for my work on my machine). Regards, -Wolli-