Django Elastic Beanstalk中Cron任务发送邮件失败求助

Let's break down the possible issues with your setup and walk through fixes step by step:

1. Cron Environment Variables Are Missing #

Cron runs in a minimal environment by default—it doesn't inherit all the environment variables your Django app relies on, like DJANGO_SETTINGS_MODULE. Without this, your manage.py command won't know how to load your app's core settings (including critical email configurations).

2. source Isn't Compatible with Cron's Default Shell #

Cron uses /bin/sh by default, but source is a Bash-specific command. This can cause your virtual environment activation script to fail silently, leaving your Python command running in the system's default environment instead of your app's venv.

3. Incomplete Logging #

Your current cron command only redirects standard output to cronjobs.log, but standard error (error messages) aren't captured. This makes it impossible to see why the command is failing if something goes wrong.

4. Potential Path or Configuration Gaps #

We also need to verify your Django email settings and ensure the cron job file is being installed correctly during deployment.

Fixes to Apply #

Update Your cronjobs.cron File

Replace your current cron line with this:

* * * * * root /bin/bash -c 'source /opt/python/run/venv/bin/activate && export DJANGO_SETTINGS_MODULE=github.settings && cd /opt/python/current/github && python manage.py cronjb >> /var/log/cronjobs.log 2>&1'

Here's what this does:

• Uses /bin/bash -c to run the command in a Bash shell (so source works as expected)
• Explicitly sets DJANGO_SETTINGS_MODULE so Django knows which settings file to load
• Changes to the project directory to avoid path-related errors with manage.py
• Redirects both stdout and stderr to your log file (so you can see all errors and output)

Check Cron and Job Logs

After redeploying, check these logs to diagnose issues:

• Cron system log: Run cat /var/log/cron to confirm the cron job is being triggered. Look for lines like (root) CMD (/bin/bash -c 'source ...')—if you don't see this, the cron file wasn't installed correctly during deployment.
• Job log: Run cat /var/log/cronjobs.log to see any errors from your cronjb command (e.g., Django settings load failures, email authentication errors).

Verify Django Email Settings

Make sure your settings.py has valid email configuration (critical for send_mail to work). For Gmail, it should look something like this:

EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
EMAIL_HOST = 'smtp.gmail.com'
EMAIL_PORT = 587
EMAIL_USE_TLS = True
EMAIL_HOST_USER = 'abc@gmail.com'
# For Gmail with 2FA enabled, use an App Password instead of your regular password
EMAIL_HOST_PASSWORD = 'your-app-specific-password'

If you're using Gmail, ensure you've allowed less secure apps (or better, use an App Password if 2FA is enabled) to avoid authentication blocks.

Confirm Cron File Installation

Check if your cron file was copied correctly during deployment:
Run cat /etc/cron.d/djangocrons on your EC2 instance. If the content doesn't match your cronjobs.cron file, double-check your container_commands path—ensure .ebextensions/cronjobs.cron exists in your project root and is being uploaded to Elastic Beanstalk with your deployment.

Once you apply these changes, redeploy your app and wait a minute for the cron job to trigger. Check the logs again, and you should see either success messages or clear errors to debug further.

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