[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #1888 [Tor Relay]: Some small problems with my relay



#1888: Some small problems with my relay
---------------------------+------------------------------------------------
 Reporter:  BahTheSheep    |        Type:  defect   
   Status:  new            |    Priority:  minor    
Milestone:                 |   Component:  Tor Relay
  Version:  Tor: 0.2.1.26  |    Keywords:           
   Parent:                 |  
---------------------------+------------------------------------------------

Comment(by BahTheSheep):

 I have restarted vidalia a couple a times and at a certain point I get
 this:
 sep 02 12:32:29.265 [Notice] Tor v0.2.1.26. This is experimental software.
 Do not rely on it for strong anonymity. (Running on Windows XP Service
 Pack 3 [workstation] {terminal services, single user})
 sep 02 12:32:29.265 [Notice] Initialized libevent version 1.4.12-stable
 using method win32. Good.
 sep 02 12:32:29.265 [Notice] Opening OR listener on 0.0.0.0:9001
 sep 02 12:32:29.265 [Notice] Opening Directory listener on 0.0.0.0:9030
 sep 02 12:32:29.375 [Notice] Opening Socks listener on 127.0.0.1:9050
 sep 02 12:32:29.375 [Notice] Opening Control listener on 127.0.0.1:9051
 sep 02 12:32:29.375 [Notice] Parsing GEOIP file.
 sep 02 12:33:18.203 [Notice] Self-testing indicates your ORPort is
 reachable from the outside. Excellent. Publishing server descriptor.
 sep 02 12:33:18.203 [Warning] router_orport_found_reachable(): Bug: ORPort
 found reachable, but I have no routerinfo yet. Failing to inform
 controller of success.
 sep 02 12:33:22.609 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
 sep 02 12:33:26.390 [Notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 sep 02 12:33:26.390 [Notice] Bootstrapped 100%: Done.
 sep 02 12:34:18.281 [Notice] Your DNS provider gave an answer for
 "b7inw6br3oivj.org", which is not supposed to exist.  Apparently they are
 hijacking DNS failures. Trying to correct for this.  We've noticed 1
 possibly bad address so far.
 sep 02 12:34:39.281 [Notice] Guessed our IP address as 80.56.78.10
 (source: 208.53.142.44).
 sep 02 12:35:58.187 [Notice] Self-testing indicates your DirPort is
 reachable from the outside. Excellent.
 sep 02 12:37:55.312 [Notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit 'torserversNet4'. Retrying on a new circuit.
 sep 02 12:37:55.328 [Notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit 'torserversNet4'. Retrying on a new circuit.
 sep 02 12:37:56.312 [Notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit 'torserversNet4'. Retrying on a new circuit.
 sep 02 12:38:04.187 [Notice] Self-testing indicates your ORPort is
 reachable from the outside. Excellent. Publishing server descriptor.
 sep 02 12:39:20.406 [Notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 sep 02 12:39:20.406 [Notice] Tried for 120 seconds to get a connection to
 [scrubbed]:443. Giving up. (waiting for circuit)
 sep 02 12:39:21.406 [Notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 sep 02 12:39:52.453 [Notice] Tried for 120 seconds to get a connection to
 [scrubbed]:443. Giving up. (waiting for circuit)
 sep 02 12:46:06.953 [Notice] Performing bandwidth self-test...done.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1888#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs