ilyadinaburg commented on issue #25667:
URL: https://github.com/apache/airflow/issues/25667#issuecomment-1217728956
Hi, I'm facing the same issue as @fernhtls with scheduler and triggerer
pods. Running Airflow 2.3.2 on AWS, official helm chart 1.6.0.
Below is the result of livenessProbe command:
```
airflow@airflow2-test-us-west-2-scheduler-0:/opt/airflow$ sh -c
"CONNECTION_CHECK_MAX_COUNT=0 AIRFLOW__LOGGING__LOGGING_LEVEL=ERROR exec
/entrypoint \
airflow jobs check --job-type SchedulerJob --hostname $(hostname)"
No alive jobs found.
```
If I ran it without hostname as @fernhtls suggested:
```
airflow@airflow2-test-us-west-2-scheduler-0:/opt/airflow$ sh -c
"CONNECTION_CHECK_MAX_COUNT=0 AIRFLOW__LOGGING__LOGGING_LEVEL=ERROR exec
/entrypoint \
airflow jobs check --job-type SchedulerJob"
Found one alive job.
```
However, if i run it with IP address of scheduler pod instead of hostname I
got:
```
airflow@airflow2-test-us-west-2-scheduler-0:/opt/airflow$ sh -c
"CONNECTION_CHECK_MAX_COUNT=0 AIRFLOW__LOGGING__LOGGING_LEVEL=ERROR exec
/entrypoint \
airflow jobs check --job-type SchedulerJob --hostname 172.XXX.XXX.XXX"
Found one alive job.
```
So assume that might be related to setting HOSTNAME_CALLABLE in my config:
```
- name: AIRFLOW__CORE__HOSTNAME_CALLABLE
value: 'airflow.utils.net.get_host_ip_address'
```
Anyway, would be great to hear from you.
--
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]
