GitHub user potiuk added a comment to the discussion: Airflow Segmentation Faults after DagProcessor Crash
SEGFAULT is almost always the result of some library you have locally that has bugs. Airlfow is Python-only so there is really no place where segfault could be generated from within. The thing is that you should find the core file (aprently core is dumped) and look at it with gdb or similar to find out what caused it - that's the nature of SEGFAULT. You can look for AI or some tutorial help on how to do it. Also look at other discussions and issues here that mention SIGSEGV - you can see a number of workarounds for some typical libraries - and issues - especially on MacOS there are poorly written libraries that mix threading and forking and it might cause problem - there is something about PROXY. But other than that - you need to find out which native library is causing it. Converted to a discussion GitHub link: https://github.com/apache/airflow/discussions/51451#discussioncomment-13380983 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
