Announcement

Collapse
No announcement yet.

Data stopped feeding for no reason today

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Data stopped feeding for no reason today

    I noticed that my ADSB data was not feeding today, so I took a deeper look, and it's not even feeding to flightaware.com either. I have changed nothing, and the crazy thing was working fine up until today. I've rebooted the Inovato Quadra computer, restarted F R24, unplugged and reseated the RTL-SDR dongle, etc, etc. Nothing fixes it. Have they made some changes that I need to be aware of? Been running fine with 100% uptime for months and then today it;s crickets. Looking for suggestions other than a hammer
    Tags: None
  • #2
    Here's the first few lines of my log:

    2023-07-03 15:43:57 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to avr-tcp://127.0.0.1:30002
    2023-07-03 15:43:57 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://127.0.0.1:30002)
    2023-07-03 15:43:52 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to avr-tcp://127.0.0.1:30002
    2023-07-03 15:43:52 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://127.0.0.1:30002)
    2023-07-03 15:43:47 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to avr-tcp://127.0.0.1:30002
    2023-07-03 15:43:47 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://127.0.0.1:30002)
    2023-07-03 15:43:42 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to avr-tcp://127.0.0.1:30002
    2023-07-03 15:43:42 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://127.0.0.1:30002)
    2023-07-03 15:43:37 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to avr-tcp://127.0.0.1:30002
    2023-07-03 15:43:37 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://127.0.0.1:30002)
    2023-07-03 15:43:35 | [feed][n]syncing stream result: 1 2023-07-03 15:43:34 | [feed][n]ping 14
    2023-07-03 15:43:32 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to avr-tcp://127.0.0.1:30002

    Comment

    • #3
      Pretty sure avt-tcp hasn't worked for ages

      But thats not your issue. Your chosen feed software isn't responding.

      Not really a fr24 thing. But a decoder.

      Work out whats wrong with what ever version of dump1090 you setup first.

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

      Comment

      • #4
        Well, in a development which is equally as puzzling, the darn thing started working again today. I changed nothing. Very odd.

        Comment

        • #5
          And here we are twp hours later, and it has stopped working again. Absolutely maddening!

          Comment

          Previous template Next
          Working...
          X

          We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

          By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

          I Agree