Hi everyone, I hope you're having a good day!
I just saw that my prefect server is desync with my prefect agent due to a timezone mismatch
(server prefect runs as docker, which have their /etc/localtime point to /usr/share/utc/utc and my agent runs with
prefect agent local start
so it uses my local timezone)
Is there any configuration option that I am missing that could provide a custom timezone to all the dockers launched via the
prefect server start
?
k
Kevin Kho
11/29/2021, 5:16 PM
Are your flows being picked up off schedule?
g
Guillaume Latour
11/29/2021, 5:20 PM
yup, and my agent appears constantly as unreachable since it has not been reached since the last 5 minutes
Guillaume Latour
11/29/2021, 5:21 PM
but if I use the 'quicklaunch' it's alright, my agent is contacted immediately
k
Kevin Kho
11/29/2021, 5:23 PM
Will ask the team for ideas
👍 1
Kevin Kho
11/29/2021, 5:59 PM
Ok so the server time runs in UTC (cloud does also), but your browser should render the time as the local time. I think if your quick run is working, and it triggers the flow immediately, it seems that everything is working as intended. When you register a flow, it will get registered as UTC, unless you specify a timezone-aware schedule with
pendulum
. I think the agent showing as unhealthy might be something else. Are the scheduled flows running delayed by the difference of local time and UTC?
🙌 1
g
Guillaume Latour
11/30/2021, 8:46 AM
Thank you for your response.
Okay I got biased by my timezone idea and did not investigate enough.
So all the flows are delayed by 5 minutes in comparison to local time.
And the server running the prefect agent and the docker prefect server has the same delay. I guess I have to change the ntp and it'll be alright...
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.