Announcement

Collapse
No announcement yet.

Linux feeder software for Flightradar24 (Old software)

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

  • Originally posted by obj View Post
    Quick bug report: the feeder exhausts available file descriptors after a while and stops feeding data properly. The website stats show the feeder "online" but no data available.

    Logs have periodic complaints with errno 24 (24 is EMFILE - "too many open files"):

    Code:
    [n]pinging the server
    [i]sent 37 planes in 1 packets
    [i]sent 37 planes in 1 packets
    [i]sent 36 planes in 1 packets
    [i]sent 34 planes in 1 packets
    [e]Socket is not valid, errno: 24
    [i]sent 36 planes in 1 packets
    [e]Socket is not valid, errno: 24
    The process file descriptors look like this:

    Code:
    pi@rpi ~ $ sudo lsof -p 2129
    COMMAND    PID USER   FD   TYPE    DEVICE SIZE/OFF      NODE NAME
    fr24feed_ 2129 adsb  cwd    DIR     179,2     4096         2 /
    fr24feed_ 2129 adsb  rtd    DIR     179,2     4096         2 /
    fr24feed_ 2129 adsb  txt    REG     179,2   791538    144509 /usr/local/adsb/bin/fr24feed_arm-rpi_242
    fr24feed_ 2129 adsb  mem    REG     179,2    71528      7920 /lib/arm-linux-gnueabihf/libresolv-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2    18040      5520 /lib/arm-linux-gnueabihf/libnss_dns-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2    42692      7880 /lib/arm-linux-gnueabihf/libnss_files-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2  1200240      7900 /lib/arm-linux-gnueabihf/libc-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2   130448      1885 /lib/arm-linux-gnueabihf/libgcc_s.so.1
    fr24feed_ 2129 adsb  mem    REG     179,2   427628      7431 /lib/arm-linux-gnueabihf/libm-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2   800736      1249 /usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.19
    fr24feed_ 2129 adsb  mem    REG     179,2    87792      5181 /lib/arm-linux-gnueabihf/libz.so.1.2.7
    fr24feed_ 2129 adsb  mem    REG     179,2   116462      7878 /lib/arm-linux-gnueabihf/libpthread-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2    10170     25003 /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so
    fr24feed_ 2129 adsb  mem    REG     179,2   126236      7434 /lib/arm-linux-gnueabihf/ld-2.13.so
    fr24feed_ 2129 adsb    0r   CHR       1,3      0t0        21 /dev/null
    fr24feed_ 2129 adsb    1w   REG     179,2 35906793    271294 /var/log/adsb/fr24feed.log
    fr24feed_ 2129 adsb    2w   REG     179,2 35906793    271294 /var/log/adsb/fr24feed.log
    fr24feed_ 2129 adsb    3u  IPv4 360960925      0t0       UDP *:41058 
    fr24feed_ 2129 adsb    4u  IPv4 264769977      0t0       TCP localhost:47243->localhost:30003 (ESTABLISHED)
    fr24feed_ 2129 adsb    5r  FIFO       0,9      0t0 305654561 pipe
    fr24feed_ 2129 adsb    6r  FIFO       0,9      0t0 269894173 pipe
    fr24feed_ 2129 adsb    7r  FIFO       0,9      0t0 256578387 pipe
    fr24feed_ 2129 adsb    8r  FIFO       0,9      0t0  45787475 pipe
    [... lots more ...]
    fr24feed_ 2129 adsb 1021r  FIFO       0,9      0t0 305610871 pipe
    fr24feed_ 2129 adsb 1022r  FIFO       0,9      0t0 305654149 pipe
    fr24feed_ 2129 adsb 1023w  FIFO       0,9      0t0 359848218 pipe
    This is using "fr24feed_arm-rpi_242". The process has been up for a bit over a month at this point (but it might have stopped feeding a while back - I don't check it too often)
    I'm having the same problem. This is the second time in a month that this has happened.

    Comment


    • Hi,

      what do I need to do if/when I want to have several "antennas" for one "feeder"?

      Here is the set-up I've been thinking:

      Feeder host
      - running fr24feed and feeding to FR24
      - runs dump1090 (with --net-only if there is no DVB-T stick)
      - can have a DVB-T stick
      - just one per site

      Antenna host
      - does not run fr24feed
      - has a DVB-T stick and runs dump1090
      - 1-2 per site, different antenna configuration/location

      The motivation is mainly to test new antennas without disturbing steady the feed to FR24.

      I can have 1+2 hosts (all with DVB-T sticks) at home and 1+1 (both with DVB-T sticks) at the garage (different location, i.e. different feed with separate key).

      My very first idea was to do this:

      nc antennahostX 30002 | nc feederhost 30001
      but I'm not sure if this works, the number of total usable messages does not seem to add up.

      I was expecting that the number of total usable messages from the feeder is the sum of number of total usable messages from all the antennas, but this does not seem to be the case.

      I have --stats-every 600 so I see the summary every 10 minutes, although the reporting periods are not exactly the same, it depends on when each dump1090 was started, but since I live in an area that does not have the sky full of flights all the time I can compare the number of messages somewhat accurately. Simplified example: one flight goes by, antenna1 has 3 messages, antenna2 has 4 messages, and the feeder (with it's own antenna) has 6 messages.

      Many of the messages are (or at least should be) duplicates, does the feeder dump1090 ignore these (identical messages received about the same time)?

      Or is this completely wrong? Is 30002/30001 the right port pair, or should I use 30005/30004? The fr24feed connects to 30003, which is BaseStation output port, but dump1090 does not have BaseStation input port.

      -Paavo
      Last edited by ptl; 2014-11-29, 09:36.

      Comment


      • Nevermind, feeding from multiple antennas works at least in nc level.

        I'm still unsure of what port-pair (dump1090 output-input format) to use, any advice is appreciated.

        -Paavo

        Hi,

        a bit more testing at nc level.

        This seems to work (when just looking at what comes from antennahost and what feederhost emits from 30002:

        nc antennahost 30002 | nc feederhost 30001
        But this does not work (more than one antennahost feeding to feederhost):

        nc antennahost1 30002 | nc feederhost 30001
        nc antennahost2 30002 | nc feederhost 30001
        Here both pipes (try to?) push just one message to feederhost, and then nothing moves in the pipe.

        Can feederhost:30001 be opened just once?

        Do I need a fifo or somethng to combine the streams?
        Last edited by ptl; 2014-11-29, 12:07.

        Comment


        • Originally posted by ptl View Post
          Nevermind, feeding from multiple antennas works at least in nc level.

          I'm still unsure of what port-pair (dump1090 output-input format) to use, any advice is appreciated.
          I use 30004/30005; in theory that format provides slightly more metadata (e.g. signal level):

          Code:
          #!/bin/sh
          
          while :
          do
            nc -d localhost 30005 | nc -q1 rpi.lxi 30004
            sleep 15
          done

          Comment


          • Hi,

            since today I am not able to Feed, when I start the Feedingsoftware I'll get following error

            Code:
            minion@bananapi ~ # ./fr24.sh
            fr24feed_arm-rpi_242: Kein Prozess gefunden
            Found 1 device(s):
            0: Generic, RTL2832U, SN: 77771111153705700 (currently selected)
            minion@bananapi ~ # [e]HTTP Response: [HTTP/1.1 404 Not Found]
            Found Rafael Micro R820T tuner
            Max available gain is: 49.60
            Setting gain to: 49.60
            Exact sample rate is: 2000000.052982 Hz
            Gain reported by device: 49.60
            Thats the content of my script

            Code:
            #
            killall fr24feed_arm-rpi_242
            killall dump1090
            sleep 10
            #
            #start dump1090 . we don.t want output so throw it into a black hole (the null device)
            #the symbol at the end of the line says don.t wait for this to finish, just move
            #onto  the next command (note dump 1090 needs to run the dump1090  folder
            #for the built in web page to work)
            #
            cd /root/dump1090
            ./dump1090 --fix --net --net-http-port 8082 --aggressive --enable-agc  --net-beast  --net-sbs-port 30003 --net-ro-port 31001 --quiet > /dev/null &
            cd /root
            #
            #start the fr24 feeder
            #
            export FR24AUTHIP=83.140.247.20
            ./fr24feed_arm-rpi_242 --fr24key=  --bs-ip=127.0.0.1 > /tmp/fr24feed.log &
            Well, it looks like the 242 Software receives an invalid HTTP Command or so...

            €dit: Looks like I got it, i removed the FR24AUTHIP from the Script and now I'm online
            Last edited by equi; 2014-12-09, 16:18.
            Regards,
            T-EDDE7

            Debian 8 Server | jetvision ADS-B USB Dongle | ADS-B Collinear Antenna
            Banana Pi | Mystique SDR R820T2 | stock Antenna

            Comment


            • Since 8 Dec I am not able to feed too.

              fr24feed_arm-le_241s with FR24AUTHIP:

              [i]FR24Feed v241 - built on Feb 20 2014/09:54:09
              [i]Downloading configuration...[e]HTTP Response: [HTTP/1.1 404 Not Found]
              ERROR

              fr24feed_arm-le_241s without FR24AUTHIP:

              [i]FR24Feed v241 - built on Feb 20 2014/09:54:09
              [i]Downloading configuration...execl: No such file or directory
              [e]Could not connect to feed.flightradar24.com, errno: 101
              ERROR
              [e]Could not retrieve configuration from Flightradar24

              fr24feed_arm-le_242s without FR24AUTHIP has the same error:

              [i]FR24Feed v242 - built on Apr 23 2014/09:49:17
              [i]Downloading configuration...execl: No such file or directory
              [e]Could not connect to feed.flightradar24.com, errno: 101
              ERROR
              [e]Could not retrieve configuration from Flightradar24

              Comment


              • Hi Walt,

                with which commands/parameters do you start your FR24 Client ? Is feed.flightradar24.com pingable from your Client ?

                Regards
                Regards,
                T-EDDE7

                Debian 8 Server | jetvision ADS-B USB Dongle | ADS-B Collinear Antenna
                Banana Pi | Mystique SDR R820T2 | stock Antenna

                Comment


                • Hi equi,

                  # ping feed.flightradar24.com
                  PING feed.flightradar24.com (83.140.21.89): 56 data bytes
                  64 bytes from 83.140.21.89: seq=0 ttl=56 time=99.341 ms

                  Command:

                  ./fr24feed_arm-le_242s --fr24key=XXXXX > $PATHLOGFILES/feed.log 2>&1 &

                  Comment


                  • Did you already run the 242 Version before ?
                    Regards,
                    T-EDDE7

                    Debian 8 Server | jetvision ADS-B USB Dongle | ADS-B Collinear Antenna
                    Banana Pi | Mystique SDR R820T2 | stock Antenna

                    Comment


                    • earlier v.241 worked well (with FR24AUTHIP) . I tried v.242 yesterday.

                      Comment


                      • Maybe there is a link between our issues and this posting.

                        Originally posted by piopawlu View Post
                        Thanks again for all the feedback, there should be a new build on Friday that will address most of the reported issues.
                        http://forum.flightradar24.com/threa...0242#post60242

                        Did you tried it today again with the 242 ?
                        Regards,
                        T-EDDE7

                        Debian 8 Server | jetvision ADS-B USB Dongle | ADS-B Collinear Antenna
                        Banana Pi | Mystique SDR R820T2 | stock Antenna

                        Comment


                        • Thanks for the interesting news.
                          v.242 is running just now with same error.

                          Comment


                          • Hm, there is not much I can do from here. You should contact the Support Team and inform them about that faulty Server
                            Regards,
                            T-EDDE7

                            Debian 8 Server | jetvision ADS-B USB Dongle | ADS-B Collinear Antenna
                            Banana Pi | Mystique SDR R820T2 | stock Antenna

                            Comment


                            • I have dump1090 running for flightaware and the FA software is running fine.
                              Now I also installed the fr24feeder for PI: fr24feed_arm-rpi_242
                              I put FR24AUTHIP=83.140.247.20 in /etc/profile
                              I added --net-sbs-port 30003 to the dump1090 command line,
                              but when I start fr24feed_arm-rpi_242 --fr24key=m_y_k_e_y
                              I get:
                              [e]HTTP Response: [HTTP/1.1 404 Not Found]

                              What do I do wrong?

                              Comment


                              • Originally posted by equi View Post
                                Well, it looks like the 242 Software receives an invalid HTTP Command or so...

                                €dit: Looks like I got it, i removed the FR24AUTHIP from the Script and now I'm online
                                Thanks for the info. Commenting out the FR24AUTHIP did the trick for me too. Wonder what has changed to cause this to not work anymore?
                                T-KCMI1

                                Comment

                                Working...
                                X