0

We installed Airflow 1.7, and used it for several months. I used PIP to uninstall ariflow 1.7 and install 1.9 (gory details are [here|airflow initdb failed: ImportError: No module named log.logging_mixin

Since then, I haven't had a single DAG run. I renamed and moved log files to match the 1.9 expectations, but still nothing happens.

I have a "run every 40 minutes" DAG, it hasn't run since 3/28. When I manually trigger it, no log file is created, nothing happens except I get a running DAG listed under "DAG Runs" (I do NOT get anything listed under "Recent Tasks", and "Last Run" does not get updated.

I have a "Run once" DAG that I created. I triggered it, same behavior.

I have also tried running the example_bash_operator DAG. Same behavior.

Greg Dougherty
  • 3,281
  • 8
  • 35
  • 58
  • 1
    Can you post the logs from the scheduler and the worker? – Simon D Apr 20 '18 at 12:43
  • I assumed (word chosen w/ malice aforethought) that nohup airflow webserver -p 8080 would kick everything off. I was wrong. @tobi6 if you want to post your comment as an answer i'll give you the credit – Greg Dougherty Apr 20 '18 at 16:17

1 Answers1

1

The Airflow documentation is a bit thin on all the requirements needed to run DAGs correctly.

Aside from the webserver, make sure the scheduler is running as well. Also check if the DAG is configured with a correct schedule and there is scheduling information in the "Task Instance Information" page.

See this answer for more "checkpoints": Airflow 1.9.0 is queuing but not launching tasks

tobi6
  • 8,033
  • 6
  • 26
  • 41