Announcement

Collapse
No announcement yet.

No Issue's For Years Now This.....

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

  • No Issue's For Years Now This.....

    Hi Guys

    I am hoping someone can help me with this issue. I have a generic DVT and been running it for years (or 18 months) with no issue's, now suddenly with the new software that has had no issue's (and been installed for a few months), is producing a 'could not connect' error.

    Code:
    2016-01-14 23:18:13 | [main][i]FR24 Feeder/Decoder [0x02107000]
    2016-01-14 23:18:13 | [main][i]Version: 1.0.16-6/generic
    2016-01-14 23:18:13 | [main][i]Built on Dec 10 2015 12:18:54 (r:284/Windows/i386)
    2016-01-14 23:18:13 | [main][i]Copyright 2012-2015 Flightradar24 AB
    2016-01-14 23:18:13 | [main][i]<NOT ALLOWED LINKS>)
    2016-01-14 23:18:13 | [httpd][i]Server started, listening on 0.0.0.0:8754
    2016-01-14 23:18:13 | [main][i]Reader 0 started
    2016-01-14 23:18:13 | [main][i]Socket server started
    2016-01-14 23:18:13 | [time][i]Synchronizing time via NTP
    2016-01-14 23:18:13 | [master][i]Starting processing thread
    2016-01-14 23:18:13 | [reader][i][0]Initializing reader
    2016-01-14 23:18:13 | [bs][i]Initializing server
    2016-01-14 23:18:13 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw)
    2016-01-14 23:18:13 | [bs][i]Starting server on 0.0.0.0:30003
    2016-01-14 23:18:13 | [reader][i][0]Connected to the receiver, authenticating
    2016-01-14 23:18:13 | [reader][i][0]Authenticated, processing messages
    2016-01-14 23:18:23 | [time][i]Time synchronized correctly, offset +3.0267 seconds
    2016-01-14 23:18:23 | [main][i]Feed Network client started
    2016-01-14 23:18:23 | [main][i]RAW data server started
    2016-01-14 23:18:23 | [feed][i]Downloading configuration
    2016-01-14 23:18:23 | [raw][i]Initializing server
    2016-01-14 23:18:23 | [raw][i]Starting server on 0.0.0.0:30002
    2016-01-14 23:18:24 | [feed][c]Interval: 5s
    2016-01-14 23:18:24 | [feed][c]Latitude: <REDACTED>
    2016-01-14 23:18:24 | [feed][c]Longitude: <REDACTED>
    2016-01-14 23:18:24 | [feed][c]GND: YES
    2016-01-14 23:18:24 | [feed][c]NonADSB: YES
    2016-01-14 23:18:24 | [feed][c]Timestamps: optional
    2016-01-14 23:18:24 | [feed][c]Send extended-addr data (non-ICAO, DF18): disabled
    2016-01-14 23:18:24 | [feed][c]Max range AIR: 350.0nm
    2016-01-14 23:18:24 | [feed][c]Max range GND: 100.0nm
    2016-01-14 23:18:24 | [feed][i]defined 1 server
    2016-01-14 23:18:24 | [feed][n]<REDACTED>@83.140.21.66:8099/UDP
    2016-01-14 23:18:24 | [stats][i]Stats thread started
    2016-01-14 23:18:24 | [feed][n]connecting
    2016-01-14 23:19:04 | [feed][e]Could not connect!
    2016-01-14 23:19:04 | [feed][n]Error: Could not connect! (fd -1)
    2016-01-14 23:19:04 | [feed][n]waiting 6 seconds
    2016-01-14 23:19:10 | [feed][n]<REDACTED>@83.140.21.66:8099/UDP
    2016-01-14 23:19:10 | [feed][n]connecting
    2016-01-14 23:19:51 | [feed][e]Could not connect!
    2016-01-14 23:19:51 | [feed][n]Error: Could not connect! (fd -1)
    Sharing key is fine, firewall is causing no issue's (not blocking), and it was working this morning.

    Any one that can assist would be greatly appreciated.

  • #2
    I had the same issue this afternoon and it solved itself.
    Surprisingly FR24 stats don't show a downtime at all, but does show much fewer aircraft then usual, so I think it was a problem on their end.

    Comment


    • #3
      I had the exact same problem today also. Did a refresh reinstall and after a while it started working again. Suspect it was a problem at fr24 end.

      Comment


      • #4
        I also had to do a reinstall. Problem has not reoccurred.

        Comment

        Working...
        X