CODEWITHSUNDEEP
airflow
Joey Baruch
Joey Baruch

Reputation: 5229

Airflow Debugging broken DAGs new CLI

I'm trying to debug a Broken DAG message from the airflow UI, from the accepted answer of Debugging Broken DAGs.

However, with airflow 2.1.0, the airfow list_dags command now prints a usage message:

usage: airflow [-h] GROUP_OR_COMMAND ...

airflow dags list and airflow dags report both give a table with DAGs, but none give the full stack trace I'm looking for.

$ airflow dags report

file             | duration       | dag_num | task_num | dags
=================+================+=========+==========+=================
/myBROKENDAG.py  | 0:00:00.032594 | 0       | 0        |
/example-dag.py  | 0:00:00.009614 | 1       | 9        | example_dag
/mydag2.py       | 0:00:00.007147 | 1       | 1        | mydag2

Any ideas on how to find the full stack trace for a broken DAG with the new CLI?

Upvotes: 2

Views: 469

Answers (1)

Joey Baruch
Joey Baruch

Reputation: 5229

What I could figure so far, is from the container or host running the airflow webserver:

cd dags
python myBROKENDAG.py

this also accounted for the UI-defined connection and printed the full stacktrace.

Credit to this answer

Upvotes: 1

Related Questions