Supervisorctl 说 gunicorn 进程处于 RUNNING 状态,我认为它成功了。但还是有些不对劲。资源仅通过 IP 可用
Nginx 配置:
upstream hello_app_server {
server unix:/var/www/aqe-backend/gunicorn.sock fail_timeout=0;
}
server {
listen 80;
server_name 188.166.200.51;
client_max_body_size 4G;
access_log /var/www/aqe-backend/logs/nginx-access.log;
error_log /var/www/aqe-backend/logs/nginx-error.log;
location /static/ {
alias /var/www/aqe-backend/static/;
}
location /media/ {
alias /var/www/aqe-backend/media/;
}
location / {
# an HTTP header important enough to have its own Wikipedia entry:
# http://en.wikipedia.org/wiki/X-Forwarded-For
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
# enable this if and only if you use HTTPS, this helps Rack
# set the proper protocol for doing redirects:
# proxy_set_header X-Forwarded-Proto https;
# pass the Host: header from the client right along so redirects
# can be set properly within the Rack application
proxy_set_header Host $http_host;
# we don't want nginx trying to do something clever with
# redirects, we set the Host: header above already.
proxy_redirect off;
# set "proxy_buffering off" *only* for Rainbows! when doing
# Comet/long-poll stuff. It's also safe to set if you're
# using only serving fast clients with Unicorn + nginx.
# Otherwise you _want_ nginx to buffer responses to slow
# clients, really.
# proxy_buffering off;
# Try to serve static files from nginx, no point in making an
# *application* server like Unicorn/Rainbows! serve static files.
if (!-f $request_filename) {
proxy_pass http://188.166.200.51;
break;
}
}
error_page 500 502 503 504 /500.html;
location = /500.html {
root /var/www/aqe-backend/static/;
}
}
gunicorn脚本:
#!/bin/bash
NAME="aqe" # Name of the application
DJANGODIR=/var/www/aqe-backend/ # Django project directory
SOCKFILE=/var/www/aqe-backend/gunicorn.sock # we will communicte using this unix socket
USER=www-data # the user to run as
GROUP=www-data # the group to run as
NUM_WORKERS=3 # how many worker processes should Gunicorn spawn
DJANGO_SETTINGS_MODULE=project.settings_prod # which settings file should Django use
DJANGO_WSGI_MODULE=project.wsgi # WSGI module name
echo "Starting $NAME as `whoami`"
# Activate the virtual environment
cd $DJANGODIR
source env/bin/activate
export DJANGO_SETTINGS_MODULE=$DJANGO_SETTINGS_MODULE
export PYTHONPATH=$DJANGODIR:$PYTHONPATH
# Create the run directory if it doesn't exist
RUNDIR=$(dirname $SOCKFILE)
test -d $RUNDIR || mkdir -p $RUNDIR
# Start your Django Unicorn
# Programs meant to be run under supervisor should not daemonize themselves (do not use --daemon)
exec gunicorn ${DJANGO_WSGI_MODULE}:application \
--name $NAME \
--workers $NUM_WORKERS \
--user=$USER --group=$GROUP \
--bind=unix:$SOCKFILE \
--log-level=debug \
--log-file=-
答案1
尝试检查您的gunicorn.sock
文件是否确实存在。可能是它所在的文件夹没有正确的权限,或者根本不存在(如果您只是按照教程操作,它可能就不存在)。
如果它已经存在,请将其删除,然后使用 (重新)创建它mkdir /var/www/aqe-backend
。
看https://stackoverflow.com/questions/28689445/nginx-django-and-gunicorn-gunicorn-sock-file-is-missing了解更多信息。
另外,检查日志(例如)也tail /var/log/long.err.log
可以提供帮助。