我在后端(与Puma的Rails)绑定到unix套接字的app服务器这是nginx配置的相关部分location /live/ {proxy_pass http://app; # match the name of upstream directive which is defined aboveproxy_set_header Host $hos...
我在后端(与Puma的Rails)绑定到unix套接字的app服务器
这是nginx配置的相关部分
location /live/ {
proxy_pass http://app; # match the name of upstream directive which is defined above
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_redirect off;
proxy_set_header Connection 'Upgrade';
proxy_http_version 1.1;
chunked_transfer_encoding off;
send_timeout 300;
proxy_send_timeout 300;
keepalive_timeout 7200;
}
SSE事件来自/ live /,因此我调整了ngix配置来处理对此路由的所有请求.
问题是连接在60秒后完全关闭.这是我在响应头中看到的内容
Cache-Control:no-cache
Connection:keep-alive
Content-Type:text/event-stream
Date:Mon, 04 Nov 2013 13:41:52 GMT
Server:nginx
X-Content-Type-Options:nosniff
X-Frame-Options:SAMEORIGIN
X-Request-Id:7065a7bc-3450-4fe2-b60c-33dfa8d41951
X-Runtime:0.010852
X-UA-Compatible:chrome=1
X-XSS-Protection:1; mode=block
所以似乎nginx将初始响应设置为close.为什么keepalive_timeout在这里不起作用.
在nginx error.log中我看到了
2013/11/04 13:42:52 [error] 3689#0: *9 upstream timed out (110: Connection timed out) while reading upstream, client: ......., server: myapp.com, request: "GET /live/events HTTP/1.1", upstream: "http://unix:/home/ubuntu/myapp/shared/sockets/puma.sock:/live/events", host: "myapp.com"
解决方法:
为了防止其他人遇到Nginx Puma Rails的Timeout错误,Nginx中的以下配置应该将超时时间增加到605秒(10分5秒):
server {
# ... here goes your proxy configuration
# Avoid 504 HTTP Timeout Errors
proxy_connect_timeout 605;
proxy_send_timeout 605;
proxy_read_timeout 605;
send_timeout 605;
keepalive_timeout 605;
}
沃梦达教程
本文标题为:ruby-on-rails – Nginx在60秒后完全超时
猜你喜欢
- R语言绘图数据可视化pie chart饼图 2022-12-10
- 汇编语言程序设计之根据输入改变屏幕颜色的代码 2023-07-06
- Golang http.Client设置超时 2023-09-05
- Go Web开发进阶实战(gin框架) 2023-09-06
- R语言-如何切换科学计数法和更换小数点位数 2022-11-23
- Ruby 迭代器知识汇总 2023-07-23
- Ruby on Rails在Ping ++ 平台实现支付 2023-07-22
- R语言关于二项分布知识点总结 2022-11-30
- Swift超详细讲解指针 2023-07-08
- Ruby的字符串与数组求最大值的相关问题讨论 2023-07-22