ThuanDoHung opened a new issue, #34816:
URL: https://github.com/apache/airflow/issues/34816
### Apache Airflow version
2.7.1
### What happened
After upgrade from 2.6.0 to 2.7.1 (try pip uninstall apache-airflow, and
clear dir airflow - remove airflow.cfg), I can start sc
soidamientrung commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-2018278668
> HI, on 2.7.3 i show scheduler was fixed but triggerer was not fixed. i can
not start trigger on daemon, log of triggerer same 2.7.2.
Do you have solution for this er
jens-scheffler-bosch commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1752146995
Some questions regarding your report:
- Have you tried a clean install of Airflow 2.7.1 as well?
- Are you running in a Venv or in a system site package instal
ThuanDoHung commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1753369678
- i run venv
- if start airflow triggerer then run and show log to console, but ctrl+c or
close terminal triggerer killed.
- if start airflow trigger --daemon, i dont show
ThuanDoHung commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1753370697
airflow triggerer --capacity 5 --log-file ./logs/triggerer/triggerer.log
--pid ./triggerer.pid --daemon
_
|__( )_ __/__
jens-scheffler-bosch commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1753930437
Sorry I can not understand you last comment completely.
- Can you please repeat and also add the verbose option via `--verbose` to
the command?
- And can you
ThuanDoHung commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1756834887
Hi,
I try:
Install new server (ubuntu server 22.04.3 LTS) and postgresql 16,
Install airflow:
wget
https://raw.githubusercontent.com/apache/airflow/constraints
ThuanDoHung commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1756844473
I think if run triggerer on daemon, it not start gunicorn (i show gunicorn
start on log file). if i run without daemon, i show starting gunicorn on
console.
--
This is an au
calfzhou commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1761000144
The same issue with 2.7.2, `airflow triggerer -D` not working anymore. In
the error log file, i see that triggerer was kill by a `term` signal `Handling
signal: term` right after
Bisk1 commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1761672715
I tested a couple of versions and can confirm it, the regression took place
between 2.6.2 and 2.6.3 - in 2.6.3 (and later), after starting triggerer with
-D option, `airflow-triggere
ThuanDoHung commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1761794857
> I tested a couple of versions and can confirm it, the regression took
place between 2.6.2 and 2.6.3 - in 2.6.3 (and later), after starting triggerer
with -D option, `airflow-
Bisk1 commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1761974585
I think I isolated the code change that caused the problem - the problem
starts to appear after this commit:
https://github.com/apache/airflow/commit/d6cc9e4bb1efe9713eccd8e62e46f11b
Bisk1 commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1762156063
After debugging I think I understand the problem fully. Here is what happens
when we run triggerer in daemon mode on current main.
1. Triggerer's main thread creates triggerer_
jens-scheffler-bosch commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1762218787
Wow. Cool analysis. Respect. This is not an easy catch! Thanks for investing
the time locating the root!
Yes, with this explanaition it all makes much sense. Hap
Bisk1 commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1762232940
Also contrary to the original issue description and I don't see any problem
with the scheduler in daemon mode. But maybe it was a communication issue.
--
This is an automated messa
potiuk commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1762994839
Very cool analysis indeed. It all makes perfect sense. Thanks for both -
analysis and the fix!
--
This is an automated message from the Apache Git Service.
To respond to the messa
potiuk closed issue #34816: Airflow 2.7.1 can not start Scheduler & trigger
URL: https://github.com/apache/airflow/issues/34816
--
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.
ThuanDoHung commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1798300105
HI, on 2.7.3 i show scheduler was fixed but triggerer was not fixed. i can
not start trigger on daemon, log of triggerer same 2.7.2.
--
This is an automated message from the
potiuk commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1798307908
> HI, on 2.7.3 i show scheduler was fixed but triggerer was not fixed. i can
not start trigger on daemon, log of triggerer same 2.7.2.
Can you please open a new issue about it
boring-cyborg[bot] commented on issue #34816:
URL: https://github.com/apache/airflow/issues/34816#issuecomment-1751774659
Thanks for opening your first issue here! Be sure to follow the issue
template! If you are willing to raise PR to address this issue please do so, no
need to wait for ap
20 matches
Mail list logo
