Child process keeps dying during airflow standalone on Raspberry Pi

[wyfok]

Apache Airflow version

3.0.3

If "Other Airflow 2 version" selected, which one?

No response

What happened?

During following the quick start page , the api-server keeps waiting for child process but child process keeps dying.

[2025-07-21T20:16:41.702+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.filesystem.FSHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
[2025-07-21T20:16:41.707+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.package_index.PackageIndexHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
standalone | Starting Airflow Standalone
standalone | Checking database is initialized
standalone | Database ready
api-server | [2025-07-21T20:16:54.156+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.filesystem.FSHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
api-server | [2025-07-21T20:16:54.160+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.package_index.PackageIndexHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
triggerer | [2025-07-21T20:16:54.217+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.filesystem.FSHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
triggerer | [2025-07-21T20:16:54.220+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.package_index.PackageIndexHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
api-server | ____________ _____________
api-server | ____ |( )_______ / /________ __
api-server | ____ /| |_ /__ / / __ / __ _ | /| / /
api-server | ___ ___ | / _ / _ / _ / / // / |/ |/ /
api-server | // |// // // // _//|/
api-server | [2025-07-21T20:16:54.309+0200] {api_server_command.py:92} INFO - Running the uvicorn with:
api-server | Apps: all
api-server | Workers: 4
api-server | Host: 0.0.0.0:8080
api-server | Timeout: 120
api-server | Logfiles: -
api-server | =================================================================
api-server | INFO: Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
api-server | INFO: Started parent process [48987]
dag-processor | [2025-07-21T20:16:54.326+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.filesystem.FSHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
dag-processor | [2025-07-21T20:16:54.335+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.package_index.PackageIndexHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
scheduler | [2025-07-21T20:16:54.578+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.filesystem.FSHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
scheduler | [2025-07-21T20:16:54.594+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.package_index.PackageIndexHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
triggerer | ____________ _____________
triggerer | ____ |( )_____ / /________ __
triggerer | ____ /| |_ /__ / / __ / __ _ | /| / /
triggerer | ___ ___ | / _ / _ / _ / / // / |/ |/ /
triggerer | // |// // // // _//|/
triggerer | [2025-07-21 20:16:54 +0200] [49260] [INFO] Starting gunicorn 23.0.0
triggerer | [2025-07-21 20:16:54 +0200] [49260] [INFO] Listening at: http://[::]:8794 (49260)
triggerer | [2025-07-21 20:16:54 +0200] [49260] [INFO] Using worker: sync
triggerer | [2025-07-21 20:16:54 +0200] [49265] [INFO] Booting worker with pid: 49265
triggerer | [2025-07-21 20:16:54 +0200] [49268] [INFO] Booting worker with pid: 49268
dag-processor | [2025-07-21T20:16:56.856+0200] {settings.py:60} INFO - Configured default timezone UTC
dag-processor | [2025-07-21T20:16:56.965+0200] {dag_processor_job_runner.py:59} INFO - Starting the Dag Processor Job
dag-processor | [2025-07-21T20:16:56.969+0200] {manager.py:252} INFO - Processing files using up to 2 processes at a time
dag-processor | [2025-07-21T20:16:56.972+0200] {manager.py:253} INFO - Process each file at most once every 30 seconds
dag-processor | [2025-07-21T20:16:57.012+0200] {manager.py:122} INFO - DAG bundles loaded: dags-folder
dag-processor | [2025-07-21T20:16:57.072+0200] {manager.py:122} INFO - DAG bundles loaded: dags-folder
dag-processor | [2025-07-21T20:16:57.074+0200] {manager.py:263} INFO - Checking for new files in bundle dags-folder every 300 seconds
dag-processor | [2025-07-21T20:16:57.163+0200] {manager.py:534} INFO - Refreshing bundle dags-folder
dag-processor | [2025-07-21T20:16:57.211+0200] {manager.py:585} INFO - Searching for files in dags-folder at /home/yuasto/Desktop/Python_Project/Airflow/airflow_learning_20240715/dags
dag-processor | [2025-07-21T20:16:57.212+0200] {manager.py:587} INFO - Found 0 files for bundle dags-folder
dag-processor | [2025-07-21T20:16:57.546+0200] {manager.py:756} INFO -
dag-processor | ================================================================================
dag-processor | DAG File Processing Stats
dag-processor | Bundle File Path PID Current Duration # DAGs # Errors Last Duration Last Run At
dag-processor | -------- ----------- ----- ------------------ -------- ---------- --------------- -------------
dag-processor | ================================================================================
triggerer | [2025-07-21T20:16:57.619+0200] {triggerer_job_runner.py:154} INFO - Starting the triggerer
scheduler | ____________ _____________
scheduler | ____ |( )_____ / /________ __
scheduler | ____ /| |_ /__ / / __ / __ _ | /| / /
scheduler | ___ ___ | / _ / _ / _ / / // / |/ |/ /
scheduler | // |// // // // _/____/|__/
scheduler | [2025-07-21T20:16:58.338+0200] {scheduler_job_runner.py:989} INFO - Starting the scheduler
scheduler | [2025-07-21 20:16:58 +0200] [49381] [INFO] Starting gunicorn 23.0.0
scheduler | [2025-07-21T20:16:58.369+0200] {executor_loader.py:269} INFO - Loaded executor: :LocalExecutor:
scheduler | [2025-07-21 20:16:58 +0200] [49381] [INFO] Listening at: http://[::]:8793 (49381)
scheduler | [2025-07-21 20:16:58 +0200] [49381] [INFO] Using worker: sync
scheduler | [2025-07-21T20:16:58.424+0200] {scheduler_job_runner.py:2143} INFO - Adopting or resetting orphaned tasks for active dag runs
scheduler | [2025-07-21 20:16:58 +0200] [49386] [INFO] Booting worker with pid: 49386
scheduler | [2025-07-21 20:16:58 +0200] [49387] [INFO] Booting worker with pid: 49387
api-server | INFO: Waiting for child process [49250]
api-server | INFO: Child process [49250] died
standalone | Airflow is ready
standalone | Airflow Standalone is for development purposes only. Do not use this in production!
dag-processor | [2025-07-21T20:17:02.511+0200] {manager.py:531} INFO - Not time to refresh bundle dags-folder
api-server | INFO: Waiting for child process [49251]
api-server | INFO: Child process [49251] died
api-server | [2025-07-21T20:17:05.987+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.filesystem.FSHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
api-server | [2025-07-21T20:17:05.991+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.package_index.PackageIndexHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
dag-processor | [2025-07-21T20:17:07.813+0200] {manager.py:531} INFO - Not time to refresh bundle dags-folder
api-server | [2025-07-21T20:17:08.502+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.filesystem.FSHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
api-server | [2025-07-21T20:17:08.505+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.package_index.PackageIndexHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
api-server | [2025-07-21T20:17:09.820+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.filesystem.FSHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
api-server | [2025-07-21T20:17:09.824+0200] {providers_manager.py:953} INFO - The hook_class 'airflow.providers.standard.hooks.package_index.PackageIndexHook' is not fully initialized (UI widgets will be missing), because the 'flask_appbuilder' package is not installed, however it is not required for Airflow components to work
dag-processor | [2025-07-21T20:17:13.140+0200] {manager.py:531} INFO - Not time to refresh bundle dags-folder
api-server | INFO: Waiting for child process [49582]
api-server | INFO: Child process [49582] died
dag-processor | [2025-07-21T20:17:18.209+0200] {manager.py:531} INFO - Not time to refresh bundle dags-folder
api-server | INFO: Waiting for child process [49902]
api-server | INFO: Child process [49902] died
api-server | INFO: Started server process [49252]
api-server | INFO: Waiting for application startup.
api-server | INFO: Application startup complete.
dag-processor | [2025-07-21T20:17:23.504+0200] {manager.py:531} INFO - Not time to refresh bundle dags-folder
api-server | INFO: Started server process [49253]
api-server | INFO: Waiting for application startup.
api-server | INFO: Application startup complete.
api-server | INFO: Started server process [49416]
api-server | INFO: Waiting for application startup.
api-server | INFO: Application startup complete.
api-server | INFO: Waiting for child process [50072]
api-server | INFO: Child process [50072] died
dag-processor | [2025-07-21T20:17:27.917+0200] {manager.py:756} INFO -
dag-processor | ================================================================================

What you think should happen instead?

There should be no issue for running api-server

How to reproduce

1. Create a venv
2. pip install apache-airflow
3. airflow standalone

Operating System

Linux raspberrypi 6.12.25+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

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 approval.

[potiuk]

Can you please find out why the processes are dying - ? It seems you might have not enough memory for example or other reasons - but since there is no information in the logs it's impossible to help you without you doing more detailed investigation, I am afraid. You should look anywhere in your system logs in /var/logs possibly they can tell you why the processess died. ]

I will convert it into a discussion - maybe after you find more reasons we can determine whether it is airflow issue.