Airflow无法启动：调用setugid()不允许问题求助（新手用户）

Hey there! Let's work through this Airflow issue together—since it ran perfectly for days before, this is almost certainly a fixable permission or leftover process problem, even for someone new to Airflow.

First, let's break down that error: Airflow doesn't run: The application with bundle id (null) in running setugid() which is not allowed — this means Airflow is trying to use a Linux permission-related call (setugid()) that's being blocked, usually because of mismatched file permissions or issues with the user running Airflow.

Here are the steps to fix this, ordered from easiest to more targeted:

1. Kill all leftover Airflow processes first #

Since you mentioned multiple PIDs starting repeatedly, old stuck processes are probably interfering. Run these commands in your terminal:

• Kill all Airflow-related processes: pkill -f airflow
• Double-check for any stragglers: ps aux | grep airflow — if you see any remaining processes, kill them manually with kill <PID> (replace <PID> with the process number you see)
• Delete any leftover PID files in your Airflow home directory (default is ~/airflow): rm ~/airflow/airflow-webserver.pid ~/airflow/airflow-scheduler.pid (ignore "file not found" errors here, it just means those files didn't exist)

2. Fix Airflow directory permissions #

This is the most common cause for sudden permission errors. First, confirm which user you're running Airflow as with whoami. Then:

• Recursively set ownership of your Airflow home directory to your user: chown -R $(whoami):$(whoami) ~/airflow
• Make sure key subdirectories have correct permissions:
  • chmod 755 ~/airflow
  • chmod 755 ~/airflow/logs ~/airflow/dags ~/airflow/plugins
• Check your Airflow config file permissions: chmod 644 ~/airflow/airflow.cfg (this ensures your user can read it, but others can't modify it)

3. Test starting the webserver in single-worker mode #

Sometimes multi-worker mode can trigger permission issues that don't show up in single-worker mode. Try starting the webserver with just one worker to isolate the problem:

airflow webserver --workers 1 --port 8080

If this works, the issue might be related to resource limits or multi-process permission inheritance. You can then try increasing workers gradually, or check if your system has limits on the number of processes a user can run.

4. Check system-level security restrictions #

If the above steps don't work, the error might be from system security tools blocking setugid() calls:

• SELinux (RHEL/CentOS/Fedora): Temporarily disable it to test with sudo setenforce 0, then try starting Airflow again. If it works, you'll need to add a SELinux policy to allow Airflow's operations (you can search for Airflow-specific SELinux rules for your distro).
• AppArmor (Ubuntu/Debian): Check if there's an AppArmor profile restricting Airflow with sudo aa-status. If you see a profile related to Airflow, you can temporarily disable it with sudo aa-disable <profile-name> to test.

5. Verify your Airflow config isn't misconfigured #

Double-check your airflow.cfg file (in ~/airflow) for any recent changes:

• Ensure core.airflow_home is set to your actual Airflow directory (should be ~/airflow by default)
• Don't set webserver.user to a different user unless you know exactly what you're doing—leave it as the default if you haven't modified it before

Once you've tried these steps, restart Airflow normally with airflow webserver and airflow scheduler (or airflow standalone if you're using the standalone mode) and see if it starts up without issues.

内容的提问来源于stack exchange，提问作者Sam