zsdyx commented on issue #15938:
URL: https://github.com/apache/airflow/issues/15938#issuecomment-1343758468

   Provide some important logs first. After the service is start, Output after 
each interval.
   ```
   Exiting gracefully upon receiving signal 15
    Sending Signals.SIGTERM to group 20. PIDs of all processes in the group: 
[20]
   
   ```
   
   ENV
   GCP: k8s
   python: 3.10
   airflow: 2.4.1
   excutor:CeleryExecutor
   ```
   INFO,"       <TaskInstance: vi_base_schema_scan.vi_base_schema_scan 
scheduled__2022-12-08T15:45:00+00:00 [running]> in state 
STARTED",2022-12-09T01:54:53.346995938Z
   INFO,"       <TaskInstance: aa_table_lineage.aa_table_lineage 
scheduled__2022-12-08T21:00:00+00:00 [running]> in state 
STARTED",2022-12-09T01:54:53.346992107Z
   INFO,"       <TaskInstance: vi_base_table_lineage.vi_base_table_lineage 
scheduled__2022-12-08T19:50:00+00:00 [running]> in state 
STARTED",2022-12-09T01:54:53.346986570Z
   INFO,[2022-12-09T01:54:53.346+0000] {celery_executor.py:534} INFO - Adopted 
the following 128 tasks from a dead executor,2022-12-09T01:54:53.346933893Z
   INFO,[2022-12-09T01:54:52.470+0000] {settings.py:543} INFO - Loaded 
airflow_local_settings from /opt/airflow/config/airflow_local_settings.py 
.,2022-12-09T01:54:52.470955248Z
   INFO,[2022-12-09T01:54:52.468+0000] {settings.py:58} INFO - Configured 
default timezone Timezone('UTC'),2022-12-09T01:54:52.469795791Z
   INFO,[2022-12-09T01:54:52.465+0000] {scheduler_job.py:1374} INFO - Resetting 
orphaned tasks for active dag runs,2022-12-09T01:54:52.466143332Z
   INFO,[2022-12-09T01:54:52.462+0000] {manager.py:163} INFO - Launched 
DagFileProcessorManager with pid: 20,2022-12-09T01:54:52.465243117Z
   INFO,[2022-12-09T01:54:52.450+0000] {executor_loader.py:107} INFO - Loaded 
executor: CeleryExecutor,2022-12-09T01:54:52.451308381Z
   INFO,[2022-12-09T01:54:52.258+0000] {scheduler_job.py:706} INFO - Processing 
each file at most -1 times,2022-12-09T01:54:52.259176063Z
   INFO,[2022-12-09T01:54:52.258+0000] {scheduler_job.py:701} INFO - Starting 
the scheduler,2022-12-09T01:54:52.258964320Z
   INFO, _/_/  |_/_/  /_/    /_/    /_/  
\____/____/|__/,2022-12-09T01:54:52.258959593Z
   INFO,___  ___ |  / _  /   _  __/ _  / / /_/ /_ |/ |/ 
/,2022-12-09T01:54:52.258955844Z
   INFO,____  /| |_  /__  ___/_  /_ __  /_  __ \_ | /| / 
/,2022-12-09T01:54:52.258952230Z
   INFO, ____    |__( )_________  __/__  /________      
__,2022-12-09T01:54:52.258946962Z
   INFO,  ____________       _____________,2022-12-09T01:54:52.258915119Z
   INFO,,2022-12-09T01:54:48.293564892Z
   INFO,[2022-12-09T01:54:43.752+0000] {scheduler_job.py:775} INFO - Exited 
execute loop,2022-12-09T01:54:43.752660415Z
   INFO,[2022-12-09T01:54:43.752+0000] {process_utils.py:98} INFO - Sending the 
signal Signals.SIGTERM to process 20 as process group is 
missing.,2022-12-09T01:54:43.752538440Z
   INFO,[2022-12-09T01:54:43.752+0000] {process_utils.py:84} INFO - Sending the 
signal Signals.SIGTERM to group 20,2022-12-09T01:54:43.752411066Z
   INFO,[2022-12-09T01:54:43.752+0000] {process_utils.py:129} INFO - Sending 
Signals.SIGTERM to group 20. PIDs of all processes in the group: 
[],2022-12-09T01:54:43.752361863Z
   INFO,"[2022-12-09T01:54:43.701+0000] {process_utils.py:79} INFO - Process 
psutil.Process(pid=20, status='terminated', exitcode=0, started='01:49:51') 
(20) terminated with exit code 0",2022-12-09T01:54:43.702040509Z
   INFO,[2022-12-09T01:54:43.529+0000] {process_utils.py:84} INFO - Sending the 
signal Signals.SIGTERM to group 20,2022-12-09T01:54:43.529318886Z
   INFO,[2022-12-09T01:54:43.528+0000] {process_utils.py:129} INFO - Sending 
Signals.SIGTERM to group 20. PIDs of all processes in the group: 
[20],2022-12-09T01:54:43.529225207Z
   INFO,[2022-12-09T01:54:42.526+0000] {scheduler_job.py:173} INFO - Exiting 
gracefully upon receiving signal 15,2022-12-09T01:54:42.527221527Z
   ```


-- 
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]

Reply via email to