Announcement

Collapse
No announcement yet.

dump1090 collecting messages; flightradar24.com reporting Online - No data

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

  • #31
    Overnight, fr24feed quit feeding, as has been the practice.

    I created a rule in my main firewall to log traffic to 185.218.24.22:8099, 185.218.24.23:8099 and 185.218.24.24:8099. I'm seeing some traffic, but due to the time stamps not being consistent, it's not possible to directly correlate messages in the fr24feed log with the firewall log. My next step will be to configure a firewall in linux to log the packets, but since they don't have the same port number, I have to figure out what socket to monitor.

    As far as my main firewall is concerned, it can see the traffic.

    I also installed graphs1090 and it's showing that my system is continuously receiving messages. The big mystery is why fr24feed is not sending them.

    Comment


    • #32
      And just like that, it started working again:

      Code:
      eb 22 12:05:31 kaveri fr24feed[133332]: [feed][n]syncing stream: timeout
      Feb 22 12:05:32 kaveri fr24feed[133332]: [feed][n]disconnected
      Feb 22 12:05:32 kaveri fr24feed[133332]: [I] [feed][n]waiting 10 seconds
      Feb 22 12:05:42 kaveri fr24feed[133332]: [feed][n]CYNJ45@185.218.24.24:8099/UDP
      Feb 22 12:05:42 kaveri fr24feed[133332]: [feed][n]connecting
      Feb 22 12:05:42 kaveri fr24feed[133332]: [I] Network thread connecting to 185.218.24.24:8099 for feed CYNJ45
      Feb 22 12:05:43 kaveri fr24feed[133332]: [feed][n]connected via UDP (fd 20)
      Feb 22 12:05:43 kaveri fr24feed[133332]: [feed][n]working
      Feb 22 12:06:09 kaveri fr24feed[133332]: [I] [stats]sent 16 bytes
      Feb 22 12:07:17 kaveri fr24feed[133332]: [feed][n]syncing stream async: 1
      Feb 22 12:07:18 kaveri fr24feed[133332]: [feed][n]syncing stream result: 1
      ...
      Feb 22 12:15:04 kaveri fr24feed[133332]: [feed][n]syncing stream: timeout
      Feb 22 12:16:10 kaveri fr24feed[133332]: [I] [stats]sent 16 bytes
      Feb 22 12:16:22 kaveri fr24feed[133332]: [time][i]Synchronizing time via NTP
      Feb 22 12:16:22 kaveri fr24feed[133332]: [time][e]Time synchronized, offset -37.374 seconds, drift -0.007 seconds/minute
      Feb 22 12:16:37 kaveri fr24feed[133332]: [feed][n]syncing stream async: 1
      Feb 22 12:16:13 kaveri fr24feed[133332]: [time][e]Time jumped backward by -37.38s, resynchronizing
      Feb 22 12:16:13 kaveri fr24feed[133332]: [time][i]Synchronizing time via NTP
      Feb 22 12:16:13 kaveri fr24feed[133332]: [time][e]Time synchronized, offset -0.005 seconds, drift +0.463 seconds/minute
      Feb 22 12:16:16 kaveri fr24feed[133332]: [feed][i]sent 4,0 AC
      ...
      Feb 22 12:16:44 kaveri fr24feed[133332]: [feed][i]sent 4,0 AC
      Feb 22 12:16:45 kaveri fr24feed[133332]: [feed][n]syncing stream: timeout
      Feb 22 12:16:46 kaveri fr24feed[133332]: [feed][n]disconnected
      Feb 22 12:16:46 kaveri fr24feed[133332]: [I] [feed][n]waiting 15 seconds
      Feb 22 12:17:01 kaveri fr24feed[133332]: [feed][n]CYNJ45@185.218.24.22:8099/UDP
      Feb 22 12:17:01 kaveri fr24feed[133332]: [I] Network thread connecting to 185.218.24.22:8099 for feed CYNJ45
      Feb 22 12:17:01 kaveri fr24feed[133332]: [feed][n]connecting
      Feb 22 12:17:01 kaveri fr24feed[133332]: [feed][n]connected via UDP (fd 20)
      Feb 22 12:17:01 kaveri fr24feed[133332]: [feed][n]working
      Feb 22 12:17:01 kaveri fr24feed[133332]: [feed][i]sent 1,0 AC
      ...
      Feb 22 12:17:17 kaveri fr24feed[133332]: [feed][i]sent 5,0 AC
      Feb 22 12:11:58 kaveri fr24feed[133332]: [feed][n]syncing stream async: 1
      Feb 22 12:12:43 kaveri fr24feed[133332]: [feed][n]syncing stream: timeout
      ...
      Feb 22 12:16:10 kaveri fr24feed[133332]: [I] [stats]sent 16 bytes
      Feb 22 12:16:22 kaveri fr24feed[133332]: [time][i]Synchronizing time via NTP
      Feb 22 12:16:22 kaveri fr24feed[133332]: [time][e]Time synchronized, offset -37.374 seconds, drift -0.007 seconds/minute
      Feb 22 12:16:37 kaveri fr24feed[133332]: [feed][n]syncing stream async: 1
      Feb 22 12:16:13 kaveri fr24feed[133332]: [time][e]Time jumped backward by -37.38s, resynchronizing
      Feb 22 12:16:13 kaveri fr24feed[133332]: [time][i]Synchronizing time via NTP
      Feb 22 12:16:13 kaveri fr24feed[133332]: [time][e]Time synchronized, offset -0.005 seconds, drift +0.463 seconds/minute
      Feb 22 12:16:16 kaveri fr24feed[133332]: [feed][i]sent 4,0 AC
      Feb 22 12:16:21 kaveri fr24feed[133332]: [feed][i]sent 4,0 AC
      Feb 22 12:16:27 kaveri fr24feed[133332]: [feed][i]sent 4,0 AC​

      Comment


      • #33
        Since my last post, fr24feed has been fairly consistently stopping in the late evening and restarting in the early afternoon the next day (local time). It's down for typically around 11-13 hours per day, with few exceptions.

        For example, no uploads from 0800-2000, on 2/29 and 3/1, 0800-2100, on 3/2, 0700-1100, with another brief outage around 2100, on 3/3, 0900-2000, on 3/4, 0800-1800, on 3/5.

        During the time it's not uploading, it's collecting data, which I can see using graphs1090.

        I reported this to support. They suggested switching to beast-mode and disabling IPv6, neither of which made any difference. Then they said it might have something to do with there being fewer messages starting from around 2200-2300 local time, due to reduced air traffic, but the number of messages increases again at 0500-0600 the next day, when the air traffic resumes, so if it was only due to the number of messages, it should only be not uploading for 5-6 hours, not double that, although, since fr24feed does connect, it should be able to resume uploading once there is more traffic.

        Even when fr24feed isn't uploading, it says it's tracking and uploading aircraft, which I find points to a problem. If it's not uploading aircraft, it should not be reporting that it's uploading aircraft.

        When it's not uploading, I've tried restarting fr24feed, restarting dump1090 and fr24feed and even rebooting the VM. It doesn't appear that any of those actions consistently make any difference. It stops uploading and resumes uploading for no apparent reason, with no indicative messages in the log.

        I'm unconvinced this is caused by WSL or because I'm not running the software on an RPi, because the pattern is so consistent, so I decided to install PiAware and try feeding to FlightAware to see if it would work properly.

        Yesterday afternoon, I installed the software and within minutes, it was working, including MLAT. It has worked continuously since. This makes me more convinced that the problem lies with fr24feed and the FlightRadar server. I'm going to keep trying to get support to investigate what's happening, but I don't have a lot of confidence they will do anything. My impression is that they know there is a problem, but they can't be bothered to investigate it. I will report back if there are any developments.

        Comment

        Working...
        X