[
https://issues.apache.org/jira/browse/AIRFLOW-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Beau Barker updated AIRFLOW-3102:
---------------------------------
Summary: Tasks not starting - Processor exited with return code -9 (was:
Tasks not starting)
> Tasks not starting - Processor exited with return code -9
> ---------------------------------------------------------
>
> Key: AIRFLOW-3102
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3102
> Project: Apache Airflow
> Issue Type: Task
> Components: scheduler
> Affects Versions: 1.10.0
> Environment: Docker
> Reporter: Beau Barker
> Priority: Major
>
> I am finding tasks aren't starting for me.
> The scheduler logs are showing "Processor exited with return code -9".
>
> {code:java}
> airflow.utils.dag_processing.DagFileProcessorManager INFO: Started a process
> (PID: 23) to generate tasks for /usr/local/airflow/dags/definitions/my_dag.py
> airflow.jobs.SchedulerJob INFO:
> ================================================================================
> DAG File Processing Stats
> File Path PID Runtime Last Runtime Last Run
> ----------------------------------------------------------- ----- ---------
> -------------- -------------------
> /usr/local/airflow/dags/definitions/my_dag.py 23 2.39s 7.66s
> 2018-09-22T01:27:53
> ================================================================================
> airflow.utils.dag_processing.DagFileProcessorManager INFO: Processor for
> /usr/local/airflow/dags/definitions/my_dag.py finished
> airflow.utils.dag_processing.DagFileProcessorManager WARNING: Processor for
> /usr/local/airflow/dags/definitions/my_dag.py exited with return code -9.
> {code}
>
> After much searching I've narrowed it down to [these lines in
> jobs.py|https://github.com/apache/incubator-airflow/blob/v1-10-stable/airflow/jobs.py#L372]:
>
> {code:java}
> # redirect stdout/stderr to log
> sys.stdout = stdoutt
> sys.stderr = stderr
> {code}
> If I comment those lines, the error doesn't appear and tasks start fine!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
