Opened 13 years ago

Last modified 7 years ago

#317 closed defect (Fixed)

Unable to setup Tor server

Reported by: Sk0ll Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: edmanm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I have run Tor server on Windows XP pro Sp2 (fully up to date) for many weeks without problems. But last week i update to
version 0.1.1.22 via Vidalia buddle (www.vidalia-project.net/dist/vidalia-bundle-0.1.1.22-0.0.7.exe) and now i can't setup
a Tor server.

First i got many warning messages :

août 02 21:17:31:312 [Notice] connection_create_listener(): Opening OR listener on 0.0.0.0:9001
août 02 21:17:31:312 [Notice] Your Tor server's identity key fingerprint is 'Ygdrasil 16C3 D04A A690 40EC 1DB2 F5D3 1555 0981 2D69 34D7'
août 02 21:17:31:312 [Notice] Now checking whether ORPort 82.65.94.25:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
août 02 21:17:31:312 [Warning] spawn_cpuworker(): Couldn't construct socketpair: No such file or directory
août 02 21:17:31:312 [Warning] spawn_enough_cpuworkers(): Spawn failed. Will try again later.
août 02 21:17:31:312 [Warning] spawn_dnsworker(): Couldn't construct socketpair: No such file or directory
août 02 21:17:31:312 [Warning] spawn_enough_dnsworkers(): Spawn failed. Will try again later.

etc

and the server is not reachable :

août 02 21:37:29:562 [Warning] second_elapsed_callback(): Your server (82.65.94.25:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
août 02 21:37:29:687 [Warning] second_elapsed_callback(): Your server (82.65.94.25:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

Now, when i restart my computer Tor crash with this message :

juil. 31 21:08:10:718 [Error] main.c:137: connection_add: Assertion conn->s >= 0 failed; aborting.

The bug is fully reproductible. Just trying again to setup a server ...

It looks like a socket creation failure, so i trying some registry hacks in TcpIp/Parameters .... unlucky.
The Tor client run well, but i feel more funny to contribute to the onion land with my own ;) So any idea
to workaround will be good.

Cheer

Richie

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (7)

comment:1 Changed 13 years ago by Sk0ll

Sorry, i forgot to paste a mail adress for any questions ... So here is : trashin.in_AT_free.fr (replace _AT_ by @)

Richie

comment:2 Changed 13 years ago by Sk0ll

I make the last update with the 0.1.1.23 Tor version and now the client crash :

août 05 20:04:31:093 [Notice] Tor v0.1.1.23. This is experimental software. Do not rely on it for strong anonymity.
août 05 20:04:31:640 [Notice] Initialized libevent version 1.1a+imweasel using method win32. Good.
août 05 20:04:31:640 [Notice] connection_create_listener(): Opening OR listener on 0.0.0.0:9001
août 05 20:04:31:859 [Notice] connection_create_listener(): Opening Socks listener on 127.0.0.1:9050
août 05 20:04:31:968 [Notice] connection_create_listener(): Opening Control listener on 127.0.0.1:9051
août 05 20:05:06:843 [Error] main.c:137: connection_add: Assertion conn->s >= 0 failed; aborting.

Richie

comment:3 Changed 13 years ago by Sk0ll

Last comment is a mistake ... It's vidalia faulty not updating the tor.rc file. I make it manually and the client work
well.

Richie

comment:4 Changed 13 years ago by edmanm

What update did you have to manually make to your torrc? I'm not sure I see how the triggered asserts or socketpair failures
are Vidalia's fault.

comment:5 Changed 13 years ago by phobos

Is this still a problem?

comment:6 Changed 12 years ago by phobos

flyspray2trac: bug closed.
Assuming fixed in current versions.

comment:7 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.