Closed bhumpert closed 9 years ago
Hi,
I didn't reproduced your issue. I saw that you GET /admin/AIRFLOW/log in your request, but the logs from airflow are accessible from /admin/log
curl -IL "http://172.17.0.46:8080/admin/log/?task_id=run_this_last&dag_id=example_bash_operator" master HTTP/1.1 200 OK Content-Length: 285335 Content-Type: text/html; charset=utf-8 Server: TornadoServer/4.2.1
Try to pull the last version of the stask and re-run docker-compose
Those logs at /admin/log/ are very non-informative. You can get a more informative log at the route that I posted. You can navigate there in the gui by going to the graph of any DAG and clicking on a task, then "view log".
Hi,
I've updated the airflow.cfg with full path and I openned an issue in airflow/airbnb https://github.com/airbnb/airflow/issues/484
Thanks.
Puckel.
Whenever I try to access the logs endpoint in the admin console, webserver has the following exception:
The reason for this error is that Airflow is trying to format a string with
{AIRFLOW_HOME}
in it and failing because the keyAIRFLOW_HOME
does not appear in locals. The root of this problem seems to be that the{AIRFLOW_HOME}
key is in the docker-airflowconfig/airflow.cfg
underbase_log_folder
. It's easy enough to fix this problem (by cloning the repo and modifying the config), but I didn't know if there was a step which I was missing that would correctly format the config in the process of bringing the containers up. Really the only step that I'm performing isdocker-compose up -d
.