Announcement

Collapse
No announcement yet.

Fr24feed - failed to synchronize time

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

  • Fr24feed - failed to synchronize time

    On one of my feeders it frequently stops working, getting stuck in the status shown below.

    Version is 1.0.19-15.

    1. Is this a known problem?

    2. Is there a list of bugs in different versions and a "latest released version" list?


    FR24 Feeder/Decoder Process: running.
    FR24 Stats Timestamp: 2018-10-12 01:41:14.
    FR24 Link: failure ... failed!
    Receiver: connected (1329467514 MSGS/0 SYNC).
    FR24 MLAT: ok [UDP].
    FR24 MLAT AC seen: 6.



    2018-10-12 00:59:44 | [time][i]Synchronizing time via NTP
    2018-10-12 00:59:44 | [time][e]Failed to synchronize time
    2018-10-12 00:59:46 | [time][i]Synchronizing time via NTP
    2018-10-12 00:59:46 | [time][e]Failed to synchronize time
    2018-10-12 00:59:48 | [time][i]Synchronizing time via NTP
    2018-10-12 00:59:48 | [time][e]Failed to synchronize time
    2018-10-12 00:59:50 | [time][i]Synchronizing time via NTP
    2018-10-12 00:59:50 | [time][e]Failed to synchronize time
    2018-10-12 00:59:51 | [mlat][i]Received ADS-B time references AC:
    2018-10-12 00:59:51 | [mlat][i] 394A01
    2018-10-12 00:59:51 | [mlat][i] 394A06
    2018-10-12 00:59:51 | [mlat][i] 39BD26
    2018-10-12 00:59:51 | [mlat][i] 400A66
    2018-10-12 00:59:51 | [mlat][i] 40621B
    2018-10-12 00:59:51 | [mlat][i] 4242D9
    2018-10-12 00:59:51 | [mlat][i] 424941
    2018-10-12 00:59:51 | [mlat][i] 45D065
    2018-10-12 00:59:51 | [mlat][i] 758525
    2018-10-12 00:59:51 | [mlat][i] 78023C
    2018-10-12 00:59:51 | [mlat][i] 78070A
    2018-10-12 00:59:51 | [mlat][i] 7813C2
    2018-10-12 00:59:51 | [mlat][i]Pinging the server
    2018-10-12 00:59:51 | [mlat][i]Stats 2789530/0
    2018-10-12 00:59:52 | [time][i]Synchronizing time via NTP
    2018-10-12 00:59:52 | [time][e]Failed to synchronize time
    2018-10-12 00:59:54 | [feed][i]Downloading configuration
    2018-10-12 00:59:54 | [e]Socket is not valid, errno: 24
    2018-10-12 00:59:54 | ERROR
    2018-10-12 00:59:54 | [e]Could not retrieve configuration from Flightradar24
    2018-10-12 00:59:54 | [feed][i]Failed, Sleeping 30 seconds
    2018-10-12 00:59:54 | [time][i]Synchronizing time via NTP
    2018-10-12 00:59:54 | [time][e]Failed to synchronize time
    2018-10-12 00:59:56 | [time][i]Synchronizing time via NTP
    2018-10-12 00:59:56 | [time][e]Failed to synchronize time
    2018-10-12 00:59:58 | [time][i]Synchronizing time via NTP
    2018-10-12 00:59:58 | [time][e]Failed to synchronize time
    2018-10-12 01:00:00 | [time][i]Synchronizing time via NTP
    2018-10-12 01:00:00 | [time][e]Failed to synchronize time
    2018-10-12 01:00:02 | [time][i]Synchronizing time via NTP
    2018-10-12 01:00:02 | [time][e]Failed to synchronize time
    2018-10-12 01:00:04 | [time][i]Synchronizing time via NTP
    2018-10-12 01:00:04 | [time][e]Failed to synchronize time
    2018-10-12 01:00:06 | [time][i]Synchronizing time via NTP
    2018-10-12 01:00:06 | [time][e]Failed to synchronize time
    2018-10-12 01:00:08 | [time][i]Synchronizing time via NTP
    2018-10-12 01:00:08 | [time][e]Failed to synchronize time
    2018-10-12 01:00:10 | [time][i]Synchronizing time via NTP
    2018-10-12 01:00:10 | [time][e]Failed to synchronize time
    2018-10-12 01:00:11 | [mlat][i]Pinging the server
    2018-10-12 01:00:11 | [mlat][i]Stats 2789530/0
    2018-10-12 01:00:12 | [time][i]Synchronizing time via NTP
    2018-10-12 01:00:12 | [time][e]Failed to synchronize time
    F-ESDF1, F-ESGG1, F-ESGP1, F-ESNK1, F-ESNV2, F-ESNV3 F-ESSL4, F-LFMN3
    P-ESGR, P-ESIA, P-ESIB, P-ESGF
    mrmac (a) fastest.cc

  • #2
    1329467514 is a 7 year old timestamp so you seem to have some type of clock issue.
    F-KDAG1

    Comment


    • #3
      pi@raspberrypi:~ $ date -d @1329467514
      Fri Feb 17 03:31:54 EST 2012

      Comment


      • #4
        Looks like the time sync failure is just part of a wider "failed to connect" issue:

        [I]FR24 Link: failure ... failed!
        2018-10-12 00:59:54 | [feed][i]Downloading configuration
        2018-10-12 00:59:54 | [e]Socket is not valid, errno: 24
        2018-10-12 00:59:54 | ERROR
        2018-10-12 00:59:54 | [e]Could not retrieve configuration from Flightradar24
        2018-10-12 00:59:54 | [feed]Failed, Sleeping 30 seconds

        No idea what language the FR24feed client is written in but socket error 24 googles to "too many open files", but again that could well be the result of not being able to connect (e.g. the client connects to about six different NTP hosts each time sync run). Does the unit definitely have a good network connection? Have you tries the obvious e.g. reboot; run "sudo ps ax" and see what's running?

        The current version of Fr24feed is 1.0.23-7 which was released a couple of weeks ago so also points to the unit not having a reliable network connection.

        Comment


        • #5
          Thanks for ideas.

          1. There is nothing wrong with the clock on the Rpi itself, it is synced to ntp, running decoding, feeding and mlat for a private network at the same time without problem. No known network problems.

          2. A reboot solves the issue, until it comes back a few days or a week later. Stopping and starting just fr24feed also solves he problem, so the rest of the system is OK.

          3. The file system is read-only , logs on a ram-disk, but that is no problem. I run more than 10 identical systems using the same image without problem.

          4. I have turned off auto-update, that s why it is on 1.0.19-15, nothing to do with the network. A manual update to latest ran without issue. Now we see if that has solved the problem or if it is coming back.

          /M
          F-ESDF1, F-ESGG1, F-ESGP1, F-ESNK1, F-ESNV2, F-ESNV3 F-ESSL4, F-LFMN3
          P-ESGR, P-ESIA, P-ESIB, P-ESGF
          mrmac (a) fastest.cc

          Comment


          • #6
            Not much left that's different to the other identical systems that work ok - just the Pi/PSU and the network connection (hardware/signal if it's WiFi)...

            Comment

            Working...
            X