Nginx 不会重启。 . . nginx.service 的作业失败，因为控制进程以错误代码退出答案

【问题标题】：Nginx won't restart . . . Job for nginx.service failed because the control process exited with error codeNginx 不会重启。 . . nginx.service 的作业失败，因为控制进程以错误代码退出
【发布时间】：2018-08-10 09:01:00
【问题描述】：

我正在关注有关设置 Nginx 的 youtube 视频，我正在重新启动，它会在我获得部分位置时给出我需要编辑我完全遵循的服务器块文件（启用站点/默认）他们在视频中做了什么，但在保存并尝试重新启动时：

sudo service nginx restart

我收到了这个错误： nginx.service 的作业失败，因为控制进程以错误代码退出。详见“systemctl status nginx.service”和“journalctl -xe”。

所以我跑了

systemctl status nginx.service

它给出了输出：

Active: failed (Result: exit-code) since Fri 2018-03-02 01:36:33 EST; 10min ago

我在 Ubuntu 16.04 Linux VPS 上运行所有这些

下面是 /etc/nginx/sites-enabled/default 文件的内容：

  ##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
    listen 80 default_server;
    listen [::]:80 default_server;

    # SSL configuration
    #
    # listen 443 ssl default_server;
    # listen [::]:443 ssl default_server;
    #
    # Note: You should disable gzip for SSL traffic.
    # See: https://bugs.debian.org/773332
    #
    # Read up on ssl_ciphers to ensure a secure configuration.
    # See: https://bugs.debian.org/765782
    #
    # Self signed certs generated by the ssl-cert package
    # Don't use them in a production server!
    #
    # include snippets/snakeoil.conf;

    root /var/www/html;

    # Add index.php to the list if you are using PHP
    index index.php index.html index.htm index.nginx-debian.html;

    server_name x.x.x.x;

    location / {
        # First attempt to serve request as file, then
        # as directory, then fall back to displaying a 404.
        try_files $uri $uri/ =404;
    }

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #


/* additions i made*/


    error_page 404 /404.html;
    error_page 500 502 503 504 /50x.html;
    location = /50x.html {
    root /usr/share/nginx/html;
    }
    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        try_files $uri = 404;
        fastcgi_split_path_info ^(.*\.php)(/.*)$;

        # With php7.0-cgi alone:
    #   fastcgi_pass 127.0.0.1:9000;
    #   # With php7.0-fpm:
        fastcgi_pass unix:/run/php/php7.0-fpm.sock;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root $fastcgi_script_name;
        include fastcgi_params;
    }

/*end of additions*/



    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    #location ~ /\.ht {
    #   deny all;
    #}
}


# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
#   listen 80;
#   listen [::]:80;
#
#   server_name example.com;
#
#   root /var/www/example.com;
#   index index.html;
#
#   location / {
#       try_files $uri $uri/ =404;
#   }
#}

编辑：他们在视频中使用了 php5.6，但如果这有帮助，我使用的是 PHP 7.0

【问题讨论】：

/* ... */ 不是有效的注释语法。它真的在配置文件中还是你试图注释你的问题？你的配置文件有很多语法错误，用nginx -t测试一下。
是的，我只是用它来注释。

标签： nginx

【解决方案1】：

出了点问题

通过编辑 /etc/nginx/nginx.conf 将错误日志记录设置为调试：
找到与error_log 的行，验证日志文件位置并将级别更改为调试：
error_log logs/error.log debug;

再次尝试重新启动并检查日志文件以获取更多详细信息。

【讨论】：

所以我检查了 nginx.conf，这是我在error_log、# Logging Settings ## access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; 上找到的内容，我不知道如何将级别更改为调试，请解释一下。谢谢
非常感谢，通过跟踪 nginx.conf 指向的位置内的日志（在本例中为 /var/log/nginx/error.log），我能够解决问题。这可以关闭

【解决方案2】：

似乎另一台服务器正在端口 443/80 上运行。所以检查端口

netstat -tpln

很可能应该是apache。

sudo killall apache2

【讨论】：