Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downstream error 711: client request too frequent #160

Open
zh99998 opened this issue Dec 19, 2019 · 37 comments
Open

Downstream error 711: client request too frequent #160

zh99998 opened this issue Dec 19, 2019 · 37 comments

Comments

@zh99998
Copy link

zh99998 commented Dec 19, 2019

开了几个小时之后提速失效了,log如下

image

@zh99998
Copy link
Author

zh99998 commented Dec 19, 2019

重启程序会恢复

@Yemao7
Copy link

Yemao7 commented Feb 2, 2020

捕获
我也遇到这种情况.
宽带是辽宁移动100M
固件Pandora
不知该如何解决

@fffonion
Copy link
Owner

fffonion commented Feb 5, 2020

把重新请求的时间改到6小时试试?
https://github.com/fffonion/Xunlei-Fastdick/blob/6h/swjsq.py

@zh99998
Copy link
Author

zh99998 commented Feb 5, 2020

把重新请求的时间改到6小时试试?
https://github.com/fffonion/Xunlei-Fastdick/blob/6h/swjsq.py

谢,我在路由器上运行了新的版本了,目前正常,等过几个小时看看

@zh99998
Copy link
Author

zh99998 commented Feb 6, 2020

并没有解决,依然会每5分钟输出一次 client request too frequent

@yyysuo
Copy link

yyysuo commented Feb 6, 2020

docker版本遇到了相同的情况,盼解决,能在环境变量里面添加请求间隔参数么。

@fffonion
Copy link
Owner

fffonion commented Feb 7, 2020

那试试不重新登陆 😂
还是这个分支 https://github.com/fffonion/Xunlei-Fastdick/blob/6h/swjsq.py

@zh99998
Copy link
Author

zh99998 commented Feb 7, 2020

那试试不重新登陆 😂
还是这个分支 https://github.com/fffonion/Xunlei-Fastdick/blob/6h/swjsq.py

更新并运行了。

@zh99998
Copy link
Author

zh99998 commented Feb 8, 2020

不掉线了。
打印出来了大量这种log,这是符合预期的吗

xunlei-fastdick_1      | 00:31:28 Upgrade done: down 200M
xunlei-fastdick_1      | 00:41:18 Initializing upgrade
xunlei-fastdick_1      | 00:41:19 Upgrade done: down 200M
xunlei-fastdick_1      | 00:51:09 Initializing upgrade
xunlei-fastdick_1      | 00:51:10 Upgrade done: down 200M
xunlei-fastdick_1      | 01:01:00 Initializing upgrade
xunlei-fastdick_1      | 01:01:01 Upgrade done: down 200M
xunlei-fastdick_1      | 01:10:51 Initializing upgrade
xunlei-fastdick_1      | 01:10:52 Upgrade done: down 200M
xunlei-fastdick_1      | 01:20:42 Initializing upgrade
xunlei-fastdick_1      | 01:20:43 Upgrade done: down 200M
xunlei-fastdick_1      | 01:30:33 Initializing upgrade
xunlei-fastdick_1      | 01:30:34 Upgrade done: down 200M
xunlei-fastdick_1      | 01:40:24 Initializing upgrade
xunlei-fastdick_1      | 01:40:25 Upgrade done: down 200M
xunlei-fastdick_1      | 01:50:15 Initializing upgrade
xunlei-fastdick_1      | 01:50:16 Upgrade done: down 200M
xunlei-fastdick_1      | 02:00:07 Initializing upgrade
xunlei-fastdick_1      | 02:00:08 Upgrade done: down 200M
xunlei-fastdick_1      | 02:09:58 Initializing upgrade
xunlei-fastdick_1      | 02:09:59 Upgrade done: down 200M
xunlei-fastdick_1      | 02:19:49 Initializing upgrade
xunlei-fastdick_1      | 02:19:50 Upgrade done: down 200M
xunlei-fastdick_1      | 02:29:40 Initializing upgrade
xunlei-fastdick_1      | 02:29:41 Upgrade done: down 200M
xunlei-fastdick_1      | 02:39:31 Initializing upgrade
xunlei-fastdick_1      | 02:39:32 Upgrade done: down 200M

