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

[tor-bugs] Re: [Tor Bug Tracker] #1162: cant start a relay

To: undisclosed-recipients:;
Subject: [tor-bugs] Re: [Tor Bug Tracker] #1162: cant start a relay
From: "Tor Bug Tracker" <torproject-admin@xxxxxxxxxxxxxx>
Date: Fri, 14 May 2010 04:25:59 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivered-to: tor-bugs-outgoing@xxxxxxxx
Delivered-to: tor-bugs@xxxxxxxxxxxxxx
Delivery-date: Fri, 14 May 2010 00:26:31 -0400
In-reply-to: <046.89f38bd4125f4621adb54c271b0cb4f3@xxxxxxxxxxxxxx>
References: <046.89f38bd4125f4621adb54c271b0cb4f3@xxxxxxxxxxxxxx>
Reply-to: tor-assistants@xxxxxxxxxxxxxx
Sender: owner-tor-bugs@xxxxxxxxxxxxxx

#1162: cant start a relay
----------------------+-----------------------------------------------------
 Reporter:  tedted    |         Type:  defect        
   Status:  closed    |     Priority:  minor         
Milestone:            |    Component:  Tor-Tor client
  Version:  0.2.1.20  |   Resolution:  worksforme    
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by phobos):

  * status:  new => closed
  * resolution:  None => worksforme


Old description:

> Hello . I just tried your software. It works ok as long as I use it as a
> client but not if I try to relay : it crashes every time, it says tor as
> unexpedly exits.
> here the log :
> dÃc. 02 19:20:13.594 [Notice] Tor v0.2.1.20. This is experimental
> software. Do not rely on it for strong anonymity. (Running on Windows XP
> Service Pack 3 [workstation] {terminal services, single user})
> dÃc. 02 19:20:15.454 [Notice] Initialized libevent version 1.4.12-stable
> using method win32. Good.
> dÃc. 02 19:20:15.454 [Notice] Opening Socks listener on 127.0.0.1:9050
> dÃc. 02 19:20:15.454 [Notice] Opening Control listener on 127.0.0.1:9051
> dÃc. 02 19:20:28.766 [Notice] Parsing GEOIP file.
> dÃc. 02 19:20:28.766 [Notice] We now have enough directory information to
> build circuits.
> dÃc. 02 19:20:28.766 [Notice] Bootstrapped 80%: Connecting to the Tor
> network.
> dÃc. 02 19:20:28.766 [Notice] Bootstrapped 85%: Finishing handshake with
> first hop.
> dÃc. 02 19:20:28.766 [Notice] Bootstrapped 90%: Establishing a Tor
> circuit.
> dÃc. 02 19:20:28.766 [Notice] Tor has successfully opened a circuit.
> Looks like client functionality is working.
> dÃc. 02 19:20:28.766 [Notice] Bootstrapped 100%: Done.
> dÃc. 02 19:20:28.766 [Notice] Your ContactInfo config option is not set.
> Please consider setting it, so we can contact you if your server is
> misconfigured or something else goes wrong.
> dÃc. 02 19:20:28.766 [Notice] Opening OR listener on 0.0.0.0:443
> dÃc. 02 19:20:28.766 [Notice] Opening Directory listener on 0.0.0.0:9030
> dÃc. 02 19:20:28.766 [Notice] Your Tor server's identity key fingerprint
> is 'Unnamed AC09D7B124DE36F537AD17F586BF41C397F0B67F'
> dÃc. 02 19:20:28.766 [Error] libevent call with win32 failed: Socket
> operation on nonsocket [WSAENOTSOCK ] [10038]
>
> No matter what I try the last line always occur and crash the software.
> Im under xp sp3 pro.
>
> [Automatically added by flyspray2trac: Operating System: All]

New description:

 Hello . I just tried your software. It works ok as long as I use it as a
 client but not if I try to relay : it crashes every time, it says tor as
 unexpedly exits.
 here the log :
 dÃc. 02 19:20:13.594 [Notice] Tor v0.2.1.20. This is experimental
 software. Do not rely on it for strong anonymity. (Running on Windows XP
 Service Pack 3 [workstation] {terminal services, single user})
 dÃc. 02 19:20:15.454 [Notice] Initialized libevent version 1.4.12-stable
 using method win32. Good.
 dÃc. 02 19:20:15.454 [Notice] Opening Socks listener on 127.0.0.1:9050
 dÃc. 02 19:20:15.454 [Notice] Opening Control listener on 127.0.0.1:9051
 dÃc. 02 19:20:28.766 [Notice] Parsing GEOIP file.
 dÃc. 02 19:20:28.766 [Notice] We now have enough directory information to
 build circuits.
 dÃc. 02 19:20:28.766 [Notice] Bootstrapped 80%: Connecting to the Tor
 network.
 dÃc. 02 19:20:28.766 [Notice] Bootstrapped 85%: Finishing handshake with
 first hop.
 dÃc. 02 19:20:28.766 [Notice] Bootstrapped 90%: Establishing a Tor
 circuit.
 dÃc. 02 19:20:28.766 [Notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 dÃc. 02 19:20:28.766 [Notice] Bootstrapped 100%: Done.
 dÃc. 02 19:20:28.766 [Notice] Your ContactInfo config option is not set.
 Please consider setting it, so we can contact you if your server is
 misconfigured or something else goes wrong.
 dÃc. 02 19:20:28.766 [Notice] Opening OR listener on 0.0.0.0:443
 dÃc. 02 19:20:28.766 [Notice] Opening Directory listener on 0.0.0.0:9030
 dÃc. 02 19:20:28.766 [Notice] Your Tor server's identity key fingerprint
 is 'Unnamed AC09D7B124DE36F537AD17F586BF41C397F0B67F'
 dÃc. 02 19:20:28.766 [Error] libevent call with win32 failed: Socket
 operation on nonsocket [WSAENOTSOCK ] [10038]

 No matter what I try the last line always occur and crash the software.
 Im under xp sp3 pro.

 [Automatically added by flyspray2trac: Operating System: All]

--

Comment:

 can't recreate and user disappeared.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1162#comment:3>
Tor Bug Tracker <https://trac.torproject.org/>
The Tor Project: anonymity online

Prev by Author: [tor-bugs] Re: [Tor Bug Tracker] #1275: Maclike directories for Tor
Next by Author: [tor-bugs] Re: [Tor Bug Tracker] #881: stalled too much writing to 127.0.0.1
Previous by thread: [tor-bugs] Re: [Tor Bug Tracker] #1275: Maclike directories for Tor
Next by thread: [tor-bugs] Re: [Tor Bug Tracker] #881: stalled too much writing to 127.0.0.1
Index(es):
- Author
- Thread