[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-relays] Network Scan through Tor Exit Node (Port 80)
hi
I m having problem in running tor since last 1 week.
I am getting the following log.
Mar 08 14:17:17.950 [Notice] Initialized libevent version 1.4.14-stable using method win32. Good.
Mar 08 14:17:17.950 [Notice] Opening Socks listener on 127.0.0.1:9050
Mar 08 14:17:17.950 [Notice] Opening Control listener on 127.0.0.1:9051
Mar 08 14:17:17.950 [Notice] Parsing GEOIP file.
Mar 08 14:17:22.831 [Notice] No current certificate known for authority moria1; launching request.
Mar 08 14:17:22.831 [Notice] No current certificate known for authority tor26; launching request.
Mar 08 14:17:22.831 [Notice] No current certificate known for authority dizum; launching request.
Mar 08 14:17:22.831 [Notice] No current certificate known for authority ides; launching request.
Mar 08 14:17:22.831 [Notice] No current certificate known for authority gabelmoo; launching request.
Mar 08 14:17:22.832 [Notice] No current certificate known for authority dannenberg; launching request.
Mar 08 14:17:22.832 [Notice] No current certificate known for authority urras; launching request.
Mar 08 14:17:22.832 [Notice] No current certificate known for authority maatuska; launching request.
Mar
08 14:17:42.440 [Warning] Problem bootstrapping. Stuck at 10%:
Finishing handshake with directory server. (Socket is not connected
[WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
Mar 08 14:18:03.172 [Notice] Tor v0.2.1.30. This is experimental
software. Do not rely on it for strong anonymity. (Running on Very
recent version of Windows [major=6,minor=1] [workstation] {terminal
services, single user})
Mar 08 14:18:03.284 [Notice] Initialized libevent version 1.4.14-stable using method win32. Good.
Mar 08 14:18:03.285 [Notice] Opening Socks listener on 127.0.0.1:9050
Mar 08 14:18:03.285 [Notice] Opening Control listener on 127.0.0.1:9051
Mar 08 14:18:03.285 [Notice] Parsing GEOIP file.
Mar 08 14:18:08.857 [Notice] No current certificate known for authority moria1; launching request.
Mar 08 14:18:08.857 [Notice] No current certificate known for authority tor26; launching request.
Mar 08 14:18:08.857 [Notice] No current certificate known for authority dizum; launching request.
Mar 08 14:18:08.857 [Notice] No current certificate known for authority ides; launching request.
Mar 08 14:18:08.857 [Notice] No current certificate known for authority gabelmoo; launching request.
Mar 08 14:18:08.858 [Notice] No current certificate known for authority dannenberg; launching request.
Mar 08 14:18:08.858 [Notice] No current certificate known for authority urras; launching request.
Mar 08 14:18:08.862 [Notice] No current certificate known for authority maatuska; launching request.
Mar 08 14:18:29.841 [Warning] Problem bootstrapping. Stuck at 10%:
Finishing handshake with directory server. (Socket is not connected
[WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
Mar 08 14:20:09.428 [Notice] No current certificate known for authority moria1; launching request.
Mar 08 14:20:09.467 [Notice] No current certificate known for authority tor26; launching request.
Mar 08 14:20:09.472 [Notice] No current certificate known for authority dizum; launching request.
Mar 08 14:20:09.477 [Notice] No current certificate known for authority ides; launching request.
Mar 08 14:20:09.482 [Notice] No current certificate known for authority gabelmoo; launching request.
Mar 08 14:20:09.486 [Notice] No current certificate known for authority dannenberg; launching request.
Mar 08 14:20:09.491 [Notice] No current certificate known for authority urras; launching request.
Mar 08 14:20:09.496 [Notice] No current certificate known for authority maatuska; launching request.
Mar
08 14:20:30.430 [Warning] Problem bootstrapping. Stuck at 10%:
Finishing handshake with directory server. (Socket is not connected
[WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
Mar 08 14:22:26.329 [Notice] Application request when we're believed to
be offline. Optimistically trying directory fetches again.
Mar 08
14:22:59.733 [Notice] Application request when we're believed to be
offline. Optimistically trying directory fetches again.
Mar 08 14:23:20.734 [Warning] Problem bootstrapping. Stuck at 10%:
Finishing handshake with directory server. (Socket is not connected
[WSAENOTCONN ]; NOROUTE; count 6; recommendation warn)
Mar 08 14:24:26.465 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 08 14:24:59.467 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 08 14:26:15.483 [Notice] No current certificate known for authority moria1; launching request.
Mar 08 14:26:15.486 [Notice] No current certificate known for authority tor26; launching request.
Mar 08 14:26:15.492 [Notice] No current certificate known for authority dizum; launching request.
Mar 08 14:26:15.492 [Notice] No current certificate known for authority ides; launching request.
Mar 08 14:26:15.492 [Notice] No current certificate known for authority gabelmoo; launching request.
Mar 08 14:26:15.492 [Notice] No current certificate known for authority dannenberg; launching request.
Mar 08 14:26:15.493 [Notice] No current certificate known for authority urras; launching request.
Mar 08 14:26:15.493 [Notice] No current certificate known for authority maatuska; launching request.
Mar
08 14:26:36.486 [Warning] Problem bootstrapping. Stuck at 10%:
Finishing handshake with directory server. (Socket is not connected
[WSAENOTCONN ]; NOROUTE; count 10; recommendation warn)
I am using my university network.
My room mate is using the same network & it's working fine in his PC.
Please help.
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays