Custom Query (26254 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (94 - 96 of 26254)

Ticket Resolution Summary Owner Reporter
#1307 fixed Hosting many hidden services causes many errors and takes hours to start up rransom marked
Description

In my torrc i have configured about 200 hidden services (I have a reason for this, they are needed and im not just wasting them)

When I start tor it takes hours to start while using 99% CPU and giving many errors in the logs. I have been having this problem for a while but it seems to get worse as i add more hidden services.

Older version of tor (0.2.1.22 and below) gave many errors like this. [warn] Error launching circuit to node xxxx for service xxxxxxx.

Tor 0.2.1.24 (i never used 0.2.1.23) gives different errors and seems to be taking way longer to start. Here is my log for 0.2.1.24.

Mar 13 02:11:11.841 [notice] Parsing GEOIP file. Mar 13 02:11:12.077 [notice] OpenSSL OpenSSL 0.9.8m 25 Feb 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation Mar 13 02:11:13.862 [notice] We now have enough directory information to build circuits. Mar 13 02:11:13.862 [notice] Bootstrapped 80%: Connecting to the Tor network. Mar 13 02:13:11.982 [notice] Bootstrapped 85%: Finishing handshake with first hop. Mar 13 02:13:12.503 [notice] Bootstrapped 90%: Establishing a Tor circuit. Mar 13 02:13:12.993 [notice] Your system clock just jumped 119 seconds forward; assuming established circuits no longer work. Mar 13 02:15:25.191 [notice] Your system clock just jumped 133 seconds forward; assuming established circuits no longer work. Mar 13 02:15:26.194 [notice] We stalled too much while trying to write 317968 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 7, type OR, state 8, marked at main.c:722). Mar 13 02:15:28.954 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Mar 13 02:15:28.954 [notice] Bootstrapped 100%: Done. Mar 13 02:17:57.051 [notice] Your system clock just jumped 123 seconds forward; assuming established circuits no longer work. Mar 13 02:20:08.157 [notice] Your system clock just jumped 131 seconds forward; assuming established circuits no longer work. Mar 13 02:20:08.193 [notice] We stalled too much while trying to write 303728 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 15, type OR, state 8, marked at main.c:722). Mar 13 02:20:08.194 [notice] We stalled too much while trying to write 309872 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 7, type OR, state 8, marked at main.c:722). Mar 13 02:20:47.760 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Mar 13 02:23:01.965 [notice] Your system clock just jumped 126 seconds forward; assuming established circuits no longer work. Mar 13 02:25:13.073 [notice] Your system clock just jumped 132 seconds forward; assuming established circuits no longer work. Mar 13 02:25:13.104 [notice] We stalled too much while trying to write 150640 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 13, type OR, state 8, marked at main.c:722). Mar 13 02:25:13.144 [notice] We stalled too much while trying to write 159232 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 15, type OR, state 8, marked at main.c:722). Mar 13 02:25:13.144 [notice] We stalled too much while trying to write 160768 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 11, type OR, state 8, marked at main.c:722). Mar 13 02:25:14.505 [notice] We're missing a certificate from authority with signing key 08D85E2B51D1962DF9EAB4DAF1F1A0061FF0E954: launching request. Mar 13 02:25:18.434 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Mar 13 02:27:56.202 [notice] Your system clock just jumped 120 seconds forward; assuming established circuits no longer work. Mar 13 02:30:09.555 [notice] Your system clock just jumped 133 seconds forward; assuming established circuits no longer work. Mar 13 02:30:09.599 [notice] We stalled too much while trying to write 246384 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 28, type OR, state 8, marked at main.c:722). Mar 13 02:30:09.600 [notice] We stalled too much while trying to write 245360 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 26, type OR, state 8, marked at main.c:722). Mar 13 02:30:09.600 [notice] We stalled too much while trying to write 232960 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 24, type OR, state 8, marked at main.c:722). Mar 13 02:30:16.401 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Mar 13 02:32:57.525 [notice] Your system clock just jumped 120 seconds forward; assuming established circuits no longer work. Mar 13 02:35:10.484 [notice] Your system clock just jumped 133 seconds forward; assuming established circuits no longer work. Mar 13 02:35:10.528 [notice] We stalled too much while trying to write 154224 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 24, type OR, state 8, marked at main.c:722). Mar 13 02:35:10.529 [notice] We stalled too much while trying to write 161392 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 26, type OR, state 8, marked at main.c:722). Mar 13 02:35:10.530 [notice] We stalled too much while trying to write 161392 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 33, type OR, state 8, marked at main.c:722). Mar 13 02:35:10.531 [notice] We stalled too much while trying to write 158320 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 25, type OR, state 8, marked at main.c:722). Mar 13 02:35:10.532 [notice] We stalled too much while trying to write 170096 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 28, type OR, state 8, marked at main.c:722). Mar 13 02:35:10.532 [notice] We stalled too much while trying to write 156672 bytes to address [scrubbed]. If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 9, type OR, state 8, marked at main.c:722). Mar 13 02:35:13.440 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Mar 13 02:38:00.857 [notice] Your system clock just jumped 122 seconds forward; assuming established circuits no longer work

.... it continues like this for hours My clock did not jump, the missing time is when tor is stuck in 99% cpu use. There is nothing wrong with my network either. It works if I remove the many hidden services.

When it does finally start up, tor and all the hidden services work fine (at least it did in 0.2.1.22, im still waiting for 0.2.1.24 to start after 2 hours.

[Automatically added by flyspray2trac: Operating System: All]

#1308 fixed Orbot broken on rooted Droid when root is disallowed n8fr8 ioerror
Description

I helped someone install Orbot on a rooted Droid tonight. Launching Orbot properly prompted the user for root, the user doesn't trust us, and thus denied the request. This caused Orbot to paint a black screen and hung Orbot. The user was prompted to quit Orbot by the OS. The user forced it closed and promptly laughed in my face.

Good times.

[Automatically added by flyspray2trac: Operating System: Other]

#1310 fixed Suggestion: Adding an explanation on dir-spec nickm ilter
Description

Hello,

I asked a question on #tor and Sebastian_ gave a good explanation to reply it. I suggest that someone should put this explanation on dir-spec. All of them below;

Q: In dir-spec @1801 it says: "Finally the authority MAY check that the router is not blacklisted beacuse of it's key, IP or another reason". Why is there MAY word? Is it possible that a router desc. pass this step without be verified whether it's on blaclisted or not?

A: that means that depending on the Tor implementation and the configuration of the directory authority, it may or may not blacklist relays. The specification does not require it to keep such a blacklist.

Thanks in advance. ilter

[Automatically added by flyspray2trac: Operating System: All]

Note: See TracQuery for help on using queries.