potiuk opened a new pull request #17157: URL: https://github.com/apache/airflow/pull/17157
In Scheduler, the SchedulerJob was instantiated before demon context was activated. SchedulerJob is a database ORM object from SQL Alchemy and it opens the connection to Postgres: When you activate daemon context, what happens under the hood is forking the process, and while some of the opened sockets were passed to the forks (stdin and stderr but also the opened log file handle), the established socket for DB connection was not passed. As the result, when scheduler was started with --daemonize flag the error `SSL SYSCALL error: Socket operation on non-socket` was raised. The PR moves SchedulerJob initialization to within the context which makes the connection to Postgres initialized after the process has been forked and daemonized. Fixes: #17120 <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md). -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
