You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My question is: is there a way to make airflow scheduler emit verbose logging, such that I can have a better insight into the reason all Windows programs return error code 1; i.e. what exactly is airflow scheduler doing differently than a regular Bash run, given that both of them run as root?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Background: my tasks run by
airflow scheduler
from WSL2. Some of them areBashOperator
s that invoke Windows programs.All of these programs fail by exiting with error code 1.
Running them directly from Bash works perfectly.
The issue is described here: #13108
My question is: is there a way to make
airflow scheduler
emit verbose logging, such that I can have a better insight into the reason all Windows programs return error code 1; i.e. what exactly isairflow scheduler
doing differently than a regular Bash run, given that both of them run asroot
?Beta Was this translation helpful? Give feedback.
All reactions