[ https://issues.apache.org/jira/browse/AIRFLOW-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556284#comment-16556284 ]
Tylar Murray commented on AIRFLOW-1305: --------------------------------------- After running into this myself using airflow v1.9.0 and confirming that the issue was with the dag table in the database. In general the cause seems to be that the scheduler and webserver are unable to reconcile differences between the database and the filesystem. The steps I would suggest to resolve this are: # check permissions on dag definition files to ensure airflow can read the files # restart scheduler and webserver in hopes they can work things out after restart # `airflow initdb` to reset the dag table using the filesystem Anecdotally, `initdb` doesn't affect any dags that still exist, but it will clear dags not found on the filesystem and add ones on the filesystem but missing from the database. > This DAG seems to be exists locally. > ------------------------------------ > > Key: AIRFLOW-1305 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1305 > Project: Apache Airflow > Issue Type: Bug > Reporter: Ting > Priority: Critical > Attachments: 702EE4FC-4E15-490C-AB2B-E2BFAFEB36D7.png > > > All DAGs I created after tutorial show like this, and I can not make it on or > off in UI. > Restart webserver, no use to this. > Also, the dags are not scheduled. > Hope for useful help. -- This message was sent by Atlassian JIRA (v7.6.3#76005)