Announcement

Collapse
No announcement yet.

FlightRadar24 - Radar Status = Offline yet everything is running ok.

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

  • FlightRadar24 - Radar Status = Offline yet everything is running ok.

    So this morning I got an email that my Radar in FlightRadar24 app shows "Offline" so I checked the laptop running the software and everything checked out ok. I even rebooted and started everything anew. Piaware is running, MLAT, Beast, and everything is running perfectly. Dump1090 is fine. But the app still shows the Radar to be offline. What gives?

    I took screenshots of everything.

  • #2
    Same thing for me. And besides that, my stats was gone and my account downgraded to basic.

    My feeder has been up and working (responding to the local web-interface) with aircrafts listed as tracked all the time.

    Comment


    • #3
      Good morning,

      I figured out the problem. The software that runs the Feeder was outdated and I updated it. Everything is running OK now.

      So, here's what I did.

      First, stop the feeder and terminate the software (your feeder IP address:8754)
      On your Linux box: sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_linux.sh)"
      It will ask you for your email, sharing key, etc.
      Restart the feeder and REBOOT the Linux box.
      Restart piaware

      Let me know if this works for you, good luck!!

      Comment


      • #4
        About a week ago my FR24 feed stopped - FA is still feeding (including MLAT), and the Pi hadn't rebooted.

        I checked the version of FR, and got back this:


        pi@PiPlane3B:~ $ sudo apt-get update
        Hit:1 http://www.flightaware.com/adsb/piaware/files/packages bullseye InRelease
        Hit:2 https://linux.teamviewer.com/deb stable InRelease
        Hit:3 https://repo-feed.flightradar24.com flightradar24 InRelease
        Hit:4 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
        Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease
        Reading package lists... Done
        pi@PiPlane3B:~ $ sudo apt-cache policy fr24feed
        fr24feed:
        Installed: 1.0.29-10
        Candidate: 1.0.29-10
        Version table:
        *** 1.0.29-10 100
        100 /var/lib/dpkg/status


        ​Which I interpret as saying I have the latest version of FR.
        When I check the status of my fr24feed, I see this:

        pi@PiPlane3B:~ $ sudo fr24feed-status
        FR24 Feeder/Decoder Process: running.
        FR24 Stats Timestamp: 2023-12-13 16:53:03.
        FR24 Link: unknown ... failed!
        Receiver: connected (11589834 MSGS/0 SYNC).
        FR24 MLAT: not running ... failed!


        ​I searched the forum for the string "FR24 Link: unknown ... failed!"


        and quickly found myself in over my (non-Linux savvy) head.
        I expect the solution here is "obvious" to a more experienced Linux and FR24/FA user - maybe someone can point me in the right direction?

        Thanks.

        Comment


        • #5
          You are a victim of this
          Since not announced officially, and going by a number of feeders software who stopped working this month and asked here for help. Only for it to work after a forced update. It is presumed we can take this error seen as the reason if you have auto update disabled you may face your feeders stopping. Be warned.


          are you on a standard Pi software base?
          Abcd has some details on updating the .deb directly using wget
          But for some reason your repo is not updating

          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment


          • #6
            Oblivian thanks for the help. The confusing (to me) aspect here is that when I do a version check, I'm told I'm on the current version

            pi@PiPlane3B:~ $ sudo apt-cache policy fr24feed
            fr24feed:
            Installed: 1.0.29-10
            Candidate: 1.0.29-10
            Version table:
            *** 1.0.29-10 100
            100 /var/lib/dpkg/status


            When I run
            sudo apt-get update
            sudo apt-get install fr24feed​


            I get back
            Reading package lists... Done
            Building dependency tree... Done
            Reading state information... Done
            fr24feed is already the newest version (1.0.29-10).
            The following package was automatically installed and is no longer required:
            libminizip1
            Use 'sudo apt autoremove' to remove it.
            0 upgraded, 0 newly installed, 0 to remove and 236 not upgraded.


            ​which is obviously less than the version you reference here (1.0.44) - why is my Pi confused on this?

            So I guess I need to manually force it from the repository (?)
            Wget https://repo-feed.flightradar24.com/...44-0_armhf.deb
            sudo dpkg -i fr24feed_1.0.44-0_armhf.deb​


            I'm running a pretty vanilla install (just feeding FA and FR24) - on Bullseye, which was current when I set this up (it's just been chugging away since July '22).​

            As noted, I'm pretty much a Linux noob, so I haven't monkeyed with anything there. It appears Bookworm came out a couple months ago - and I haven't installed it. Should I consider doing that, or perhaps just update Bullseye (I'm sure there are fixes to that) without going all the way to Bookworm?

            If so, is there a preferred order to this - update Raspbian first, and then FR24?
            Last edited by SD_Mark; 2023-12-13, 19:08.

            Comment


            • #7
              You need to totally reinstall for bookworm. Don't go that far unless you get a new pi 5 at this time.

              No answer sorry. Possibly something to do with your build/install process at the start..True 64 and Linux always behind Pi build.
              May need manual repo file update.

              Wget the url I posted
              Then
              Sudo dpkg -i fr24feed_1.0.44-0_armhf.deb
              ​​​
              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment


              • #8
                It's copy pasted the '...'s

                You need to get the full url from rt Click/long click not copy the text

                I've made a quick code edit to fix that
                Last edited by Oblivian; 2023-12-13, 19:21.
                Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                Comment


                • #9
                  The file was found and I installed it. ​After a reboot:
                  pi@PiPlane3B:~ $ frstat
                  FR24 Feeder/Decoder Process: running.
                  FR24 Stats Timestamp: 2023-12-13 19:35:08.
                  FR24 Link: connected [UDP].
                  FR24 Radar: T-KCRQ46.
                  FR24 Tracked AC: 148.
                  Receiver: connected (51133 MSGS/0 SYNC).
                  FR24 MLAT: not running ... failed!


                  ​So looks like it's mostly working, but MLAT isn't happy. Maybe that will resolve itself in time?

                  Thanks for getting me back online.

                  Comment


                  • #10
                    Never mind. I found this:
                    This only relates to volunteer receivers and NOT Flightradar24 equipment. No action needed if you have receiver provided by Flightradar24. Hi guys, As a lot of you have seen, we sent out an email requesting that MLAT be disabled if sharing with other networks. There is a lot of confusion revolving around this so this post


                    So I probably already turned it off (am feeding FA) and forgot I did so.

                    Comment


                    • #11
                      After reading the issues you had with your Pi, I will leave my one install alone and repurpose the Pi for something else. Yikes!

                      Comment

                      Working...
                      X