@fffonion
Copy link
Owner

fffonion commented Feb 8, 2020

不太对,但是至少不抽了
重新试试 https://github.com/fffonion/Xunlei-Fastdick/blob/6h/swjsq.py
感谢🙏

@yyysuo
Copy link

yyysuo commented Feb 8, 2020

反馈个情况,在PC上用下列脚本
https://raw.githubusercontent.com/fffonion/Xunlei-Fastdick/master/swjsq.py
生成的swjsq_wget.sh,复制到hiboy版本的pavadan固件中,稳定运行2天无任何问题,也没有异常日志。

@fffonion
Copy link
Owner

fffonion commented Feb 8, 2020

我有个快鸟后端在抽风的猜想,不一定对
634E2AD10966174037D05804CFFF31EA

@yyysuo
Copy link

yyysuo commented Feb 8, 2020

您的意思是昨天一直报请求频繁,是因为迅雷服务器抽风了?

@fffonion
Copy link
Owner

fffonion commented Feb 8, 2020

@yyysuo 有这可能,因为根据 @zh99998 最新提供的log,虽然脚本仍然存在一个逻辑问题,但是每十分钟一次的upgrade却没有触发后端的错误

@zh99998
Copy link
Author

zh99998 commented Feb 8, 2020

不太对,但是至少不抽了
重新试试 https://github.com/fffonion/Xunlei-Fastdick/blob/6h/swjsq.py
感谢🙏

半小时前更新的,到现在没打出过异常log,加速也还在。
再过几个小时看看情况

@zh99998
Copy link
Author

zh99998 commented Feb 8, 2020

@yyysuo 有这可能,因为根据 @zh99998 最新提供的log,虽然脚本仍然存在一个逻辑问题,但是每十分钟一次的upgrade却没有触发后端的错误

在6h版本以前,那个问题是持续存在的。不是偶尔现象。只要挂几个小时稳定会出现那个。

@zh99998
Copy link
Author

zh99998 commented Feb 9, 2020

放了一晚上,没打出任何异常log。提速还在,看起来好了。

@fffonion
Copy link
Owner

fffonion commented Feb 9, 2020

@zh99998 感谢,那我merge到master了

@yyysuo docker镜像也更新了

@yyysuo
Copy link

yyysuo commented Feb 11, 2020

docker版本的还是报错
05:24:49 Initializing upgrade
05:24:54 Downstream error 711: client request too frequent

我怀疑跟我的时区设置有关,但是加了TZ参数不生效呢。

@zh99998
Copy link
Author

zh99998 commented Feb 11, 2020

image
还是有。
我也是先怀疑了时区,然后现在这个是把时区改对之后再测试的。

从log的时间上看,刚运行不久之后就一直在打那个了,但是我记得刚启动不久看log是没有的。
我怀疑是整24小时之后才出现的问题

但是加了TZ参数不生效呢。
时区这么设置
volumes:
- /etc/localtime:/etc/localtime:ro

@zh99998
Copy link
Author

zh99998 commented Feb 11, 2020

另外就是在这个状态下,继续运行是永远不会恢复的,但是重启一下就会恢复
所以有可能不仅仅是频率问题,还可能跟做了哪些步骤有关

我猜想只要在远端发来711那个错误的时候就直接报错退出让 docker 重启它,可能就能稳定运行

@yyysuo
Copy link

yyysuo commented Feb 12, 2020

另外就是在这个状态下,继续运行是永远不会恢复的,但是重启一下就会恢复
所以有可能不仅仅是频率问题,还可能跟做了哪些步骤有关

我猜想只要在远端发来711那个错误的时候就直接报错退出让 docker 重启它,可能就能稳定运行

不是24小时之后失效的,基本上1个小时之后就失效了。另外老毛子固件上的我也在观察,老毛子固件上至少能保证24小时之内不操心

@zh99998
Copy link
Author

zh99998 commented Feb 12, 2020

image
来了一个新掉法。
早上7点24的时候看log发现掉了,重启过,然后13点的时候打出来个500,现在测试加速是不在了的。
重启后恢复

@zh99998
Copy link
Author

zh99998 commented Feb 12, 2020

所以能搞一个遇到任何错误就 throw 到顶层报错退出的模式吗,感觉可以缓解不少问题。

@fffonion
Copy link
Owner

感觉可能是重新加速的时候,加速请求upgrade和恢复请求recover中间没有限流导致的
我先本地试试

@fffonion
Copy link
Owner

我这边看起来没啥问题,但是路由器太烂了测不动速w
大家可以试试master分支上的新版

@yahaha-rf
Copy link

我这边看起来没啥问题,但是路由器太烂了测不动速w
大家可以试试master分支上的新版

路由器跑最新的脚本 无法提速 且过几个小时就会报
Downstream error 711: client request too frequent

@fffonion
Copy link
Owner

@xuezhichao19970719 能否贴一下 error 711附近的日志

@yahaha-rf
Copy link

@xuezhichao19970719 能否贴一下 error 711附近的日志

和楼上几个是一样的 坐标武汉电信
我重启了路由 日志被清了 等再跑几个小时才会出现这个日志
等下日志出来了我贴上来

@fffonion
Copy link
Owner

@xuezhichao19970719 新版的输出应该有一些变化的,可以检查一下是否用了master分支 https://github.com/fffonion/Xunlei-Fastdick/blob/master/swjsq.py

@yahaha-rf
Copy link

@xuezhichao19970719 新版的输出应该有一些变化的,可以检查一下是否用了master分支 https://github.com/fffonion/Xunlei-Fastdick/blob/master/swjsq.py

image

emm 换了最新的 错误变了 无法加速 但是我用迅雷快鸟网页端可以加速

@fffonion
Copy link
Owner

@xuezhichao19970719 这是上次没正常退出,过一段时间会变正常。测个速试试

@frostnotfall
Copy link

最新的脚本,虽然显示成功,但实际提速是失败的。
我是公网IP,重启路由器后运行脚本输出提示成功,但speedtest测速不到200Mb,然后我重启路由器,使用网页端提速试用,speedtest测速630Mb。
凌晨将近一点时测试的,应该可以排除带宽共享占用问题。

@yahaha-rf
Copy link

@xuezhichao19970719 这是上次没正常退出,过一段时间会变正常。测个速试试

最新的脚本,虽然显示成功,但实际提速是失败的。
我是公网IP,重启路由器后运行脚本输出提示成功,但speedtest测速不到200Mb,然后我重启路由器,使用网页端提速试用,speedtest测速630Mb。
凌晨将近一点时测试的,应该可以排除带宽共享占用问题。

我好了 就是开了脚本得等一会 才会加速

@zh99998
Copy link
Author

zh99998 commented Feb 24, 2020

我这里是提示成功但是实际没有提速

@yahaha-rf
Copy link

16:36:38 Login xunlei succeeded
16:36:38 Expire date for chaoji member: 20270307
16:36:38 To Upgrade: 湖北电信 down 100M -> 200M
16:36:38 To Upgrade: 湖北电信 down 100M -> 200M
16:36:39 Initializing upgrade
16:36:39 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582389400, u'sequence': 0}}
16:36:39 Downstream upgrade error 812: speedup server already speed up
16:36:39 Downstream already upgraded, continuing
19:33:51 Initializing upgrade
19:34:11 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582400053, u'sequence': 0}}
19:34:11 Downstream upgrade error 812: speedup server already speed up
19:34:11 Downstream already upgraded, continuing
22:31:26 Initializing upgrade
22:31:47 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582410709, u'sequence': 0}}
22:31:47 Downstream upgrade error 812: speedup server already speed up
22:31:47 Downstream already upgraded, continuing
01:29:01 Initializing upgrade
01:29:22 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582421364, u'sequence': 0}}
01:29:22 Downstream upgrade error 812: speedup server already speed up
01:29:22 Downstream already upgraded, continuing
04:26:37 Initializing upgrade
04:26:57 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582432019, u'sequence': 0}}
04:26:57 Downstream upgrade error 812: speedup server already speed up
04:26:57 Downstream already upgraded, continuing
07:24:14 Initializing upgrade
07:24:35 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582442677, u'sequence': 0}}
07:24:35 Downstream upgrade error 812: speedup server already speed up
07:24:35 Downstream already upgraded, continuing
09:03:03 Initializing upgrade
09:03:24 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582448606, u'sequence': 0}}
09:03:24 Downstream upgrade error 812: speedup server already speed up
09:03:24 Downstream already upgraded, continuing
12:00:38 Initializing upgrade
12:00:58 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582459261, u'sequence': 0}}
12:00:58 Downstream upgrade error 812: speedup server already speed up
12:00:58 Downstream already upgraded, continuing
14:58:13 Initializing upgrade
14:58:34 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582469916, u'sequence': 0}}
14:58:34 Downstream upgrade error 812: speedup server already speed up
14:58:34 Downstream already upgraded, continuing
17:55:44 Initializing upgrade
17:56:04 {'down': {u'errno': 812, u'message': u'speedup server already speed up', u'richmessage': u'\u62b1\u6b49\uff0c\u670d\u52a1\u5668\u8bf7\u6c42\u51fa\u9519\uff0c\u8bf7\u91cd\u8bd5', u'timestamp': 1582480567, u'sequence': 0}}
17:56:04 Downstream upgrade error 812: speedup server already speed up
17:56:04 Downstream already upgraded, continuing
19:04:59 Downstream keepalive error 513: not exist channel
19:05:00 Initializing upgrade
19:05:21 Upgrade done: down 200M
19:05:21 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582484723, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
19:05:21 Traceback (most recent call last):
File "/tmp/kuainiao/swjsq.py", line 495, in run
print(api_ret)
File "/tmp/kuainiao/swjsq.py", line 153, in print
_real_print(line, **kwargs)
IOError: [Errno 32] Broken pipe

19:10:11 Initializing upgrade
19:10:32 Upgrade done: down 200M
19:10:32 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582485034, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
22:07:45 Initializing upgrade
22:08:06 Upgrade done: down 200M
22:08:06 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582495689, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
01:05:20 Initializing upgrade
01:05:42 Upgrade done: down 200M
01:05:42 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582506345, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
04:02:56 Initializing upgrade
04:03:17 Upgrade done: down 200M
04:03:17 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582517000, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
07:00:31 Initializing upgrade
07:00:53 Upgrade done: down 200M
07:00:53 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582527656, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
08:39:21 Initializing upgrade
08:39:42 Upgrade done: down 200M
08:39:42 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582533585, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
11:36:56 Initializing upgrade
11:37:18 Upgrade done: down 200M
11:37:18 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582544241, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
14:34:33 Initializing upgrade
14:34:54 Upgrade done: down 200M
14:34:54 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582554898, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
17:32:08 Initializing upgrade
17:32:30 Upgrade done: down 200M
17:32:30 {'down': {u'province': u'hu_bei', u'sequence': 0, u'errno': 0, u'sp_name': u'\u7535\u4fe1', u'sp': u'tel', u'bandwidth': {u'downstream': 204800, u'upstream': 20480}, u'timestamp': 1582565553, u'message': u'\u63d0\u901f\u6210\u529f#', u'dial_account': u'hb::a111098107', u'province_name': u'\u6e56\u5317'}}
20:29:45 Initializing upgrade

不知道为啥。。总得等几个小时才能提速成功

@fffonion fffonion mentioned this issue Sep 10, 2020
@VwEl
Copy link

VwEl commented Aug 1, 2022

@xuezhichao19970719 这是上次没正常退出,过一段时间会变正常。测个速试试

希望可以增加定时重登或者定时重启

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants