使用Supervisor和Gunicorn部署Django项目时遇FATAL退出过快错误

Hey there! Let's work through this issue you're facing with your first Django deployment using Gunicorn and Supervisor. That "FATAL Exited too quickly" error usually points to a problem with how Gunicorn is configured or how Supervisor is trying to launch it—let's break down the steps to diagnose and fix this:

1. First, Check the Supervisor Process Logs #

The error message mentions the "process log may have details"—this is your best starting point. Supervisor logs each program's output to specific files, usually located at /var/log/supervisor/. To see what's causing the crash:

# Check the error log for your smartsurvey program
cat /var/log/supervisor/smartsurvey-stderr.log

# Or watch it in real-time to catch the error as it happens
tail -f /var/log/supervisor/smartsurvey-stderr.log

This log will often tell you exactly what's wrong—like a missing dependency, incorrect path, or permission issue.

2. Verify Your Gunicorn Setup #

Since you didn't share your Gunicorn config, let's confirm the basics you need to get right:

• Use your virtual environment: Always call Gunicorn from your Django project's virtual environment to avoid missing packages. For example, if your venv is at /home/youruser/venv/, your Gunicorn command should start with /home/youruser/venv/bin/gunicorn instead of just gunicorn.
• Correct WSGI path: Make sure you're pointing to your Django project's WSGI file. If your project is named smartsurvey, the path should be smartsurvey.wsgi:application (assuming your project structure follows Django's default).
• Test Gunicorn manually: Before relying on Supervisor, launch Gunicorn directly to confirm it works:

  cd /path/to/your/django/project
  source venv/bin/activate  # Activate your virtual environment
  gunicorn smartsurvey.wsgi:application --bind 127.0.0.1:8000
  

  If this fails, fix the error here first (e.g., install missing packages, correct the WSGI path) before moving back to Supervisor.

3. Audit Your Supervisor [program:smartsurvey] Config #

Double-check these critical settings in your Supervisor config file (usually at /etc/supervisor/conf.d/smartsurvey.conf):

• command: Must be the full, working Gunicorn command (including the virtual environment path).
• directory: Set this to your Django project's root directory—this ensures Gunicorn can find your settings.py and other project files.
• user: Specify a user that has read access to your project files and write access to the log directory (e.g., your regular user or www-data).
• Log paths: Ensure stdout_logfile and stderr_logfile point to directories that exist and the specified user can write to them.

Here's an example of a valid config to reference:

[program:smartsurvey]
command=/home/youruser/venv/bin/gunicorn --workers 3 smartsurvey.wsgi:application --bind 127.0.0.1:8000
directory=/home/youruser/smartsurvey_project
user=youruser
autostart=true
autorestart=true
stdout_logfile=/var/log/supervisor/smartsurvey_stdout.log
stderr_logfile=/var/log/supervisor/smartsurvey_stderr.log

4. Check Permissions #

Permissions are a common culprit here:

• Make sure the user specified in your Supervisor config owns (or has read access to) your Django project directory and virtual environment:

  sudo chown -R youruser:youruser /path/to/your/django/project
  sudo chown -R youruser:youruser /path/to/your/venv
  

• Ensure the log directory /var/log/supervisor/ is writable by the same user.

After making any changes to your Supervisor config, run these commands to apply them:

sudo supervisorctl reread
sudo supervisorctl update
sudo supervisorctl restart smartsurvey

Start with checking the error log—it will almost certainly give you the specific issue to fix. Once you resolve that, your Supervisor-managed Gunicorn process should stay running!

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