AWS Elastic Beanstalk环境更新后Nginx无法自动重启问题排查

我在AWS Elastic Beanstalk上部署了PHP 8.1+Nginx的网站，初始运行正常，但AWS更新Elastic Beanstalk环境配置后，网站因Nginx故障无法访问，页面显示Nginx默认欢迎页。必须通过SSH连接到EC2实例，执行sudo service nginx restart命令手动重启Nginx才能恢复服务。

自定义Nginx配置文件.platform/nginx/nginx.conf内容：

#Elastic Beanstalk Nginx Configuration File

user                    nginx;
error_log               /var/log/nginx/error.log warn;
pid                     /var/run/nginx.pid;
worker_processes        auto;
worker_rlimit_nofile    31486;

events {
    worker_connections  1024;
}

http {
    server_tokens off;
    
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "&request" '
                      '$status $body_bytes_sent "&http_referer" '
                      '&http_user_agent" "&http_x_forwarded_for"';

    include       conf.d/*.conf;

    map $http_upgrade $connection_upgrade {
        default     "upgrade";
    }

    server {

        location ^~ /pv/ {
           #  allow 192.168.1.1/24;
           deny all;
           return 404;
        }
     
        listen        80 default_server;
        access_log    /var/log/nginx/access.log main;

        client_header_timeout 60;
        client_body_timeout   60;
        client_max_body_size  50M;
        keepalive_timeout     60;
        gzip                  off;
        gzip_comp_level       4;
        gzip_types text/plain text/css application/json application/javascript application/x-javascript text/xml application/xml application/xml+rss text/javascript;

        # Include the Elastic Beanstalk generated locations
        include conf.d/elasticbeanstalk/*.conf;

    server_name mywebsitename.com;
    index index.php;
    error_page 404 /index.php;

    location /app/upload_video.php {
         client_max_body_size 2084M;
    }
    
    if ($http_user_agent ~ "Snabcd"){
        rewrite ^/?cup/product/([^/]+)/([^/]+)/([^/]+)/location/([^/]+)/([^/]+)/([^/]+)(?:/(menu-selected)/([^/]+)|)/?$ https://$host/indexapp.php?c1=$1&c2=$2&c3=$3&r2=$4&r3=$5&r4=$6&f_urlseo=1&f_idxt=cpn&$7=$8 last;
        rewrite ^/?cup/product/([^/]+)/([^/]+)/([^/]+)(?:/(menu-selected)/([^/]+)|)/?$ https://$host/indexapp.php?c1=$1&c2=$2&c3=$3&f_urlseo=1&f_idxt=cpn&$4=$5 permanent ;
    }

    if ($http_user_agent !~ "Snabcd"){
        rewrite ^/?cup/product/([^/]+)/([^/]+)/([^/]+)/location/([^/]+)/([^/]+)/([^/]+)(?:/(menu-selected)/([^/]+)|)/?$ https://$host/indexpc.php?c1=$1&c2=$2&c3=$3&r2=$4&r3=$5&r4=$6&f_urlseo=1&f_idxt=cpn&$7=$8 last;
        rewrite ^/?cup/product/([^/]+)/([^/]+)/([^/]+)(?:/(menu-selected)/([^/]+)|)/?$ https://$host/indexpc.php?c1=$1&c2=$2&c3=$3&f_urlseo=1&f_idxt=cpn&$4=$5 
    }

    rewrite ^/?ld/([^/]+).*/?$      https://$host/ad_detail.php?ldasid=$1 permanent; 
  
    rewrite ^/?job/sales/location/([^/]+)/([^/]+)/([^/]+).*/?$   https://$host/users/jobs/job_sales.php?r2=$1&r3=$2&r4=$3 permanent; 

    
  https://$host/ect/gamesrc/javascript/tw/index_all_games.php [L,R=301]
    if ($host ~ "192.168.|172.20.|10.0."){ 
        rewrite ^/?games/?$ https://$host/ect/gamesrc/javascript/tw/index_all_games.php permanent;
    } 
    rewrite ^/?games/?$ https://$host/gamesrc/javascript/tw/index_all_games.php permanent;

  }
}

.ebextensions目录下的EBS配置文件：

