jscheffl commented on issue #47518:
URL: https://github.com/apache/airflow/issues/47518#issuecomment-2707517184
Error trace #1 I could capture from scheduler POD stdout:
```
[2025-03-07T20:54:18.258+0000] {_client.py:1026} INFO - HTTP Request: PATCH
http://airflow-api-server:8080/execution/task-instances/01957263-27fd-78fb-8e16-57907c484768/st
[2025-03-07T20:54:18.259+0000] {_trace.py:47} DEBUG -
receive_response_body.started request=<Request [b'PATCH']>
[2025-03-07T20:54:18.259+0000] {_trace.py:47} DEBUG -
receive_response_body.complete
[2025-03-07T20:54:18.259+0000] {_trace.py:47} DEBUG -
response_closed.started
[2025-03-07T20:54:18.259+0000] {_trace.py:47} DEBUG -
response_closed.complete
2025-03-07 20:54:18 [debug ] Workload process exited [supervisor]
exit_code=0
2025-03-07 20:54:18 [info ] Task finished [supervisor]
duration=1.4302356929983944 exit_code=0 final_state=success
[2025-03-07 20:59:21 +0000] [62] [INFO] Worker exiting (pid: 62)
[2025-03-07 20:59:21 +0000] [63] [INFO] Worker exiting (pid: 63)
[2025-03-07T20:59:21.527+0000] {scheduler_job_runner.py:232} INFO - Exiting
gracefully upon receiving signal 15
[2025-03-07 20:59:21 +0000] [61] [INFO] Handling signal: term
[2025-03-07T20:59:21.527+0000] {listener.py:37} DEBUG - Calling
'before_stopping' with {'component': <airflow.jobs.job.Job object at
0x7ef6b162d820>}
[2025-03-07T20:59:21.528+0000] {listener.py:38} DEBUG - Hook impls: []
[2025-03-07T20:59:21.528+0000] {listener.py:42} DEBUG - Result from
'before_stopping': []
[2025-03-07T20:59:21.535+0000] {cli_action_loggers.py:97} DEBUG - Calling
callbacks: []
[2025-03-07 20:59:21 +0000] [61] [INFO] Shutting down: Master
stream closed EOF for airflow/airflow-scheduler-0 (scheduler)
```
After this the POD was dead, unfortunately KinD/Liveness probe did not
restart scheduler :-(
--
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]
