This problem seems to have returned, though now the clock is set properly. Apr 11 13:56:33.000 [notice] Tor 0.2.4.20 (git-3cb5c70beec5bf46) opening log file. Apr 11 13:56:33.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Apr 11 13:56:33.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Apr 11 13:56:33.000 [notice] We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but wit h a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. B uilding openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) wou ld make ECDH much faster. Apr 11 13:56:33.000 [notice] We now have enough directory information to build circuits. Apr 11 13:56:33.000 [notice] Bootstrapped 80%: Connecting to the Tor network. Apr 11 13:56:36.000 [notice] Bootstrapped 85%: Finishing handshake with first hop. Apr 11 13:56:36.000 [notice] Bootstrapped 90%: Establishing a Tor circuit. Apr 11 13:56:36.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Apr 11 13:56:36.000 [notice] Bootstrapped 100%: Done. Apr 11 13:56:38.000 [notice] Your Guard Unnamed ($A0306CADEE237E9A3CD766F9858FC73EE8D70CF2) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 158/ 230. Use counts are 78/78. 159 circuits completed, 0 were unusable, 1 collapsed, and 30 timed out. For reference, your timeout cutoff is 60 seconds. Apr 11 13:57:10.000 [notice] Your Guard relaynet ($E2CFC6A603232D0EA3452B80170D7257417DC7A1) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 126 /181. Use counts are 81/81. 127 circuits completed, 0 were unusable, 1 collapsed, and 14 timed out. For reference, your timeout cutoff is 60 seconds.
Can someone please assist? All my services are down. On 04/11/2014 06:02 AM, Cyrus wrote: > I am having a problem with my Tor daemon on my server which is Gentoo > Hardened. Hidden services never seem to come online since restarting. > There are some interesting messages in the log about the Tor network > being overloaded. I've tried to look them up but couldn't find anything. > I think there might be some kind of bug. > > This is urgent, I need help asap. > > Apr 11 19:54:27.000 [notice] Tor 0.2.4.20 (git-3cb5c70beec5bf46) opening > log file. > Apr 11 19:58:39.000 [notice] Catching signal TERM, exiting cleanly. > Apr 11 19:58:39.000 [notice] Tor 0.2.4.20 (git-3cb5c70beec5bf46) opening > log file. > Apr 11 19:58:39.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. > Apr 11 19:58:39.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. > Apr 11 19:58:39.000 [notice] We were built to run on a 64-bit CPU, with > OpenSSL 1.0.1 or later, but wit > h a version of OpenSSL that apparently lacks accelerated support for the > NIST P-224 and P-256 groups. B > uilding openssl with such support (using the enable-ec_nistp_64_gcc_128 > option when configuring it) wou > ld make ECDH much faster. > Apr 11 19:58:39.000 [notice] We now have enough directory information to > build circuits. > Apr 11 19:58:39.000 [notice] Bootstrapped 80%: Connecting to the Tor > network. > Apr 11 19:58:42.000 [notice] Bootstrapped 85%: Finishing handshake with > first hop. > Apr 11 19:58:42.000 [notice] Bootstrapped 90%: Establishing a Tor circuit. > Apr 11 19:58:42.000 [notice] Your Guard v235 > ($F3416AAAC641B106022BC051F64DBBA18C52D8CF) is failing mor > e circuits than usual. Most likely this means the Tor network is > overloaded. Success counts are 155/222 > . Use counts are 91/91. 158 circuits completed, 0 were unusable, 3 > collapsed, and 21 timed out. For ref > erence, your timeout cutoff is 60 seconds. > Apr 11 19:58:43.000 [notice] Tor has successfully opened a circuit. > Looks like client functionality is > working. > Apr 11 19:58:43.000 [notice] Bootstrapped 100%: Done. > Apr 11 19:58:43.000 [notice] Your Guard relaynet > ($E2CFC6A603232D0EA3452B80170D7257417DC7A1) is failing > more circuits than usual. Most likely this means the Tor network is > overloaded. Success counts are 196 > /280. Use counts are 95/95. 199 circuits completed, 0 were unusable, 3 > collapsed, and 28 timed out. For > reference, your timeout cutoff is 60 seconds. > Apr 11 19:58:43.000 [notice] Your Guard Unnamed > ($A0306CADEE237E9A3CD766F9858FC73EE8D70CF2) is failing > more circuits than usual. Most likely this means the Tor network is > overloaded. Success counts are 110/ > 158. Use counts are 95/95. 111 circuits completed, 0 were unusable, 1 > collapsed, and 12 timed out. For > reference, your timeout cutoff is 60 seconds. > -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
