Skip to content
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

failover_fetch.py logs in local timezone, not UTC #31

Open
gregcorbett opened this issue Apr 8, 2024 · 0 comments
Open

failover_fetch.py logs in local timezone, not UTC #31

gregcorbett opened this issue Apr 8, 2024 · 0 comments
Labels

Comments

@gregcorbett
Copy link
Member

failover_fetch.py logs in local time zone, not UTC. This causes the check_db_dump_recent.py script to return RETURN_CODE_UNKNOWN if the local time zone is not UTC.

I think the best thing to do is have the failover_fetch.py script always log in UTC. This should fix the issue and make the logs easier to read when the local time zone changes.

Seems relevant: https://stackoverflow.com/questions/6321160/how-to-set-timestamps-on-gmt-utc-on-python-logging

@gregcorbett gregcorbett added the bug label Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant