Webserver shows wrong datetime (timezone) in log
See original GitHub issueApache Airflow version
2.2.1 (latest released)
Operating System
Ubuntu 20.04.2 (docker)
Versions of Apache Airflow Providers
- apache-airflow-providers-amazon==2.3.0
- apache-airflow-providers-ftp==2.0.1
- apache-airflow-providers-http==2.0.1
- apache-airflow-providers-imap==2.0.1
- apache-airflow-providers-mongo==2.1.0
- apache-airflow-providers-postgres==2.3.0
- apache-airflow-providers-sqlite==2.0.1
Deployment
Docker-Compose
Deployment details
Docker image build on Ubuntu 20.04 -> installed apache airflow via pip. Localtime in image changed to Europe/Moscow.
Log format ariflow.cfg option: log_format = %%(asctime)s %%(filename)s:%%(lineno)d %%(levelname)s - %%(message)s
What happened
For my purposes it’s more usefull to run dags when it’s midnight in my timezone. So I changed default_timezone option in airflow.cfg to “Europe/Moscow” and also changed /etc/localtime in my docker image.
It works nice:
- dags with @daily schedule_interval runs at midnight
- python`s datetime.now() get me my localtime by default
- airflow webserver shows all time correctly when I change timezone in right top corner
… except one thing. Python logging module saves asctime without timezone (for example “2021-10-31 18:25:42,550”). And when I open task`s log in web interface, it shifts this time forward by three hours (for my timzone), but it’s already in my timzone. It is a little bit confusing 😦
What you expected to happen
I expected to see my timezone in logs 😃
I see several solutions for that:
- any possibility to turn that shift off?
- setup logging timezone in airflow.cfg?
That problem is gone when I change system (in container) /etc/localtime to UTC. But this is very problematic because of the ability to affect a lot of python tasks.
How to reproduce
- build docker container with different /etc/localtime
FROM ubuntu:20.04
ARG DEBIAN_FRONTEND=noninteractive RUN apt-get update && apt-get install -y apt-utils locales tzdata
&& locale-gen en_US.UTF-8
&& ln -sf /usr/share/zoneinfo/Europe/Moscow /etc/localtime ENV LANG=en_US.UTF-8 LANGUAGE=en_US:en AIRFLOW_GPL_UNIDECODE=yesRUN apt-get install -y
python3-pip
&& python3 -m pip install --upgrade pip setuptools wheel
&& pip3 install --no-cache-dir
apache-airflow-providers-amazon
apache-airflow-providers-mongo
apache-airflow-providers-postgres
apache-airflow==2.2.1
celery
… anything else
- run webserver / scheduler / celery worker inside
- open web page -> trigger dag with python operator which prints something via logging
- open done dag -> task log -> find asctime mark in log
- switch timezone in web interface
- watch how airflow thinks that asctime in log in UTC, but it’s not
Anything else
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project’s Code of Conduct
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (7 by maintainers)
Top GitHub Comments
I know what’s the problem, I should change the js file tiLog.478df866123cef0b0eae.js under ‘airflow/www/static/dist’ directly instead of ‘airflow/www/static/js/ti_log.js’. Once I restart the webserver, the datetime became the right one. Thanks for your reply anyway.