packages:
  yum:
    sysstat: []
Resources:
  sslSecurityGroupIngress: 
    Type: AWS::EC2::SecurityGroupIngress
    Properties:
      GroupId: {Ref : AWSEBSecurityGroup}
      IpProtocol: tcp
      ToPort: 443
      FromPort: 443
      CidrIp: 0.0.0.0/0
container_commands:
  01nginxrestart:
    command: "sudo service nginx restart"

1. Nginx配置文件存在语法错误 #

你的自定义nginx.conf有两处致命语法问题：

• 不完整的rewrite指令：在if ($http_user_agent !~ "Snabcd")块的第二条rewrite语句末尾缺少分号，导致Nginx解析配置失败：

  rewrite ^/?cup/product/([^/]+)/([^/]+)/([^/]+)(?:/(menu-selected)/([^/]+)|)/?$ https://$host/indexpc.php?c1=$1&c2=$2&c3=$3&f_urlseo=1&f_idxt=cpn&$4=$5 
  

• 无效配置行：存在一条既不是指令也不是注释的无效代码行，直接破坏了配置结构：

  https://$host/ect/gamesrc/javascript/tw/index_all_games.php [L,R=301]
  

当Elastic Beanstalk更新环境配置时，会尝试加载自定义Nginx配置，但因为语法错误，Nginx启动失败。此时系统会自动 fallback到默认的Nginx欢迎页配置，保证基础服务可用。而手动重启Nginx时，可能因为临时缓存或系统容错机制，让Nginx绕过部分错误加载配置，从而恢复服务。

2. .ebextensions中的重启命令时机不对 #

container_commands仅在应用部署阶段执行，而Elastic Beanstalk的环境配置更新（比如修改环境变量、实例类型等）不会触发完整的部署流程，因此该重启命令不会被执行，无法自动修复Nginx的异常状态。另外，即使在部署阶段执行，如果配置本身有语法错误，sudo service nginx restart也会执行失败，无法生效。

3. Elastic Beanstalk的配置验证逻辑 #

Elastic Beanstalk在更新环境时会严格验证Nginx配置的语法正确性，一旦发现错误就会放弃加载自定义配置，转而使用默认配置。而手动重启时，Nginx的错误处理逻辑可能相对宽松，因此能恢复服务。

1. 修复Nginx配置语法错误 #

• 补全if ($http_user_agent !~ "Snabcd")块中第二条rewrite语句的分号：

  rewrite ^/?cup/product/([^/]+)/([^/]+)/([^/]+)(?:/(menu-selected)/([^/]+)|)/?$ https://$host/indexpc.php?c1=$1&c2=$2&c3=$3&f_urlseo=1&f_idxt=cpn&$4=$5 permanent;
  

• 删除那条无效的配置行，或者将其修改为合法的rewrite指令（如果是误写的跳转规则）：

  # 示例：如果是针对某个路径的跳转，补充完整指令
  rewrite ^/?invalid-path/?$ https://$host/ect/gamesrc/javascript/tw/index_all_games.php [L,R=301];
  

修复后，在本地用nginx -t验证配置语法：

nginx -t -c /path/to/your/nginx.conf

2. 调整.ebextensions的重启逻辑 #

将container_commands替换为commands，并添加services指令确保Nginx始终运行：

packages:
  yum:
    sysstat: []
Resources:
  sslSecurityGroupIngress: 
    Type: AWS::EC2::SecurityGroupIngress
    Properties:
      GroupId: {Ref : AWSEBSecurityGroup}
      IpProtocol: tcp
      ToPort: 443
      FromPort: 443
      CidrIp: 0.0.0.0/0
commands:
  01nginx_restart:
    command: "sudo service nginx restart"
    ignoreErrors: true # 避免因重启失败中断部署，前提是配置已正确
services:
  sysvinit:
    nginx:
      enabled: true
      ensureRunning: true

services指令会监控Nginx状态，配置更新后自动重启服务，同时确保Nginx始终处于运行状态。

3. 排查Nginx日志定位问题 #

每次环境更新失败后，登录EC2实例查看/var/log/nginx/error.log，日志中会明确显示配置语法错误的位置，帮助快速定位问题。

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