You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/01/07 12:21:27 UTC

[GitHub] [airflow] nielspedersen commented on issue #10435: Negsignal.SIGKILL error on macOS

nielspedersen commented on issue #10435:
URL: https://github.com/apache/airflow/issues/10435#issuecomment-756083946


   It's not completely related, but I had a different error message and Google lead me here. So in the hopes that it will help anyone in my boat:
   
   I was/am having this issue on macOS Mojave version 10.14.6 running airflow locally and trying to get it to run tasks on Amazon ECS/Fargate.
   
   In the logs, I'd get the error:
   
   ```
   {local_task_job.py:102} INFO - Task exited with return code Negsignal.SIGABRT
   ```
   
   After a lot of Google, someone suggested trying to `$ export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES`, and that seems to have worked.
   
   The airflow scheduler running locally also hints at this: 
   
   ```
   objc[70653]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called.
   objc[70653]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
   ```
   
   Sorry for commenting at a closed issue, but I hope this can help anyone having the same error
   


----------------------------------------------------------------
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:
users@infra.apache.org