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

[tor-relays] problem with tor

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-relays] problem with tor
From: PRAFULL CHANDRA MOULEKHI <prafullmoulekhi90@xxxxxxxxx>
Date: Thu, 14 Apr 2011 20:17:21 +0530
Delivered-to: archiver@xxxxxxxx
Delivery-date: Thu, 14 Apr 2011 10:47:39 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=CgOtZO+j02OfY1XCff4oCVaCSsp4MLqqF796KYA78fM=; b=W2hEMCiaCMqHrGjeJAVp0imKiymP9vG1X3OfpcIVvn2rv3EB7VN5BM329Wx1S2dEHR VdFFw9G3GdQRaJzFpchby3IrsUGVegcyNMW5JIwl423e0u6ArRIRk1HHFF4wvH5Vl6mA SqBH6VvYAsDUx75D8PTQj58hIsawpuUfTff5A=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; b=oU/16nN6QXZVhHMoUhk736ozEpR1grhAGxKbLeDAls/+QWDzlJaXHExi97CI7jNnrv xxfCY6k67O70SJ4kavjHhO1OZo5ovvgCY84fu1cq/0k3SSUf5arHm34mlL6n+3rbzTjP +CixPn7LBGqu4wDa0ylpOMVopA8U7Zu/e8XQc=
In-reply-to: <BANLkTimO0WD6O1KTMmX5MDTc_JA6JZGp0Q@xxxxxxxxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-relays>
List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>
List-id: "This mailing list is for support and questions about running Tor relays \(exit, non-exit, bridge\)." <tor-relays.lists.torproject.org>
List-post: <mailto:tor-relays@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>
References: <mailman.5.1302696003.19816.tor-relays@xxxxxxxxxxxxxxxxxxxx> <BANLkTimO0WD6O1KTMmX5MDTc_JA6JZGp0Q@xxxxxxxxxxxxxx>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9

Hi my tor is not working since last 15 days.
I am tired off running it again & again.
7 its not working. It's showing  that "no certificate available"
The log is attached to with mail.

Please help.

Prafull

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)

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

References:
- Re: [tor-relays] tor-relays Digest, Vol 3, Issue 11
  - From: Gijs Peskens

Prev by Author: Re: [tor-relays] tor-relays Digest, Vol 3, Issue 9
Next by Author: Re: [tor-relays] two relays serving same hidden service
Previous by thread: Re: [tor-relays] tor-relays Digest, Vol 3, Issue 11
Next by thread: [tor-relays] Persistent XSS vulnerability in TorStatus
Index(es):
- Author
- Thread