Gunicorn没有在AWS EC2上创建.sock文件

Question

我坚持按照本教程创建一个Django Web应用程序：https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-16-04#check-for-the-gunicorn-socket-file

我想我已经阅读了有关SO的所有相关问题：

django gunicorn sock file not created by wsgi

Gunicorn not generating sock file

https://github.com/benoitc/gunicorn/issues/1166

他们都没有帮助。

我完全按照描述执行每个步骤，但仍未创建myapp.sock文件。

主项目目录是/home/ubuntu/puchalatravel它的内容：

ubuntu@ip-172-31-35-104:~/puchalatravel$ ls -l
total 60
-rw-r--r-- 1 ubuntu ubuntu   40960 Sep  4 09:37 db.sqlite3
-rwxrwxr-x 1 ubuntu ubuntu     545 Sep  4 07:42 manage.py
drwxrwxr-x 3 ubuntu www-data  4096 Sep  4 09:32 puchalatravel
drwxrwxr-x 4 ubuntu ubuntu    4096 Sep  4 07:41 puchalatravelenv
drwxrwxr-x 3 ubuntu ubuntu    4096 Sep  4 09:34 static

访问该文件夹：

ubuntu@ip-172-31-35-104:~$ ls -l
total 1616
drwxrwxr-x 4 ubuntu ubuntu      4096 Aug 30 07:25 eb-virt
-rw-rw-r-- 1 ubuntu ubuntu   1642522 Aug 30 07:11 get-pip.py
drwxrwxr-x 6 ubuntu www-data    4096 Sep  4 09:37 puchalatravel

/etc/systemd/system/gunicorn.service的内容

[Unit]
Description=gunicorn daemon
After=network.target

[Service]
User=ubuntu
Group=www-data
WorkingDirectory=/home/ubuntu/puchalatravel
ExecStart=/home/ubuntu/puchalatravel/puchalatravelenv/bin/gunicorn --access-logfile - --workers 3 --bind unix:/home/puchalatravel/puchalatravel.sock puchalatravel.wsgi:application

[Install]
WantedBy=multi-user.target

/etc/nginx/sites-available/puchalatravel的内容

server {                                                                                                                                                                                                                                 sserver {
listen 8000;
    server_name ec2-18-188-249-6.us-east-2.compute.amazonaws.com;

    location = /favicon.ico { access_log off; log_not_found off; }
    location /static/ {
        root /home/ubuntu/puchalatravel;
    }

    location / {
        include proxy_params;
        proxy_pass http://unix:/home/ubuntu/puchalatravel/puchalatravel.sock;
    }
}

我跑了

pkill gunicorn
sudo systemctl daemon-reload
sudo systemctl start gunicorn
sudo systemctl enable gunicorn
sudo systemctl restart nginx

好几次，没有任何影响。

sudo systemctl status gunicorn的输出

● gunicorn.service - gunicorn daemon
Loaded: loaded (/etc/systemd/system/gunicorn.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-09-04 09:56:51 UTC; 18min ago
Main PID: 19906 (code=exited, status=1/FAILURE)

Sep 04 09:56:46 ip-172-31-35-104 gunicorn[19906]: [2018-09-04 09:56:46 +0000] [19906] [INFO] Starting gunicorn 19.9.0
Sep 04 09:56:46 ip-172-31-35-104 gunicorn[19906]: [2018-09-04 09:56:46 +0000] [19906] [ERROR] Retrying in 1 second.
Sep 04 09:56:47 ip-172-31-35-104 gunicorn[19906]: [2018-09-04 09:56:47 +0000] [19906] [ERROR] Retrying in 1 second.
Sep 04 09:56:48 ip-172-31-35-104 gunicorn[19906]: [2018-09-04 09:56:48 +0000] [19906] [ERROR] Retrying in 1 second.
Sep 04 09:56:49 ip-172-31-35-104 gunicorn[19906]: [2018-09-04 09:56:49 +0000] [19906] [ERROR] Retrying in 1 second.
Sep 04 09:56:50 ip-172-31-35-104 gunicorn[19906]: [2018-09-04 09:56:50 +0000] [19906] [ERROR] Retrying in 1 second.
Sep 04 09:56:51 ip-172-31-35-104 gunicorn[19906]: [2018-09-04 09:56:51 +0000] [19906] [ERROR] Can't connect to /home/puchalatravel/puchalatravel.sock
Sep 04 09:56:51 ip-172-31-35-104 systemd[1]: gunicorn.service: Main process exited, code=exited, status=1/FAILURE
Sep 04 09:56:51 ip-172-31-35-104 systemd[1]: gunicorn.service: Unit entered failed state.
Sep 04 09:56:51 ip-172-31-35-104 systemd[1]: gunicorn.service: Failed with result 'exit-code'.

这可能与AWS EC2设置有关吗？ Gunicorn可以直接将页面提供给端口8000，但不能通过套接字提供，因为它不是创建的。

Answer 1

你的gunicorn.service文件配置gunicorn在“/home/puchalatravel/puchalatravel.sock”而不是“/home/ubuntu/puchalatravel/puchalatravel.sock”中创建文件。