nginx-upsync-module
nginx-upsync-module copied to clipboard
upsync_timeout: timed out reading upsync_server
2018/12/05 14:08:51 [error] 31184#0: [WARN] upsync_timeout: timed out reading upsync_server: 172.18.41.169:80 2018/12/05 14:08:51 [error] 31184#0: [WARN] upsync_timeout: timed out reading upsync_server: 172.18.41.169:80 2018/12/05 14:08:51 [error] 31183#0: [WARN] upsync_timeout: timed out reading upsync_server: 172.18.41.169:80 2018/12/05 14:08:52 [error] 31183#0: [WARN] upsync_timeout: timed out reading upsync_server: 172.18.41.169:80 2018/12/05 14:08:52 [error] 31184#0: [WARN] upsync_timeout: timed out reading upsync_server: 172.18.41.169:80 2018/12/05 14:08:53 [error] 31184#0: [WARN] upsync_timeout: timed out reading upsync_server: 172.18.41.169:80 2018/12/05 14:09:17 [error] 31184#0: [WARN] upsync_timeout: timed out reading upsync_server: 172.18.41.169:80 2018/12/05 14:09:19 [error] 31183#0: [WARN] upsync_timeout: timed out reading upsync_server: 172.18.41.169:80
每隔一段时间就会报这个错误
请问解决了吗?
It's not a problem. Each connection(between nginx and conf server) will set timeout for the long pulling. If it's no changes or updates about the value(proxy servers list) during the time, the connection will cut off and try to get a new connection. The message is just a hint which tell you there is no changes.
Maybe we should change the log level so those messages won't be logged as [error]
根据观察错误日志出现的时间是upsync_timeout+upsync_interval,是pulling到期后模块发起的FIN包。但是为什么把它当成错误日志呢....容易引起误解,以为配置不当或者网络有波动啥的