Question

我使用本教程部署了一个Django网站

https://jee-appy.blogspot.com/2017/01/deply-django-with-nginx.html

该网站可从互联网访问，www.simplesol.com

当我尝试发出POST请求时，它失败了，我收到502错误。

在我的nginx-error.log文件中，我收到此错误消息

function fetchMovies(query) {
  const requestId = fetchMovies.requestId(query)
//                  ^^^^^^^^^^^
  return dispatch => {
    dispatch(sendingRequest(requestId))
    return ajax.get(`/movies/search?q=${query}`)
    .then(res => {
      dispatch(receievedResponse(requestId))
      return dispatch(addMovies(res.data.movies))
    })
  }
}
fetchMovies.requestId = (query) => `fetchMoviesLoading-${query}`;

这些是我/etc/nginx/sites-available/simplesol.conf的内容

*344 upstream prematurely closed connection while reading response header 
from upstream, client: InternalIP, server: ExternalIP, request: "POST 
/audit/ HTTP/1.1", upstream: 
"http://unix:/home/webadmin/virtual_env/run/gunicorn.sock:/audit/", host: 
"www.simplesol.com", referrer: "http://www.simplesol.com/audit/"

/etc/nginx/sites-available/simplesol.conf

command = /home/webadmin/gunicorn_start.bash                   ;  Command to start app
user = webadmin                                                ; User to run as
stdout_logfile = /home/webadmin/logs/gunicorn_supervisor.log   ; Where to write log messages
redirect_stderr = true                                       ; Save stderr in the same log
environment=LANG=en_US.UTF-8,LC_ALL=en_US.UTF-8              ; Set UTF-8 as default encoding

gunicorn_start.bash

upstream 192.168.8.5 {

server unix:/home/webadmin/adrienne/run/gunicorn.sock fail_timeout=0;
}

server {

    listen   80;
server_name 192.168.8.5 ;

client_max_body_size 4G;
access_log /home/webadmin/logs/nginx-access.log;
error_log /home/webadmin/logs/nginx-error.log;

location /static/ {
    autoindex on;
    alias /home/webadmin/static/;
}

location /media/ {
    alias   /home/webadmin/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://192.168.8.5;
        break;
    }
}

# Error pages
error_page 500 502 503 504 /500.html;
location = /500.html {
    root /home/webadmin/SimpleSolWebsite/static/;
}
   }

我的配置文件有问题吗？我不知道我哪里出错了，我在谷歌上没有取得任何成功。提前感谢您对我的任何见解！

gunicorn_supervisor_log

#!/bin/bash

NAME="django_app"                                   
DJANGODIR=/home/ubuntu/sample_project               
SOCKFILE=/home/ubuntu/django_env/run/gunicorn.sock  
USER=ubuntu                                         
GROUP=ubuntu                                        
NUM_WORKERS=3                                       
DJANGO_SETTINGS_MODULE=sample_project.settings              
DJANGO_WSGI_MODULE=sample_project.wsgi              
echo "Starting $NAME as `whoami`"



cd $DJANGODIR
source /home/ubuntu/django_env/bin/activate
export DJANGO_SETTINGS_MODULE=$DJANGO_SETTINGS_MODULE
 export PYTHONPATH=$DJANGODIR:$PYTHONPATH



RUNDIR=$(dirname $SOCKFILE)
test -d $RUNDIR || mkdir -p $RUNDIR



exec gunicorn ${DJANGO_WSGI_MODULE}:application \
  --name $NAME \
  --workers $NUM_WORKERS \
  --user=$USER --group=$GROUP \
  --bind=unix:$SOCKFILE \
  --log-level=debug \
  --log-file=-

联系人应用

models.py

[2018-03-14 22:23:22 +0000] [25559] [DEBUG] GET /contact/
[2018-03-14 22:23:51 +0000] [10934] [DEBUG] POST /contact/
[2018-03-14 15:24:21 -0700] [24869] [CRITICAL] WORKER TIMEOUT (pid:10934)
[2018-03-14 22:24:21 +0000] [10934] [INFO] Worker exiting (pid: 10934)
[2018-03-14 15:24:21 -0700] [23688] [INFO] Booting worker with pid: 23688

forms.py

from django.db import models


class Contacts(models.Model):
    contact_name = models.CharField(max_length=256, default='contact name')
    phone_number = models.CharField(max_length=15)
    phone_ext = models.CharField(max_length=10, default='ext', blank="True")
    email = models.EmailField()
    comments = models.TextField()
    company_name = models.CharField(max_length=250, default='company name')

views.py

from django import forms
from contacts.models import Contacts
from django.forms import ModelForm
from django.db import models

class ContactForm(forms.ModelForm):
    class Meta:
        model = Contacts
        fields = "__all__"

Answer 1

Gunicorn的默认超时为30 seconds

工人沉默超过这么多秒就被杀死了重新启动。

如果某个工作人员被杀死/重新启动，那么与nginx的连接将被终止，而nginx将产生您遇到的错误

* 344上游过早关闭连接，同时从上游读取响应头

您在gunicorn的日志中看到的错误证实了这一点：

[2018-03-14 22:23:51 +0000] [10934] [DEBUG] POST /contact/
[2018-03-14 15:24:21 -0700] [24869] [CRITICAL] WORKER TIMEOUT (pid:10934)

因此要么修改代码以在〜30秒内完成所有操作（更好），要么调整超时（更糟糕）

＆＃34;上游过早关闭连接，同时从上游读取响应头＃34; Django，Ubuntu，Nginx，Gunicorn

1 个答案: