Announcement

Collapse
No announcement yet.

Irregular feed

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

  • #16
    Could be - but I never saw that when I was running the SBS3 that FR24 provided me with. It started when I began tinkering with the RPI ..

    Oh well .. it feeds, I have my account .. everyone is happy, right?

    Have a great weekend and thanks for trying. You guys are a treasure. Shame FR24 don't step up in their own forum ... @Mike ..
    ENFB.net
    Radarstation KGVL

    Comment


    • #17
      Have a nice weekend as well.

      Comment


      • #18
        ..... and suddenly, since Tuesday midday, both my feeders show uninterrupted lines again. Guess the problem wasn’t on my side after all ...

        ENFB.net
        Radarstation KGVL

        Comment


        • #19
          Originally posted by LN-MOW View Post
          So I got my raspberry to work after my SBS feed was cancelled. However - my feed seems highly irregular.



          But every time I look at my status, I'm showing online and there's a lot of traffic. right now I'm showing 38.1% uptime.

          Linux/generic/static_armel/1.0.23-8
          Updated: 16:31:00 GMT-0400 (Eastern Daylight Time)
          FR24 Link: Connected via UDP
          FR24 Radar Code: T-KGVL5
          Local IP(s): 192.168.1.25
          Aircraft Tracked:
          (ModeS & ADS-B) 35
          Aircraft Uploaded: 23
          Receiver: dvbt, Connected
          MLAT running: N/A


          Any idea why this is?

          About 6 weeks ago I began having the same problem...

          Comment


          • #20
            Any idea what is happening here? I currently have the same issue. Has there been a discovery or resolution?

            Comment


            • #21
              Originally posted by verdi View Post
              Any idea what is happening here? I currently have the same issue. Has there been a discovery or resolution?
              For me it suddenly sorted itself out .. suspecting a software update must have corrected it.

              I do, however, have a probblem with one of my stations continously dropping the feed while still online. 'Online - no data'. I'll reboot with Putty and it will work for a while, then drop out again ..
              ENFB.net
              Radarstation KGVL

              Comment


              • #22
                My FR24 feed magically seems to be behaving over the past 24 hours. We'll see what happens. However I have had atrocious trouble with it for the past couple months. Support has attempted to help me but until the past 24 hours nothing has worked...

                Comment


                • #23
                  So my FR24 feed stopped again after a fairly long period of working. I think the following is what may be happening... from my modem/router log... Started Unicast Maintenance Ranging - No Response received - T3 time-out. I see many people complain of this happening. I think that message means that internet connectivity was interrupted. I am going to try to work with Spectrum to eliminate this issue... When FR24 craps out FA keeps working sending data but the PiAware SkyAware aircraft display stops displaying/updating.

                  Comment


                  • #24
                    I believe that I have traced the problem to the following from the system log of my modem / router: "Started Unicast Maintenance Ranging - No Response received - T3 time-out"
                    That command and activity out of the modem / router (which occurs periodically) causes the Pi to lose internet connectivity to the FR24 part of the software. It doesn't totally bonk FA from continuing to report aircraft activity however it does affect FA from continuing to report and update PiAware SkyAware. A Google of the Unicast Maintenance Ranging activity indicates
                    many people experience the same issue. At this point I am not sure what causes the lack of response or what to do about it. I have calls in to Spectrum tech...


                    The following is from my modem / router. Note the time stamps:

                    Time Priority Description
                    Mon Sep 22 12:47:15 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received -
                    T3 time-out; CM-MAC=b0:c2:87:b4:7a:a6;CMTS-MAC=00:01:5c:8b:c8:5a;
                    CM-QOS=1.1;CM-VER=3.0;


                    The following is from the FlightAware log. Note the time when problem arises:

                    [2020-09-22 12:34 EDT] mlat-client(1080): Results: 18.7 positions/minute
                    [2020-09-22 12:34 EDT] mlat-client(1080): Receiver status: connected
                    [2020-09-22 12:34 EDT] mlat-client(1080): Server status: synchronized with 219 nearby receivers
                    [2020-09-22 12:34 EDT] mlat-client(1080): Receiver: 145.7 msg/s received 74.7 msg/s processed (51%)
                    [2020-09-22 12:38 EDT] 47040 msgs recv'd from dump1090-fa (614 in last 5m); 46963 msgs sent to FlightAware
                    [2020-09-22 12:46 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:46 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: connection lost
                    [2020-09-22 12:46 EDT] faup1090 exited normally
                    [2020-09-22 12:46 EDT] reconnecting to dump1090-fa
                    [2020-09-22 12:47 EDT] mlat-client(1080): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
                    [2020-09-22 12:47 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:47 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:47 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
                    [2020-09-22 12:47 EDT] no ADS-B data program seen listening on port 30005 for 61 seconds, next check in 60s
                    [2020-09-22 12:47 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:48 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:48 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
                    [2020-09-22 12:48 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:48 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
                    [2020-09-22 12:48 EDT] no ADS-B data program seen listening on port 30005 for 121 seconds, next check in 60s
                    [2020-09-22 12:48 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:48 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
                    [2020-09-22 12:48 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:48 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:49 EDT] mlat-client(1080): Receiver status: disconnected
                    [2020-09-22 12:49 EDT] mlat-client(1080): Server status: not synchronized with any nearby receivers
                    [2020-09-22 12:49 EDT] mlat-client(1080): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.8kB/s UDP to server
                    [2020-09-22 12:49 EDT] mlat-client(1080): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
                    [2020-09-22 12:49 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
                    [2020-09-22 12:49 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:49 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:49 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
                    [2020-09-22 12:49 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:49 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:49 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:50 EDT] mlat-client(1080): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
                    [2020-09-22 12:50 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:50 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
                    [2020-09-22 12:50 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:50 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:50 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
                    [2020-09-22 12:50 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
                    [2020-09-22 12:50 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:50 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:50 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:51 EDT] mlat-client(1080): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
                    [2020-09-22 12:51 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:51 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:51 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:51 EDT] no ADS-B data program seen listening on port 30005 for 301 seconds, next check in 60s
                    [2020-09-22 12:51 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
                    [2020-09-22 12:52 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:52 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
                    [2020-09-22 12:52 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
                    [2020-09-22 12:52 EDT] mlat-client(1080): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
                    [2020-09-22 12:52 EDT] mlat-client(1080): Reconnecting in 0.5 seconds

                    To get things to return to normal I have to reboot Pi.
                    Last edited by verdi; 2020-09-22, 20:21.

                    Comment


                    • #25
                      I have recently (within the past 3 weeks) moved to my new location. Previously I was in Tenn on Spectrum. For about a year I had no problem with my Pi or FA or FR24 misbehaving. About 2 months before I moved I started to have crap-out issues. Then I moved to my NY location and immediately started having horrible misbehaving problems. Today I was told that the techs were working a local problem that was supposedly related to my issues. At the same time I think I discovered what my "issues" are. So two things have happened... The techs have supposedly resolved whatever problem they were working on. I researched what the causes of the ranging timeouts are. So I am working one looking at cables, connections, etc. In my satellite business I typically found that ground blocks and splitters etc were a constant source of noise problems. I have eliminated two ground blocks in my internet cable path. I have an appointment for a tech to come to my place tomorrow. We will see what happens and as I monitor the modem logs etc...

                      Comment


                      • #26
                        A router outage, shouldn't drop an internal connection to a pi/local device.

                        The messages relate to localhost being unavailable/denied. The port is closed. The traffic isn't traversing your isp or router at that point.

                        mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused

                        no ADS-B data program seen listening on port 30005 for 301 seconds, next check in 60s

                        That is internal.

                        However, dump1090 stopping will produce this, and stop aircraft showing on your local map at the same time

                        You need to look at the dump1090 logs. That is what happens when a dvbt stick 'wedges' and becomes powered down. Dump1090 cant connect to it, and so wont start. And shut all the ports.

                        Another possibility is ipv6 changes. Or the pi loopback failing/shutting down.

                        But none of that log points to an isp issue. Or you wouldn't see 'connected no data', and piaware would complain it can't reach fa.

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

                        Comment


                        • #27
                          And fyi, your issue is unrelated to this thread.

                          ​​​​​​Look at his statistics screenshot. Lots of dots, then fine, lots of dots.

                          That is a known udp connection issue, and doesnt disconnect the feeder locally.

                          Yours is a local failure looking at your description. Which is different to what this thread was initially started for.
                          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                          Comment

                          Working...
                          X