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"

相关推荐
HalvmånEver3 分钟前
Linux:线程同步
linux·运维·服务器·线程·同步
岁杪杪8 分钟前
关于运维:LINUX 零基础
运维·服务器·php
tianyuanwo32 分钟前
企业级NTP客户端配置指南:基于内部NTP服务器的实践
运维·服务器·ntp客户端
芷栀夏38 分钟前
CANN开源实战:基于DrissionPage构建企业级网页自动化与数据采集系统
运维·人工智能·开源·自动化·cann
寄存器漫游者1 小时前
Linux 软件编程 - IO 编程
linux·运维·spring
charlotte102410241 小时前
高并发:关于在等待学校教务系统选课时的碎碎念
java·运维·网络
gaize12131 小时前
Moltbot(Clawdbot) 专属轻量服务器
运维·服务器
一分半心动2 小时前
宝塔面板lnmp架构,tp6框架网站伪静态
nginx·php
鸽芷咕2 小时前
DrissionPage 成 CANN 仓库爆款自动化工具:背后原因何在?
运维·python·自动化·cann
池央2 小时前
CANN 算子生态的深度演进:稀疏计算支持与 PyPTO 范式的抽象层级
运维·人工智能·信号处理