Announcement

Collapse
No announcement yet.

My radar gone offline

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

  • My radar gone offline

    Hi! I'm long time feeder to FR24, but suddenly my radar went offline.

    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2020-05-18 18:37:48.
    [FAIL] FR24 Link: unknown ... failed!
    [ ok ] Receiver: connected (4963 MSGS/0 SYNC).
    [FAIL] FR24 MLAT: not running ... failed!

    then trying to restart feeder
    Code:
    pi@fr24:~ $ sudo fr24feed
    2020-05-18 19:52:44 | [main][i]FR24 Feeder/Decoder
    2020-05-18 19:52:44 | [main][i]Version: 1.0.25-3/generic
    2020-05-18 19:52:44 | [main][i]Built on Apr 8 2020 07:06:55 (HEAD-5e8ef0c.git/Linux/static_armel)
    2020-05-18 19:52:44 | [main][i]Running on: raspbian9
    2020-05-18 19:52:44 | [main][i]Local IP(s): 192.168.1.201
    2020-05-18 19:52:44 | [main][i]Copyright 2012-2020 Flightradar24 AB
    2020-05-18 19:52:44 | [main][i]https://www.flightradar24.com
    2020-05-18 19:52:44 | [main][i]DNS mode: PING
    2020-05-18 19:52:44 | [main][i]Automatic updates are ENABLED
    2020-05-18 19:52:44 | [httpd][w]bind function failed, errno: 98, waiting 1 seconds
    2020-05-18 19:52:44 | [e]PacketSenderConfiguration::fetch_config(): Unable to parse jsoned response
    2020-05-18 19:52:45 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
    2020-05-18 19:52:45 | [main][i]Reader thread started
    2020-05-18 19:52:45 | [main][i]Socket server started
    2020-05-18 19:52:45 | [main][i]MLAT data feed started
    2020-05-18 19:52:45 | [bs][i]Initializing server
    2020-05-18 19:52:45 | [master][i]Starting processing thread
    2020-05-18 19:52:45 | [bs][i]Starting server on 0.0.0.0:30003
    2020-05-18 19:52:45 | [bs][e]Could not bind socket to *:30003, errno=98
    2020-05-18 19:52:45 | [reader][i]Initializing reader
    2020-05-18 19:52:45 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://localhost:30002)
    2020-05-18 19:52:45 | [mlat][i]Waiting for MLAT configuration
    2020-05-18 19:52:45 | [reader][i]Connected to the receiver, configuring
    2020-05-18 19:52:45 | [reader][i]Configured, processing messages
    2020-05-18 19:52:45 | [reader][i]Timestamp source changed from UNKNOWN to SYSTEM-UNCERTAIN
    Have no idea what was happen. What does errno=98 mean? Please help.

    Kirill

  • #2
    You'll need to stop the service before starting it on the console.

    sudo systemctl stop fr24feed
    sudo fr24feed

    when done:
    sudo systemctl restart fr24feed

    Seems for some reason it can't connect to FR24.

    Comment


    • #3
      Did sudo systemctl stop fr24feed then sudo fr24feed but got this

      2020-05-18 20:15:07 | [main][i]FR24 Feeder/Decoder
      2020-05-18 20:15:07 | [main][i]Version: 1.0.25-3/generic
      2020-05-18 20:15:07 | [main][i]Built on Apr 8 2020 07:06:55 (HEAD-5e8ef0c.git/Linux/static_armel)
      2020-05-18 20:15:07 | [main][i]Running on: raspbian9
      2020-05-18 20:15:07 | [main][i]Local IP(s): 192.168.1.201
      2020-05-18 20:15:07 | [main][i]Copyright 2012-2020 Flightradar24 AB
      2020-05-18 20:15:07 | [main][i]https://www.flightradar24.com
      2020-05-18 20:15:07 | [main][i]DNS mode: PING
      2020-05-18 20:15:08 | [main][i]Automatic updates are ENABLED
      2020-05-18 20:15:08 | info | [httpd]Server started, listening on 0.0.0.0:8754
      2020-05-18 20:15:08 | [e]PacketSenderConfiguration::fetch_config(): Unable to parse jsoned response
      2020-05-18 20:15:08 | [d]TLSConnection::ctor(): Enable verify_peer in production code!

      I mean I have the same result. Looks like it does not start

      Also feeding data to Radarbox and it is working good
      Last edited by r5acq; 2020-05-18, 19:45.

      Comment


      • #4
        That's normal. It's the stuff after that point where It connects to server

        But likely not reaching server as said
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #5
          [QUOTE=
          But likely not reaching server as said[/QUOTE]

          Now it's back online and feedimg data. Magic!

          Comment


          • #6
            Have a similar problem, This is the first time I'm offline since the start in 2014
            (Google translated)
            F-ESSB6 is Offline from 2020-08-28 11:20:08 and is not up yet!
            (Google translated)
            Location: Stockholm /Sweden
            Attached Files
            Last edited by Tord; 2020-08-30, 16:32.

            Comment


            • #7
              same here, feeder is working, but no contact to fr24server.
              Also after complete new start of the whole system.
              system: Rpi24
              Location: Berlin/Germany / EDDI90


              Update: Feeder is now working and has contact to the server. All system is running normal.
              Seems the fr24server had a hiccup.
              Last edited by MillerBerlin; 2020-08-30, 10:41.
              EDDI90 | RaspberryPi3B, Nooelec NESDR SMArt, homemade 7Element Collinear Antenna.

              Comment


              • #8
                So I have the same problem and, like the other posters here have had a stable RPI feeder for years.
                Code:
                pi@raspberrypi:~ $ fr24feed-status
                [ ok ] FR24 Feeder/Decoder Process: running.
                [ ok ] FR24 Stats Timestamp: 2020-08-30 11:38:02.
                [FAIL] FR24 Link: connecting ... failed!
                [ ok ] Receiver: connected ( MSGS/ SYNC).
                [FAIL] FR24 MLAT: not running ... failed!
                pi@raspberrypi:~ $
                But 90 mins after it went down, I still can't get it restarted. Hopefully mine will come back as it has for others but I'll try to get an idea of how long it's out for.

                I've rebooted and attempted the commands suggested above but my link to FR24 is still down. Locally, everything's working fine.

                Comment


                • #9
                  This is a dead giveaway..

                  http://feed.flightradar24.com/
                  And as of time of posting. It's offline at cloudflare. As is the main page.
                  Basically there is a cloudflare issue
                  https://www.cloudflarestatus.com/

                  feed.flightradar24.com is one of the sites it connects to during startup.

                  Above screenshot is a version ahead. Although linux its 26-3 and has different JSON errors.

                  'm still on Pi version 25-3 working away.

                  Check your versions. If they have auto-updated and gone up to 26-3 then that's a likely cause also.
                  Last edited by Oblivian; 2020-08-30, 12:16.
                  Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                  Comment


                  • #10
                    Hi Oblivian

                    I do not quite understand this. feed.flightradar24.com webpage is reachable in my webbrowser. But is not resolving to the same addresses as my fr24feed is trying to connect.
                    My radar is offline since about an hour. 3 ip's 185.218.24.22, 185.218.24.23 and 185.218.24.24 are not reachable (as my fr24feed.log says) and my radar states FR24 Link: 'disconnected'. Running fr24feed version 25-3.

                    Is there something wrong at my side? Or are some servers having issues (maybe because of something going on at Cloudflare)?

                    Comment


                    • #11
                      It seems if you have auto-update or reboot enabled. You can't reconnect after it does. But remaining connections to known IPs are fine.

                      And yes, different IPs is normal. That's how cloudflare works. It's distributed across many servers/regions. So you get to different IPs and don't hammer 1 server.

                      For instance from here, it resolves to 104.17.44.52. You can force it using hosts. But if you don't remember to remove it it can cause issues later on.
                      Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                      Comment


                      • #12
                        When i do : "fr24feed-status" on my Raspberry is says FR24 link not connected and MLAT not running. What do I do now ?

                        Comment


                        • #13
                          Thanks Oblivion for the explanations, I've been down for a couple of hours, I cannot get the http://feed.flightradar24.com/ from my browser as it redirects to;
                          https://www.flightradar24.com/share-your-data

                          Cloudflare is still showing down as well so I'll just wait until everything comes back online.

                          My FR24 feed version is 1.0.13-2 and I'm on Pi v7 Wheezy.

                          Feeding FR24 since 11/09/13

                          Comment


                          • #14
                            Originally posted by Oblivian View Post
                            It seems if you have auto-update or reboot enabled. You can't reconnect after it does. But remaining connections to known IPs are fine.

                            And yes, different IPs is normal. That's how cloudflare works. It's distributed across many servers/regions. So you get to different IPs and don't hammer 1 server.

                            For instance from here, it resolves to 104.17.44.52. You can force it using hosts. But if you don't remember to remove it it can cause issues later on.
                            Is it normal that MLAT stops running (after an update and reboot) when the FR24 link is down ?

                            Comment


                            • #15
                              Mine's just come back online. Was down for around 3 hours today but is now back up and running ok.

                              fr24feed version is 1.0.25-3
                              Linux 4.19.66-v7+ armv7l
                              Raspbian GNU/Linux 9 (stretch)

                              I did nothing other than wait for this to fix itself today - (well obviously I spent ages, googling, rebooting and reading forums before I gave up in frustration . When I came back it's working OK)



                              Comment

                              Working...
                              X