geocomm-shenningsgard commented on issue #52501:
URL: https://github.com/apache/airflow/issues/52501#issuecomment-3438860499
For whatever it's worth, I'm running into this issue with vanilla Airflow
3.0.2 and 3.1.0 Helm-based installations on EKS.
I'm seeing the following log before it even loads plugins for the Task:
```json
{"timestamp":"2025-10-23T19:36:08.551521Z","level":"warning","event":"Received
message after logging system
shutdown","category":"WatchtowerWarning","filename":"/home/airflow/.local/lib/python3.12/site-packages/watchtower/__init__.py","lineno":464,"logger":"py.warnings"}
```
My configuration is as follows:
```yaml
config:
logging:
remote_logging: "True"
remote_base_log_folder:
"cloudwatch://arn:aws:logs:us-east-1:975049905517:log-group:airflowtest"
remote_log_conn_id: "aws_default"
logging_level: "DEBUG"
env:
- name: "AIRFLOW_CONN_AWS_DEFAULT"
value: "aws://"
redis:
enabled: false
executor: "KubernetesExecutor"
postgresql:
enabled: false
data:
metadataConnection:
user: "postgres"
pass: "<password>"
host: "<blabla>.us-east-1.rds.amazonaws.com"
sslmode: "require"
statsd:
enabled: false
triggerer:
persistence:
enabled: false
extraConfigMaps:
'dag-cm':
data: |
test-dag.py: |
from airflow.sdk import DAG
from airflow.providers.standard.operators.python import
PythonOperator
from datetime import datetime
with DAG(dag_id="example_dag", start_date=datetime(2020, 1, 1)) as
dag:
def print_hello():
print("Hello world!")
def print_goodbye():
print("Goodbye world!")
hello_task = PythonOperator.partial(
task_id="hello_task",
).expand(python_callable=[print_hello, print_goodbye])
hello_task
volumes:
- name: dag-cm
configMap:
name: dag-cm
volumeMounts:
- name: dag-cm
mountPath: /opt/airflow/dags/test-dag.py
subPath: test-dag.py
defaultAirflowTag: "3.1.0"
airflowVersion: "3.1.0"
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
