feluelle commented on issue #9564:
URL: https://github.com/apache/airflow/issues/9564#issuecomment-716351145


   Hey @potiuk I am running the code from latest master and experiencing this 
issue, too, with following changes to the default config:
   ```
   AIRFLOW_HOME=/opt/airflow
   AIRFLOW__CORE__EXECUTOR=LocalExecutor
   
AIRFLOW__CORE__SQL_ALCHEMY_CONN=postgresql+psycopg2://<sqlalchemy-connection-string>
   AIRFLOW__CORE__FERNET_KEY=<fernet-key>
   AIRFLOW__CORE__MAX_ACTIVE_RUNS_PER_DAG=100
   ```
   That's all. (Probably also occuring in the default config. It might have 
sth. to do with LocalExecutor only?!)
   ```
   Process QueuedLocalWorker-4:
   Process QueuedLocalWorker-9:
   Traceback (most recent call last):
     File "/usr/local/lib/python3.8/multiprocessing/process.py", line 315, in 
_bootstrap
       self.run()
     File 
"/home/airflow/.local/lib/python3.8/site-packages/airflow/executors/local_executor.py",
 line 67, in run
       return super().run()
   Process QueuedLocalWorker-13:
     File "/usr/local/lib/python3.8/multiprocessing/process.py", line 108, in 
run
       self._target(*self._args, **self._kwargs)
     File 
"/home/airflow/.local/lib/python3.8/site-packages/airflow/executors/local_executor.py",
 line 172, in do_work
       key, command = self.task_queue.get()
   Traceback (most recent call last):
     File "<string>", line 2, in get
     File "/usr/local/lib/python3.8/multiprocessing/managers.py", line 835, in 
_callmethod
       kind, result = conn.recv()
     File "/usr/local/lib/python3.8/multiprocessing/connection.py", line 250, 
in recv
       buf = self._recv_bytes()
     File "/usr/local/lib/python3.8/multiprocessing/connection.py", line 414, 
in _recv_bytes
       buf = self._recv(4)
     File "/usr/local/lib/python3.8/multiprocessing/connection.py", line 383, 
in _recv
       raise EOFError
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to