nginx日志的一点理解

1、access.log什么时候打印?

经过测试,观察到access.log是在后端返回响应结果之后才打印的,不过也很好理解,nginx要等后端返回才知道是否处理成功。

2、nginx什么时候出现upstream timed out?

nginx超时时间<接口响应时间,就会出现upstream timed out.

3、nginx什么时候出现no live upstreams?

测试过程日下

后端接口:

java 复制代码
@RestController
public class BasicController {

    private static final Logger logger = LoggerFactory.getLogger(BasicController.class);
    @GetMapping("/xxx/test")
    public String hello() throws InterruptedException {
        logger.info("xxxtest");
        Thread.sleep(50000);
        return "success";
    }
}

开启了两个端口8080和8081,启动项目

nginx配置如下:

bash 复制代码
worker_processes  1;

events {
    worker_connections  1024;
}

http {
    include       mime.types;
    default_type  application/json;

    sendfile        on;
    
    keepalive_timeout  65;

    server {
        listen       80;
        server_name  localhost;
        # 指定前端项目所在的位置
       
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }


        location / {  
            # 设置超时时间  
            proxy_read_timeout 20s;  
            proxy_connect_timeout 20s;  
            proxy_send_timeout 20s;
            proxy_next_upstream error timeout;
            # 其他代理设置(可选)
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;

            proxy_pass http://backend;
        }
    }

    upstream backend {
        server 127.0.0.1:8080;
        server 127.0.0.1:8081;
    }
}

日志如下:

access.log

127.0.0.1 - - [07/Jun/2025:22:53:32 +0800] "GET /xxx/test HTTP/1.1" 502 497 "-" "PostmanRuntime/7.44.0"

127.0.0.1 - - [07/Jun/2025:22:53:50 +0800] "GET /xxx/test HTTP/1.1" 504 497 "-" "PostmanRuntime/7.44.0"

error.log

2025/06/07 22:53:30 [error] 44212#13196: *25 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /xxx/test HTTP/1.1", upstream: "http://127.0.0.1:8081/xxx/test", host: "localhost"

2025/06/07 22:53:32 [error] 44212#13196: *27 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /xxx/test HTTP/1.1", upstream: "http://127.0.0.1:8080/xxx/test", host: "localhost"

2025/06/07 22:53:32 [error] 44212#13196: *27 no live upstreams while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /xxx/test HTTP/1.1", upstream: "http://backend/xxx/test", host: "localhost"

2025/06/07 22:53:50 [error] 44212#13196: *25 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /xxx/test HTTP/1.1", upstream: "http://127.0.0.1:8080/xxx/test", host: "localhost"

相关推荐
杨云龙UP11 分钟前
Oracle数据库启动失败:ORA-29701、ORA-01565、ORA-17503故障处理记录_20260429
linux·运维·数据库·oracle·centos
Agent产品评测局15 分钟前
离散制造业生产流程优化,AI落地实操步骤详解:从传统自动化到企业级智能体的技术范式跃迁
运维·人工智能·ai·自动化
Gary Studio43 分钟前
ubuntu 16.04一键换源
linux·运维·ubuntu
又来敲代码了1 小时前
k8s的部署
linux·运维·云原生·容器·kubernetes
梦·D·1 小时前
安全运维工具箱sskit_v1.0.3 部署
运维
CDN3601 小时前
DNS 负载均衡技术架构与调度策略解析
运维·架构·负载均衡
忡黑梨1 小时前
eNSP_路由策略
运维·服务器·网络·华为·智能路由器·负载均衡
IT WorryFree1 小时前
FGT-KVM 完整部署极简教程(CentOS 7 + KVM 环境)
linux·运维·centos
上海云盾安全满满1 小时前
网站被攻击了,高防CDN相比与高防服务器有什么优点
运维·服务器
@encryption1 小时前
计算机网络 --- NAT
运维·服务器·计算机网络