-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: [time][e]Failed to synchronize time #116
Comments
So i did some testing, and came to the conclusion that you might have added this line for the fr24 container to your docker compose file:
Is that correct? When i added that line, i would have the same issues as you. You could have also seen the message in the logs like so warning about this: WARNING: Setting timezone via TZ is not supported in this container. fr24feed requires the container has a timezone of GMT (+0). Some other containers don't like the TZ option as well, such as shipxplorer where the timezone needs to be set in a different way. |
Yes correct, I had the TZ defined in my compose file. Thanks! |
Just for completeness, i have TZ set for the following containers: readsb, adsbx, mlathub, piaware, pfclient, rbfeeder, rtlsdirairband, tar1090 shipxplorer has the folllowing instead of TZ:
The rest of the containers have no timezone defined (autoheal, fr24, watchtower). |
As reported here sdr-enthusiasts/docker-flightradar24#116 and here sdr-enthusiasts#101 this container needs to run on GMT timezone
As reported here sdr-enthusiasts/docker-flightradar24#116 and here #101 this container needs to run on GMT timezone
Since 2 weeks I now have this error every 20 minutes in the FR24FEED container logs.
This does not prevent FR24 to work, my data is uploaded correctly.
However it shows the container as Unhealthy (due to the healthcheck I guess).
I checked my host configuration for time sync and it seems ok:
timedatectl
Local time: Fri 2022-12-30 13:33:15 CET
Universal time: Fri 2022-12-30 12:33:15 UTC
RTC time: n/a
Time zone: Europe/Paris (CET, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
The host is a Raspberry 4 running Ubuntu 22.04 ARM8.
Is this an issue with my setup?
Should the healthcheck be modified?
The text was updated successfully, but these errors were encountered: