summerstar8 / snova

Automatically exported from code.google.com/p/snova
0 stars 0 forks source link

GAE 500的问题 #198

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
现在GAE可能某个IP用着用着就会挂掉,但重启Snova一下换一个I
P就可以接着用,可不可以Snova在碰到GAE出现问题的时候自动��
�下一个IP,或者重新解析一次google的地址获得新的IP,直到没
有一个IP连得上最后自动走C4?

Original issue reported on code.google.com by bibup...@gmail.com on 23 Nov 2012 at 10:11

GoogleCodeExporter commented 9 years ago
snova/gsnova都已提供了hosts配置文件可供修改,多个IP默认是轮�
��选择
snova修改conf/hosts.conf
gsnova修改hosts/user_hosts.conf

Original comment by yinqiwen@gmail.com on 23 Nov 2012 at 12:35

GoogleCodeExporter commented 9 years ago
我的意思是,它启动的时候虽然会自动选IP,但当选定了一个
IP后,这个IP被暂时封堵的时候不会重新选一个,必须重启才�
��换新的IP。

Original comment by bibup...@gmail.com on 23 Nov 2012 at 1:04

GoogleCodeExporter commented 9 years ago
你如果修改系统hosts,大部分应用都要重启。绝大部分程序都
会缓存hosts文件内容,防止频繁读取

Original comment by yinqiwen@gmail.com on 23 Nov 2012 at 1:07

GoogleCodeExporter commented 9 years ago
我说的是重启snova,比方说用着用着它提示GAE上不了了,浏览
器提示500错误,重启一下snova后它会重新搜索新的IP,这个时�
��就可以继续用了,如果不用重启它就会自动搜索新IP,或者�
��到C4就好了。

Original comment by bibup...@gmail.com on 23 Nov 2012 at 1:58

GoogleCodeExporter commented 9 years ago
gsnova0.19.0里改过一个类似的问题

Original comment by yinqiwen@gmail.com on 23 Nov 2012 at 2:08

GoogleCodeExporter commented 9 years ago
我这里也发现这种情况,当一个google的IP挂掉了,客户端没有尝�
��其他IP,导致只能重启.我改的是cloud_hosts.conf这个文件,user_host
s.conf配置appspot的IP不起作用

Original comment by disun...@gmail.com on 24 Nov 2012 at 1:04

GoogleCodeExporter commented 9 years ago
I think my problem is the same. I am using rhcloud as server side.
Frequently, I got this on different urls:
2012/12/10 17:20:43 forward.go:474: Session[64]Request GET 
http://wiki.tinycorelinux.net/
2012/12/10 17:20:44 forward.go:474: Session[64]Request GET 
http://wiki.tinycorelinux.net/lib/exe/css.php?t=vector&tseed=1332664051
2012/12/10 17:20:44 forward.go:474: Session[65]Request GET 
http://wiki.tinycorelinux.net/lib/exe/css.php?s=all&t=vector&tseed=1332664051
2012/12/10 17:20:44 forward.go:474: Session[66]Request GET 
http://wiki.tinycorelinux.net/lib/exe/js.php?tseed=1332664051
2012/12/10 17:20:45 forward.go:474: Session[67]Request GET 
http://wiki.tinycorelinux.net/lib/exe/indexer.php?id=welcome&1355131239
2012/12/10 17:20:45 forward.go:474: Session[68]Request GET 
http://wiki.tinycorelinux.net/lib/exe/css.php?s=print&t=vector&tseed=1332664051
2012/12/10 17:20:46 forward.go:474: Session[68]Request GET 
http://wiki.tinycorelinux.net/lib/exe/opensearch.php
2012/12/10 17:20:47 forward.go:474: Session[68]Request GET 
http://wiki.tinycorelinux.net/?do=search&id=boot&button=
2012/12/10 17:20:49 forward.go:474: Session[69]Request GET 
http://wiki.tinycorelinux.net/lib/images/loading.gif
2012/12/10 17:20:56 forward.go:474: Session[69]Request GET 
http://wiki.tinycorelinux.net/wiki:boot_options
2012/12/10 17:20:56 forward.go:517: Session[69]Recv response with error 
unexpected EOF
2012/12/10 17:20:56 dispatch.go:140: Session[69]Process error:unexpected EOF 
for host:wiki.tinycorelinux.net
2012/12/10 17:20:56 dispatch.go:196: Session[69]Failed to read http request:use 
of closed network connection
2012/12/10 17:20:56 forward.go:474: Session[68]Request GET 
http://wiki.tinycorelinux.net/favicon.ico
2012/12/10 17:20:56 forward.go:517: Session[68]Recv response with error 
unexpected EOF
2012/12/10 17:20:56 dispatch.go:140: Session[68]Process error:unexpected EOF 
for host:wiki.tinycorelinux.net
2012/12/10 17:20:56 dispatch.go:196: Session[68]Failed to read http request:use 
of closed network connection

Original comment by Magiclouds on 10 Dec 2012 at 9:23

GoogleCodeExporter commented 9 years ago
Forgot to mention, my problem could be solved by a few F5.

Original comment by Magiclouds on 10 Dec 2012 at 9:23

GoogleCodeExporter commented 9 years ago
Use 127.0.01:48102 without spac support as your proxy , not 127.0.0.1:48100 
with spac support.

Original comment by yinqiwen@gmail.com on 10 Dec 2012 at 9:26

GoogleCodeExporter commented 9 years ago
你是说关闭SPAC功能?

Original comment by Magiclouds on 11 Dec 2012 at 7:21

GoogleCodeExporter commented 9 years ago
参考 http://code.google.com/p/snova/issues/detail?id=254

Original comment by yinqiwen@gmail.com on 11 Dec 2012 at 7:23

GoogleCodeExporter commented 9 years ago
也就是说抛弃gsnova自己的spac,用swichysharp的规则来切换代理��
�
个人感觉这不是用不用代理的问题,而是服务端/客户端会��
�现连接被异常关闭,snova自身不会再次尝试连接,而是直接��
�回500错误。
因为什么都不用改,出现错误时多刷新几次即可解决。另外��
�个错误确实容易在几个地址上出现,没检查是否和各规则有�
��。

Original comment by Magiclouds on 11 Dec 2012 at 7:41

GoogleCodeExporter commented 9 years ago
比如forward.go:517: Session[69]Recv response with error unexpected EOF

出现这个一般是关键词过滤造成的连接重置,spac内置的GFWList
没法涵盖所有情况,而且尝试连接目前只在IP被屏蔽,连接不
上的情况下更有效

Original comment by yinqiwen@gmail.com on 11 Dec 2012 at 7:45

GoogleCodeExporter commented 9 years ago
那这是本地与snova服务端之间的重置?是因为中间未加密么?

Original comment by Magiclouds on 11 Dec 2012 at 7:51

GoogleCodeExporter commented 9 years ago
forward.go一般表示是直连

Original comment by yinqiwen@gmail.com on 11 Dec 2012 at 7:58

GoogleCodeExporter commented 9 years ago
这样……有趣,不用代理的话反而没发生过类似问题……

Original comment by Magiclouds on 11 Dec 2012 at 9:03