分析日志解决无法连接到Tor网络的问题_Jasey_Wang_百度空间

一.Failed to bind one of the listener ports

日志示例:

这种情况大多是因为你开了两个Tor(例如本地已经启动了一个Tor又启动另一个TorFirefox),或者之前的Tor没有xx退出。

解决方法:打开任务管理器,关闭所有的Tor进程(Tor.exe)和Vidalia进程(Vidalia.exe)后再启动Tor

二.I learned some more directory information, but not enough to build a circuit

日志示例:

一月 18 10:24:03.343 [注意] Tor v0.2.0.31 (r16744). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 2 [workstation] {terminal services, single user})

一月 18 10:24:03.343 [注意] Initialized libevent version 1.4.7-stable using method win32. Good.

一月 18 10:24:03.343 [注意] Opening Socks listener on 127.0.0.1:9050

一月 18 10:24:03.343 [注意] Opening Control listener on 127.0.0.1:9051

一月 18 10:24:03.671 [注意] I learned some more directory information, but not enough to build a circuit: We have no network-status consensus.

大多数情况下都是因为Tor的节点信息过旧导致的,添加网桥后重新连接即可。如果已经添加了网桥,说明这个网桥已经失效(同时Vidalia控制面板中会提示“连接中继目录feiled(没有可用链路)”)。

三.Stuck at xx%

日志示例:

一月 21 21:52:59.593 [Notice] Tor v0.2.1.20. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})

一月 21 21:52:59.593 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.

一月 21 21:52:59.593 [Notice] Opening Socks listener on 127.0.0.1:9050

一月 21 21:52:59.593 [Notice] Opening Control listener on 127.0.0.1:9125

一月 21 21:52:59.593 [Notice] Parsing GEOIP file.

一月 21 21:53:03.046 [Notice] Bootstrapped 10%: Finishing handshake with directory server.

一月 21 21:53:23.687 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)

如果没有添加网桥,请添加网桥后再重新连接,如果添加网桥后还是反复出现这个提示,说明网桥已失效,换一个网桥重新添加即可。

四.Finishing handshake with directory server. Operation timed out

日志示例:

1月 10 16:09:14.454 [Notice] Tor v0.2.1.20. This is experimental software. Do not rely on it for strong anonymity. (Running on Darwin i386)

1月 10 16:09:14.455 [Notice] Initialized libevent version 1.4.12-stable using method kqueue. Good.

1月 10 16:09:14.455 [Notice] Opening Socks listener on 127.0.0.1:9050

1月 10 16:09:14.456 [Notice] Opening Control listener on 127.0.0.1:9051

1月 10 16:09:15.135 [Notice] Bootstrapped 10%: Finishing handshake with directory server.

1月 10 16:10:29.763 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Operation timed out; TIMEOUT; count 3; recommendation warn)

1月 10 16:10:29.764 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Operation timed out; TIMEOUT; count 4; recommendation warn)

五.no known bridge descriptors running yet/No live bridge descriptors

如果你使用了GEOIPS文件,说文件已过期(GEOIPS文件有效期为2-4天),该用网桥连接即可。

六.出现 Our clock is xx hours, xx minutes behind the time 错误并长时间卡在I learned some more directory information, but not enough to build a circuit

示例:

一月03 08:06:33.390 [Warning] Our clock is 22 hours, 53 minutes behind the time published in the consensus network status document (2010-01-03 23:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!

一月03 08:06:33.406 [Notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.

这个错误不看日志是很难察觉到的,很久之前我曾被这个错误折腾的很惨,重装多次系统都无法解决这个问题。

解决的方法很简单,你设置了错误的时区或时间,只要将时区改为”UTC+08:00 北京,香港”即或与Internet时间服务器同步一下即可

其实总结起来,{zd0}的问题就是bridge失效了,应此遇到问题,首先应该想到的是更换网巧。



郑重声明:资讯 【分析日志解决无法连接到Tor网络的问题_Jasey_Wang_百度空间】由 发布,版权归原作者及其所在单位,其原创性以及文中陈述文字和内容未经(企业库qiyeku.com)证实,请读者仅作参考,并请自行核实相关内容。若本文有侵犯到您的版权, 请你提供相关证明及申请并与我们联系(qiyeku # qq.com)或【在线投诉】,我们审核后将会尽快处理。
—— 相关资讯 ——