今天在测试大商创后台系统时,打开店铺结算,查看店铺对应的订单列表时,该列表自动跳转到502,查看线上和测试环境都能正常打开,唯独我的电脑上打开是502,

查询nginx的error.log日志,记录了如下错误

2019/11/26 10:38:55 [error] 328604#333604: *10 upstream sent too big header while reading response header from upstream, client: 127.0.0.1, server: myshop.cn, request: "GET /admin/merchants_commission.php?act=commission_amount&seller=1,2,4,65,69,70,71,72,73,76,81,82,83,85,162&1574735928782782 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9001", host: "myshop.cn", referrer: "http://myshop.cn/admin/merchants_commission.php?act=list"
2019/11/26 10:38:59 [error] 328604#333604: *3 upstream sent too big header while reading response header from upstream, client: 127.0.0.1, server: myshop.cn, request: "GET /admin/merchants_commission.php?act=commission_amount&type=all&cycle=-1&1574735928776776 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9001", host: "myshop.cn", referrer: "http://myshop.cn/admin/merchants_commission.php?act=list"
2019/11/26 10:39:00 [error] 328604#333604: *15 upstream sent too big header while reading response header from upstream, client: 127.0.0.1, server: myshop.cn, request: "GET /admin/merchants_commission.php?act=order_list&id=1 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9001", host: "myshop.cn", referrer: "http://myshop.cn/admin/merchants_commission.php?act=edit&id=1"
2019/11/26 10:39:00 [error] 328604#333604: *15 CreateFile() "D:/phpstudy_pro/WWW/youhou/admin/error/502.html" failed (3: The system cannot find the path specified), client: 127.0.0.1, server: myshop.cn, request: "GET /admin/error/502.html HTTP/1.1", host: "myshop.cn", referrer: "http://myshop.cn/admin/merchants_commission.php?act=edit&id=1"
2019/11/26 10:39:00 [error] 328604#333604: *15 CreateFile() "D:/phpstudy_pro/WWW/youhou/error/404.html" failed (3: The system cannot find the path specified), client: 127.0.0.1, server: myshop.cn, request: "GET /admin/error/502.html HTTP/1.1", host: "myshop.cn", referrer: "http://myshop.cn/admin/merchants_commission.php?act=edit&id=1"

百度了一下,找到了解决方法,再此记录一下

在 nginx.conf 的http段,加入下面的配置:

proxy_buffer_size 128k;

proxy_buffers  32 32k;

proxy_busy_buffers_size 128k;

重启后一般就可以解决, 如果还是报502,再在host配置的php段加入下面配置:

fastcgi_buffer_size 128k;

fastcgi_buffers 4 256k;

fastcgi_busy_buffers_size 256k;

重启nginx即可。

参考:https://www.jianshu.com/p/389f45d0e7a2

  

今天测试大商创,遇到了 upstream sent too big header while reading response header from upstream的更多相关文章

  1. nginx 错误502 upstream sent too big header while reading response header from upstream

    查看nginx的错误日志,得到以下错误信息:upstream sent too big header while reading response header from upstream按字面意思理 ...

  2. 修复Nginx 502错误:upstream sent too big header while reading response header from upstream

    原文出处:https://www.cnblogs.com/jpfss/p/10237463.html 便于以后参考我复制了过来! cookies的值超出了范围我是说 看看了一下日志 错误502 ups ...

  3. nginx log 错误502 upstream sent too big header while reading response header from upstream

    cookies的值超出了范围我是说 看看了一下日志 错误502 upstream sent too big header while reading response header from upst ...

  4. 出现upstream sent too big header while reading response header from upstream错误

    一个POS系统,出现upstream sent too big header while reading response header from upstream错误. 1.反向代理端,可以放到se ...

  5. nginx 502错误 upstream sent too big header while reading response header from upstream

    原本的设置是 proxy_buffer_size 4k; proxy_buffers 4 32k; proxy_busy_buffers_size 64k; 在这种配置下,使用fiddler进行抓包分 ...

  6. Nginx 502错误:upstream sent too big header while reading response header from upstream

    原因: 在使用Shiro的rememberMe功能时,服务器返回response的header部分过大导致. 解决方法: https://stackoverflow.com/questions/238 ...

  7. 修复Nginx报错:upstream sent too big header while reading response header from upstream

    在 nginx.conf 的http段,加入下面的配置: proxy_buffer_size 128k; proxy_buffers 32k; proxy_busy_buffers_size 128k ...

  8. Nginx" upstream prematurely closed connection while reading response header from upstream"问题排查

    问题背景 我们这边是一个基于Nginx的API网关(以下标记为A),最近两天有调用方反馈,偶尔会出现502错误,我们从Nginx的error日志里看,就会发现有" upstream prem ...

  9. upstream timed out (110: Connection timed out) while reading response header from upstream, client:

    遇到的问题 之前没配置下面这段,访问时候偶尔会出现 504 gateway timeout,由于偶尔出现,所以不太好排查 proxy_connect_timeout 300s;proxy_read_t ...

随机推荐

  1. 使用ImageProcessor、CodeCarvings.Piczard组件生成缩略图和添加水印

    技术栈: 1.ImageProcessor(专业图像处理,不能合成水印,NetCore中有它的升级版ImageSharp目前是预览包) 2.CodeCarvings.Piczard(缩略图,水印都能搞 ...

  2. List对象遍历时null判断

    使用for循环遍历list处理list元素时,对null值判断: 1.list为null时空指针异常 2.list不为空,但是list.size()=0时,不执行for循环内代码块 3.list.si ...

  3. UVA 11174 Stand in a Line,UVA 1436 Counting heaps —— (组合数的好题)

    这两个题的模型是有n个人,有若干的关系表示谁是谁的父亲,让他们进行排队,且父亲必须排在儿子前面(不一定相邻).求排列数. 我们假设s[i]是i这个节点,他们一家子的总个数(或者换句话说,等于他的子孙数 ...

  4. rsync+inotify 实时双向同步

    前言 在遇到需要 nginx 负载均衡,承受较高并发的情况,同时会有双机相同目录内容须保持一致的需求 rsync+inotify 是一个不错的解决方案,相较于 rsync+sersync 在处理大量文 ...

  5. Mac下持续集成-查看占用的端口及kill

    (base) localhost:~ ligaijiang$ lsof -i tcp:8080 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME Q ...

  6. 使用LuceneUtil工具类,完成CURD操作

    package loaderman.curd; import java.util.ArrayList; import java.util.List; import loaderman.entity.A ...

  7. Linux系统管理_主题02 :管好文件(1)_2.4 链接文件_ln

    在 Linux 中,链接有两种:符号链接(symbolic link)和硬链接(hard link).  删除一个符号链接不会影响到这个符号链接指向的目标文件或目 录:  反过来,删除.移动或者重 ...

  8. Linux批量处理常用方式

    批量处理思路在工作中使用的频率比较高,比如批量清理进程.批量删除文件.批量机器执行脚本等. 一.批量清理带java字样的进程 方式1:使用shell while语法. ${line}; done sh ...

  9. jenkins配置jdk、git、maven

    进入首页->系统管理->全局工具配置 配置jdk 查找jdk安装路径 如果是容器版jenkins,就登进容器里面查看jdk路径 [root@test2 ~]# echo $JAVA_HOM ...

  10. Minimum number of swaps required to sort an array

    https://www.hackerrank.com/challenges/minimum-swaps-2/problem Minimum Swaps II You are given an unor ...