Announcement

Collapse
No announcement yet.

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

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Ok thank you for the response. Is there anything I can change in the mean time to stop it from happening?
    toString - London, UK
    FR24 - T-EGLC55 / PiAware - toString / PlaneFinder - 9008
    Raspberry Pi B+ | Keedox DVB-T USB RTL-SDR [RTL2832U+R820T] | Stock Antenna

    Comment


    • You can change the global timeout parameter in your /etc/fr24feed.ini config file or stop/start service night time if your range is reduced to local traffic. But a fix should be available tomorrow.

      Comment


      • It seems like when fr24feed is configured to use "avr-tcp" as the source of data but this source is not already listening and waiting for connections when starting the feeder, fr24feed crashes.
        F-LLBG3, T-LLBG17

        Comment


        • I switched to the ARM6 version which does not request GPS.

          I am continuing to have the same problem as before - but I'm not certain it is a time-sync problem as it says in the log (see below):

          Time synchronized correctly, offset +0.0078 seconds

          I'm wondering if the key I'm using is still valid.

          Is there anyway to determine if the key I have is valid or not?

          Blort

          cat fr24feed.log
          2015-01-24 08:41:58 | [main][i]FR24 Feeder/Decoder [0x02117000]
          2015-01-24 08:41:58 | [main][i]Version: 1.0.11-3/generic
          2015-01-24 08:41:58 | [main][i]Built on 20150120-1045 (r:master-5bbce8d.git/Linux/armv6l)
          2015-01-24 08:41:58 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
          2015-01-24 08:41:58 | [main][i]Flightradar24 AB(http://flightradar24.com)
          2015-01-24 08:41:58 | [httpd][i]Server started, listening on 0.0.0.0:8754
          2015-01-24 08:41:58 | [main][i]Reader 0 started
          2015-01-24 08:41:58 | [master][i]Starting processing thread
          2015-01-24 08:41:58 | [time][i]Synchronizing time via NTP
          2015-01-24 08:41:58 | [reader][i][0]Initializing reader
          2015-01-24 08:41:58 | [reader][i][0]Connecting to Generic receiver via (tcp://127.0.0.1:45105)
          2015-01-24 08:41:58 | [reader][i][0]Connected to the receiver, authenticating
          2015-01-24 08:41:58 | [reader][i][0]Authenticated, processing messages
          2015-01-24 08:42:02 | [time][i]Time synchronized correctly, offset +0.0078 seconds
          2015-01-24 08:42:02 | [main][i]Feed Network client started
          2015-01-24 08:42:02 | [feed][i]Downloading configuration
          2015-01-24 08:42:02 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
          2015-01-24 08:42:02 | [feed][i]Failed on start, Sleeping 120 seconds
          2015-01-24 08:44:02 | [feed][i]Downloading configuration
          2015-01-24 08:44:03 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
          2015-01-24 08:44:03 | [feed][i]Failed on start, Sleeping 120 seconds
          2015-01-24 08:46:03 | [feed][i]Downloading configuration
          2015-01-24 08:46:03 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
          2015-01-24 08:46:03 | [feed][i]Failed on start, Sleeping 120 seconds
          2015-01-24 08:48:03 | [feed][i]Downloading configuration
          2015-01-24 08:48:04 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
          2015-01-24 08:48:04 | [feed][i]Failed on start, Sleeping 120 seconds
          2015-01-24 08:50:04 | [feed][i]Downloading configuration
          2015-01-24 08:50:04 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
          2015-01-24 08:50:04 | [feed][i]Failed on start, Sleeping 120 seconds
          2015-01-24 08:52:02 | [time][i]Synchronizing time via NTP
          2015-01-24 08:52:05 | [feed][i]Downloading configuration
          2015-01-24 08:52:05 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
          2015-01-24 08:52:05 | [feed][i]Failed on start, Sleeping 120 seconds
          2015-01-24 08:52:07 | [time][i]Time synchronized correctly, offset +0.0089 seconds
          2015-01-24 08:54:05 | [feed][i]Downloading configuration
          2015-01-24 08:54:06 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
          2015-01-24 08:54:06 | [feed][i]Failed on start, Sleeping 120 seconds
          2015-01-24 08:56:06 | [feed][i]Downloading configuration
          2015-01-24 08:56:06 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
          2015-01-24 08:56:06 | [feed][i]Failed on start, Sleeping 120 seconds

          Comment


          • Mac OSX feeder with DVB-T Stick

            Hi there,

            I startet feeding a few days ago with an USB DVB-T Stick and the Software for OSX running on OSX 10.10.1 Yosemite (now on Yosemite Server). No other Apps installed.
            Energy saving options are turned off.
            The feeding stops/breaks after a few hours, the log shows nothing special:

            Code:
            Last login: Sun Jan 25 23:05:59 on ttys000
            Tests-MBP:~ test$ tail -f /var/tmp/fr24feed.log
            2015-01-26 05:36:08 | [feed][i]sent 1 AC in 1 packet
            2015-01-26 05:36:19 | [feed][i]sent 1 AC in 1 packet
            2015-01-26 05:36:24 | [feed][i]sent 1 AC in 1 packet
            2015-01-26 05:36:30 | [feed][i]sent 1 AC in 1 packet
            2015-01-26 05:36:35 | [feed][i]sent 1 AC in 1 packet
            2015-01-26 05:36:40 | [feed][i]sent 1 AC in 1 packet
            2015-01-26 05:36:47 | [feed][i]sent 1 AC in 1 packet
            2015-01-26 05:36:52 | [feed][i]sent 1 AC in 1 packet
            2015-01-26 05:36:59 | [feed][i]sent 1 AC in 1 packet
            2015-01-26 05:37:04 | [feed][i]sent 1 AC in 1 packet
            The Options "Reconfigure Software" "Stop Feeding" and "Show Web Status" are greyed out, flightradar24.com shows the feeder offline.

            I have to restart the software, the log shows the following:

            Code:
            2015-01-26 09:52:16 | [main][i]FR24 Feeder/Decoder [0x02117000]
            2015-01-26 09:52:16 | [main][i]Version: 1.0.10-5/generic
            2015-01-26 09:52:16 | [main][i]Built on Jan 12 2015 16:03:50 (r:???/MacOSX/Universal)
            2015-01-26 09:52:16 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
            2015-01-26 09:52:16 | [main][i]Flightradar24 AB(http://flightradar24.com)
            2015-01-26 09:52:16 | [httpd][i]Server started, listening on 0.0.0.0:8754
            2015-01-26 09:52:16 | [master][i]Starting processing thread
            2015-01-26 09:52:16 | [main][i]Reader 0 started
            2015-01-26 09:52:16 | [reader][i][0]Initializing reader
            2015-01-26 09:52:16 | [main][i]Socket server started
            2015-01-26 09:52:16 | [reader][i][0]Connecting to Generic receiver via (exe:///Applications/FR24FeedOSX.app/Contents/Resources/dump1090  --raw)
            2015-01-26 09:52:16 | [time][i]Synchronizing time via NTP
            2015-01-26 09:52:16 | [bs][i]Initializing server
            2015-01-26 09:52:16 | [bs][i]Starting server on 0.0.0.0:30003
            2015-01-26 09:52:16 | [reader][i][0]Connected to the receiver, authenticating
            2015-01-26 09:52:16 | [reader][i][0]Authenticated, processing messages
            2015-01-26 09:52:19 | [time][i]Time synchronized correctly, offset -0.0008 seconds
            2015-01-26 09:52:19 | [main][i]Feed Network client started
            2015-01-26 09:52:19 | [feed][i]Downloading configuration
            2015-01-26 09:52:19 | [main][i]RAW data server started
            2015-01-26 09:52:19 | [raw][i]Initializing server
            2015-01-26 09:52:19 | [raw][i]Starting server on 0.0.0.0:30002
            2015-01-26 09:52:19 | [feed][c]Interval: 5s
            2015-01-26 09:52:19 | [feed][c]Latitude: 49.XXXX                           (XX out, StDt)
            2015-01-26 09:52:19 | [feed][c]Longitude: 11.XXXX                        (XX out, StDt)
            2015-01-26 09:52:19 | [feed][c]GND: YES
            2015-01-26 09:52:19 | [feed][c]NonADSB: YES
            2015-01-26 09:52:19 | [feed][c]Timestamps: optional
            2015-01-26 09:52:19 | [feed][c]Max range AIR: 350.0nm
            2015-01-26 09:52:19 | [feed][c]Max range GND: 100.0nm
            2015-01-26 09:52:19 | [feed][i]defined 1 server
            2015-01-26 09:52:19 | [feed][n]EDDN41@83.140.21.XXX:8099/UDP    (XX out, StDt)
            2015-01-26 09:52:19 | [stats][i]Stats thread started
            2015-01-26 09:52:19 | [feed][n]connecting
            2015-01-26 09:52:19 | [feed][n]connected
            2015-01-26 09:52:19 | [feed][n]switching to UDP
            2015-01-26 09:52:19 | [feed][n]working
            2015-01-26 09:52:24 | [feed][i]sent 5 AC in 1 packet
            2015-01-26 09:52:29 | [feed][i]sent 5 AC in 1 packet
            2015-01-26 09:52:34 | [feed][i]sent 5 AC in 1 packet
            2015-01-26 09:52:39 | [feed][i]sent 7 AC in 1 packet
            2... (and so on)
            Seems to be looking good.

            So what am I doing wrong? Help is appreciated.

            Best regards,
            StDt

            Comment


            • Thanks for all the feedback!

              @eshabi, will test that scenario,, even if it seems unlikely
              @blort, seems like DNS resolves to incorrect server to get the feeder config,, can you ping feed.flightradar24.com?
              @StDt, was that the last message in the log? No termination information or anything?

              Comment


              • Originally posted by piopawlu View Post
                @eshabi, will test that scenario,, even if it seems unlikely
                When I tried to use the feeder to run dump1090 (external or included) using the configuration "path=" option and connect to its avr-tcp data on port 30002, it crashed.
                Tried to run them sequentially using a batch file - crashed.
                Added a delay in the batch file between running dump1090 and the feeder using "timeout /T 3" command - runs okay. This is my current configuration.
                Tried now to run the feeder with no dump1090 running - crashed.

                this is my config file:
                receiver="avr-tcp"
                fr24key=""
                host="localhost:30002"
                bs="no"
                raw="no"
                logmode="2"
                Last edited by eshabi; 2015-01-26, 15:03.
                F-LLBG3, T-LLBG17

                Comment


                • Thanks, this bug is confirmed on Windows platform. A fix will be issued most likely tomorrow morning.

                  Comment


                  • Originally posted by piopawlu View Post
                    You can change the global timeout parameter in your /etc/fr24feed.ini config file or stop/start service night time if your range is reduced to local traffic. But a fix should be available tomorrow.
                    PHP Code:
                    2015-01-26 02:43:30 | [feed][n]ping 12
                    2015
                    -01-26 02:43:36 | [reader][w][0]Global timeout exceeded0 msgs0 resyncsreconnecting
                    2015
                    -01-26 02:43:36 | [reader][i][0]Connection terminated
                    2015
                    -01-26 02:43:36 | [main][i]Terminating child process 3089 with SIGETERM
                    2015
                    -01-26 02:43:42 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                    2015-01-26 02:43:42 | [reader][i][0]Connected to the receiverauthenticating
                    2015
                    -01-26 02:43:42 | [reader][i][0]Authenticatedprocessing messages
                    2015
                    -01-26 02:43:42 | [reader][i][0]Connection terminated
                    2015
                    -01-26 02:43:42 | [main][i]Terminating child process 3104 with SIGETERM
                    2015
                    -01-26 02:43:47 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                    2015-01-26 02:43:47 | [reader][i][0]Connected to the receiverauthenticating
                    2015
                    -01-26 02:43:47 | [reader][i][0]Authenticatedprocessing messages
                    2015
                    -01-26 02:43:47 | [reader][i][0]Connection terminated
                    2015
                    -01-26 02:43:47 | [main][i]Terminating child process 3105 with SIGETERM
                    2015
                    -01-26 02:43:53 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                    2015-01-26 02:43:53 | [reader][i][0]Connected to the receiverauthenticating
                    2015
                    -01-26 02:43:53 | [reader][i][0]Authenticatedprocessing messages
                    2015
                    -01-26 02:43:53 | [reader][i][0]Connection terminated
                    2015
                    -01-26 02:43:53 | [main][i]Terminating child process 3106 with SIGETERM
                    2015
                    -01-26 02:43:58 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                    2015-01-26 02:43:58 | [reader][i][0]Connected to the receiverauthenticating
                    2015
                    -01-26 02:43:58 | [reader][i][0]Authenticatedprocessing messages
                    2015
                    -01-26 02:43:59 | [reader][i][0]Connection terminated
                    2015
                    -01-26 02:43:59 | [main][i]Terminating child process 3107 with SIGETERM 
                    This is still happening to me some nights around 2am. But other nights it's fine... What do you think I should change the timeout parameter to?
                    toString - London, UK
                    FR24 - T-EGLC55 / PiAware - toString / PlaneFinder - 9008
                    Raspberry Pi B+ | Keedox DVB-T USB RTL-SDR [RTL2832U+R820T] | Stock Antenna

                    Comment


                    • Originally posted by piopawlu View Post
                      Thanks for all the feedback!
                      ...
                      @StDt, was that the last message in the log? No termination information or anything?
                      No sorry, nothing. The log ran all over the day.
                      Are there further log-files I could look after?

                      Same thing happened later:

                      Code:
                      ...
                      2015-01-26 11:11:39 | [feed][i]sent 4 AC in 1 packet
                      2015-01-26 11:11:44 | [feed][i]sent 6 AC in 1 packet
                      2015-01-26 11:11:49 | [feed][i]sent 6 AC in 1 packet
                      2015-01-26 11:11:51 | [feed][i]removed 3 of 12 AC
                      2015-01-26 11:11:54 | [feed][i]sent 4 AC in 1 packet
                      2015-01-26 11:11:59 | [feed][i]removed 1 of 10 AC
                      2015-01-26 11:11:59 | [feed][i]sent 6 AC in 1 packet
                      2015-01-26 11:12:04 | [feed][i]sent 7 AC in 1 packet
                      2015-01-26 11:12:09 | [feed][i]sent 6 AC in 1 packet
                      2015-01-26 11:12:14 | [feed][i]sent 6 AC in 1 packet
                      2015-01-26 11:12:19 | [feed][i]sent 7 AC in 1 packet
                      2015-01-26 11:12:24 | [feed][i]sent 5 AC in 1 packet
                      2015-01-26 18:49:08 | [main][i]FR24 Feeder/Decoder [0x02117000]
                      2015-01-26 18:49:08 | [main][i]Version: 1.0.10-5/generic
                      2015-01-26 18:49:08 | [main][i]Built on Jan 12 2015 16:03:50 (r:???/MacOSX/Universal)
                      2015-01-26 18:49:08 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
                      2015-01-26 18:49:08 | [main][i]Flightradar24 AB(http://flightradar24.com)
                      2015-01-26 18:49:08 | [httpd][i]Server started, listening on 0.0.0.0:8754
                      2015-01-26 18:49:08 | [main][i]Reader 0 started
                      2015-01-26 18:49:08 | [master][i]Starting processing thread
                      2015-01-26 18:49:08 | [reader][i][0]Initializing reader
                      2015-01-26 18:49:08 | [main][i]Socket server started
                      2015-01-26 18:49:08 | [bs][i]Initializing server
                      2015-01-26 18:49:08 | [reader][i][0]Connecting to Generic receiver via (exe:///Applications/FR24FeedOSX.app/Contents/Resources/dump1090  --raw)
                      2015-01-26 18:49:08 | [time][i]Synchronizing time via NTP
                      2015-01-26 18:49:08 | [bs][i]Starting server on 0.0.0.0:30003
                      2015-01-26 18:49:08 | [reader][i][0]Connected to the receiver, authenticating
                      2015-01-26 18:49:08 | [reader][i][0]Authenticated, processing messages
                      2015-01-26 18:49:12 | [time][i]Time synchronized correctly, offset -0.0053 seconds
                      2015-01-26 18:49:12 | [main][i]Feed Network client started
                      2015-01-26 18:49:12 | [main][i]RAW data server started
                      2015-01-26 18:49:12 | [feed][i]Downloading configuration
                      2015-01-26 18:49:12 | [raw][i]Initializing server
                      2015-01-26 18:49:12 | [raw][i]Starting server on 0.0.0.0:30002
                      2015-01-26 18:49:12 | [feed][c]Interval: 5s
                      2015-01-26 18:49:12 | [feed][c]Latitude: 49.XX00
                      2015-01-26 18:49:12 | [feed][c]Longitude: 11.XX00
                      2015-01-26 18:49:12 | [feed][c]GND: YES
                      2015-01-26 18:49:12 | [feed][c]NonADSB: YES
                      2015-01-26 18:49:12 | [feed][c]Timestamps: optional
                      2015-01-26 18:49:12 | [feed][c]Max range AIR: 350.0nm
                      2015-01-26 18:49:12 | [feed][c]Max range GND: 100.0nm
                      2015-01-26 18:49:12 | [stats][i]Stats thread started
                      2015-01-26 18:49:12 | [feed][i]defined 1 server
                      2015-01-26 18:49:12 | [feed][n]EDDN41@83.140.21.66:8099/UDP
                      2015-01-26 18:49:12 | [feed][n]connecting
                      2015-01-26 18:49:12 | [feed][n]connected
                      2015-01-26 18:49:12 | [feed][n]switching to UDP
                      2015-01-26 18:49:12 | [feed][n]working
                      2015-01-26 18:49:17 | [feed][i]sent 4 AC in 1 packet
                      2015-01-26 18:49:22 | [feed][i]sent 5 AC in 1 packet
                      2015-01-26 18:49:27 | [feed][i]sent 6 AC in 1 packet
                      2015-01-26 18:49:32 | [feed][i]sent 5 AC in 1 packet
                      2015-01-26 18:49:37 | [feed][i]sent 5 AC in 1 packet
                      2015-01-26 18:49:42 | [feed][i]sent 4 AC in 1 packet
                      2015-01-26 18:49:47 | [feed][i]sent 3 AC in 1 packet
                      2015-01-26 18:49:52 | [feed][i]sent 5 AC in 1 packet
                      2015-01-26 18:49:57 | [feed][i]sent 5 AC in 1 packet
                      2015-01-26 18:50:02 | [feed][i]sent 6 AC in 1 packet
                      2015-01-26 18:50:07 | [feed][i]sent 6 AC in 1 packet
                      2015-01-26 18:50:12 | [feed][i]sent 6 AC in 1 packet
                      ...
                      Last edited by StDt; 2015-01-26, 18:31.

                      Comment


                      • Yes I can ping feed.flightradar24.com:

                        ping feed.flightradar24.com
                        PING got.fr24.com (83.140.21.89) 56(84) bytes of data.
                        64 bytes from 83.140.21.89.biz.sta.port80.se (83.140.21.89): icmp_seq=1 ttl=53 time=202 ms
                        64 bytes from 83.140.21.89.biz.sta.port80.se (83.140.21.89): icmp_seq=2 ttl=53 time=205 ms
                        ^C
                        --- got.fr24.com ping statistics ---
                        2 packets transmitted, 2 received, 0% packet loss, time 1001ms
                        rtt min/avg/max/mdev = 202.473/203.850/205.227/1.377 ms

                        Yet I still get this:

                        2015-01-26 23:34:48 | [feed][i]Failed on start, Sleeping 120 seconds
                        2015-01-26 23:36:48 | [feed][i]Downloading configuration
                        2015-01-26 23:36:49 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
                        2015-01-26 23:36:49 | [feed][i]Failed on start, Sleeping 120 seconds
                        2015-01-26 23:38:46 | [time][i]Synchronizing time via NTP
                        2015-01-26 23:38:49 | [feed][i]Downloading configuration
                        2015-01-26 23:38:49 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
                        2015-01-26 23:38:49 | [feed][i]Failed on start, Sleeping 120 seconds
                        2015-01-26 23:38:51 | [time][i]Time synchronized correctly, offset -0.0007 seconds, drift -0.0000 seconds/minute


                        Blort

                        Comment


                        • @piopawlu

                          Same thing happened again and again.

                          First I thought it would be the WLAN connection that breaks or interrupts the feeding.

                          Then I tried a LAN cable connection. Same thing happening. (The feeding stops/breaks after a few hours/minutes, the log shows nothing at all - it stops logging)

                          Any hints?

                          Comment


                          • feeder download (Win) "not found"

                            @StDt: Maybe a firewall problem?

                            @Piotr, page http://feed.flightradar24.com/windows/ click on "fr24feed_win32-1.0.11-5.zip" shows "404 - Not Found".

                            Regards, -Wolli-
                            Last edited by Wolli; 2015-01-27, 16:06.

                            Comment


                            • Originally posted by Wolli View Post
                              @StDt: Maybe a firewall problem?
                              Regards, -Wolli-
                              Nope, then it wouldn't feed at all.
                              The log shows it is feeding. But after some time (minutes or hours) the feeding app doesn't feed anymore.

                              Comment


                              • @StDt: Yep, you're right, of course. My statement was an idea to blort's problem. Please excuse.

                                @blort: Seems imho, that the feeder does not at all connect to the FR24 server. Might the reason be a firewall issue on your side? Just an interim possibility (while waiting for Piotr's answer). Good luck however, -Wolli-

                                Comment

                                Working...
                                X