-
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
Healthcheck script last 5min time calculation does not take TZ into account #170
Comments
The container timezone is always in UTC, and when measuring time, we use relative time (seconds since epoch). Having said this, the HealthCheck routine underwent a bunch of changes in the last few days, and this should have solved the issue. If you still see this, please let me know and/or feel free to reopen this issue. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At least on my system, the logs in fr24 container are in UTC time and the healthcheck script always gives:
($TIMESTAMP_NOW - $LOG_LAST_ENTRY_TIMESTAMP)
around 7200 (my TZ is UTC+2), so it's alwaysNo data sent data to fr24feed in past 5 mins. UNHEALTHY
, even though the feeder is working fine.I'm not sure how other systems are configured, but probably some
-u
should be used when interpreting the date taken from log? Now it is assuming the parsed date is in the local TZ, but it's not, at least in my case.The text was updated successfully, but these errors were encountered: