Project-Insanity

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
<code>
Feb 15 17:03:44 tuxzentrale tor[150854]: Feb 15 17:03:44.000 [notice] Tor has not observed any network activity for the past 101 seconds. Disabling circuit build timeout recording.
Feb 15 17:04:33 tuxzentrale tor[150854]: Feb 15 17:04:33.000 [notice] Our IP address has changed.  Rotating keys...
Feb 15 17:04:33 tuxzentrale tor[150854]: Feb 15 17:04:33.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 150 seconds during 46 circuit attempts.
Feb 15 17:04:34 tuxzentrale tor[150854]: Feb 15 17:04:34.000 [warn] Guard arbitraryTessa3 ($54FF87E18CF4B351BB078A640A4DC5265969485E) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 84/195. Use counts are 43/48. 182 circuits completed, 0 were unusable, 97 collapsed, and 101 timed out. For reference, your timeout cutoff is 60 seconds.
Feb 15 17:04:36 tuxzentrale tor[150854]: Feb 15 17:04:36.000 [warn] Guard Droutnutch ($5C80CB557C96CAD80EF8EC6AB55865329DF74B1B) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 66/245. Use counts are 0/0. 239 circuits completed, 0 were unusable, 173 collapsed, and 178 timed out. For reference, your timeout cutoff is 60 seconds.
Feb 15 17:04:41 tuxzentrale tor[150854]: Feb 15 17:04:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Feb 15 17:04:41 tuxzentrale tor[150854]: Feb 15 17:04:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Feb 15 17:04:42 tuxzentrale tor[150854]: Feb 15 17:04:42.000 [warn] Guard Paphos ($B56B9FE93F83B4FA69234B17A060E8A8E7446D19) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 122/286. Use counts are 64/79. 275 circuits completed, 5 were unusable, 148 collapsed, and 167 timed out. For reference, your timeout cutoff is 60 seconds.
Feb 15 17:04:46 tuxzentrale tor[150854]: Feb 15 17:04:46.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Feb 15 17:04:46 tuxzentrale tor[150854]: Feb 15 17:04:46.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Feb 15 17:04:51 tuxzentrale tor[150854]: Feb 15 17:04:51.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Feb 15 17:04:51 tuxzentrale tor[150854]: Feb 15 17:04:51.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Feb 15 17:04:51 tuxzentrale tor[150854]: Feb 15 17:04:51.000 [warn] Guard Piratenpartei08 ($E8965A79FB2F335194141E8968755524840C44B6) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 56/190. Use counts are 2/2. 178 circuits completed, 0 were unusable, 122 collapsed, and 125 timed out. For reference, your timeout cutoff is 60 seconds.
Feb 15 17:04:52 tuxzentrale tor[150854]: Feb 15 17:04:52.000 [warn] Guard StayStrongRelay01 ($ED9A731373456FA071C12A3E63E2C8BEF0A6E721) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 55/235. Use counts are 6/6. 218 circuits completed, 0 were unusable, 163 collapsed, and 171 timed out. For reference, your timeout cutoff is 60 seconds.
</code>