Announcement

Collapse
No announcement yet.

Windows Setup/Feed Migration (virtualVM) Assistance

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • You got the wrong binary for your architecture.

    Comment


    • Sems linux binary "fr24feed" is missing.or corrupted, or mismatching with you machines architecture.

      Either
      (1) the tarball "fr24feed_1.0.24-5_amd64.tgz" did not get downloaded

      OR
      (2) the tarball downloaded, but extrsction of binary "fr24feed" failed

      OR
      (3) the linux binary "fr24feed" did not get copied to folder /usr/bin/


      Please post output of following cimmands to reveal what is missing

      Check binary
      Code:
      ls /usr/share/fr24  
      
      ls /usr/bin/fr24feed

      Check architecture of you machine/os
      Code:
      dpkg --print-architecture  
      
      dpkg --print-foreign-architectures
      Last edited by abcd567; 2020-08-15, 07:23.

      Comment


      • I guess the mismatch break the code.
        Now I am not at all familiar with the difference between amd64 and i386
        is that to be corrected on the linux build or in the way to install it fr24feed?

        Code:
        pi@FlightHost:~$ dpkg --print-architecture
        i386
        pi@FlightHost:~$ ls /usr/share/fr24
        fr24feed_1.0.24-5_amd64.tgz fr24feed_amd64
        pi@FlightHost:~$ ls /usr/bin/fr24feed
        /usr/bin/fr24feed
        pi@FlightHost:~$
        EDIT
        2.1.2. CPU Support
        Both AMD64 and Intel 64 processors are supported.

        They clearly got me on the wrong foot
        Starting from scratch ;-)
        Last edited by Oldertarl; 2020-08-15, 10:01.

        Comment



        • Oldertarl:

          STEP-1:
          Remove amd64 package and binary

          Code:
          sudo rm /usr/share/fr24/fr24feed_1.0.24-5_amd64.tgz  
          
          sudo rm -rf /usr/share/fr24/fr24feed_amd64  
          
          sudo rm /usr/bin/fr24feed

          STEP-2:
          Download, extract, and copy to folder /usr/bin/ the i386 binary

          Code:
          sudo wget -O /usr/share/fr24/fr24feed_1.0.25-3_i386.tgz "https://repo-feed.flightradar24.com/linux_x86_binaries/fr24feed_1.0.25-3_i386.tgz"  
          
          sudo tar xvzf /usr/share/fr24/fr24feed_1.0.25-3_i386.tgz -C /usr/share/fr24  
          
          ​​​​sudo cp /usr/share/fr24/fr24feed_i386/fr24feed /usr/bin/
          Restart fr24feed
          Code:
          sudo systemctl restart fr24feed

          .
          Last edited by abcd567; 2020-08-15, 11:20.

          Comment


          • Was away for the weekend, but was able to install the correct linux version for the listed scripts
            Also installed the fr24feed and dump1090-fa, including graphs1090 with all options I hade before
            I am a very happy man as we speak!

            Almost coming to my last topic on my list for this first feeder, getting the antenna to the best possible position, as 50nM is just poor knowing where I live (north of Luxembourg)

            Thanks a million for the assistance !

            Comment



            • When looking at graphs1090 the range is not showing any data
              Browsing the forums I found that the location is required in dump1090
              When adding the location in DECODER_OPTIONS="--max-range 360 --lat 50.0 --lon 6.0" , removing the --fix
              The service restarts without issues and shows the range data in the graphs
              Is there a special reason this is set to --fix rather than adding the lat and lon that I am missing in oversight?

              Comment


              • Originally posted by Oldertarl View Post
                Is there a special reason this is set to --fix rather than adding the lat and lon that I am missing in oversight?
                The receiver location is determined by adding arguments --lat xxxx --lon yyyy.

                The parameter --fix has nothing to do with the location of receiver. ​​​​It does error correction on some messages which have been damaged by noise in transit, which would otherwise be discarded. The downside of this is that it increases the chances that badly damaged messages could be wrongly “corrected”, producing bad data.

                Usually these bad messages are then filtered out by subsequent processing (this is where the “single tracks” statistic comes from).


                Comment


                • Alright all clear
                  placed --fix back in the options
                  now project "bring the antenna outside" has to start as the 50nM is just not doing the trick for me

                  Comment

                  Working...
                  X