质问关联问题合理性：Django1.11从cron启动连PostgreSQL异常

Hey there, let's work through this problem you're hitting. I've dealt with this exact scenario a handful of times, and it almost always comes down to cron's stripped-down environment compared to your regular user shell. Let's break down the most likely fixes step by step:

1. Fix Cron's Limited Environment Variables #

When you run manage.py runserver from your command line, you're using your full user environment—including your custom PATH, Python virtual environment variables, and PostgreSQL-related paths. Cron, though, uses a super minimal environment by default, which means it might not find your Python executable, Django modules, or PostgreSQL binaries.

• Quick fix: Specify the absolute path to your Python interpreter instead of just python, and load your user's shell environment first. For example:

  @reboot source ~/.bashrc && /usr/local/bin/python3 /path/to/your/project/manage.py runserver 0.0.0.0:8000
  

  (Replace /usr/local/bin/python3 with the actual path to your Python executable—you can find this with which python in your regular shell.)

2. Set the Correct Working Directory #

Cron runs commands from a default working directory (usually /root or your user's home folder), but Django's manage.py needs to be executed from your project's root directory to load settings and dependencies properly.

• Adjust your cron command to cd first:

  @reboot cd /path/to/your/django/project && source ~/.bashrc && /usr/local/bin/python3 manage.py runserver 0.0.0.0:8000
  

3. Verify PostgreSQL Connection Configuration #

Even though you've set up IPv4 local access in pg_hba.conf, cron's environment might be causing Django to use a Unix socket instead of IPv4, or it might not have access to the socket path.

• Check your Django settings.py database config:
  If you're using host: 'localhost', try switching to the Unix socket path (common on CentOS: /var/run/postgresql):

  DATABASES = {
      'default': {
          'ENGINE': 'django.db.backends.postgresql_psycopg2',
          'NAME': 'your_db_name',
          'USER': 'your_db_user',
          'PASSWORD': 'your_db_pass',
          'HOST': '/var/run/postgresql',  # Use socket path instead of localhost
          'PORT': '',
      }
  }
  

• Double-check pg_hba.conf for Unix socket access:
  Make sure there's a line allowing local socket connections, like:

  local   all             all                                     md5
  

  (After editing pg_hba.conf, restart PostgreSQL with systemctl restart postgresql.)

4. Check Cron Logs for Specific Errors #

CentOS logs cron activity to /var/log/cron—this is your best bet for finding exact error messages (like missing modules, permission issues, or database connection timeouts).

• View recent cron logs:

  tail -n 20 /var/log/cron
  

  Look for lines related to your runserver command—they'll tell you exactly what's failing.

A Quick Note on Runserver #

Just a heads-up: Django's runserver is intended for development only, not production. For a long-term setup, you should use a proper WSGI server like Gunicorn or uWSGI behind Nginx. But since you're working with a test setup, the fixes above should get you sorted.

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