Opened 8 years ago

Closed 7 years ago

Last modified 7 years ago

#4027 closed defect (user disappeared)

socket creation error on debian 6 x64

Reported by: krugar Owned by:
Priority: Medium Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version: Tor: 0.2.3.4-alpha
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

while the apt package for 0.2.2.33 from the squeeze repo works fine,
installing 0.2.3.4 from experimental-squeeze onto the same machine yields the following:

Sep 15 13:02:47.293 [notice] Tor v0.2.3.4-alpha (git-9986082fc4414b7d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Sep 15 13:02:47.293 [notice] Read configuration file "/etc/tor/torrc".
Sep 15 13:02:47.293 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good.
Sep 15 13:02:47.293 [notice] Opening OR listener on 0.0.0.0:9001
Sep 15 13:02:47.293 [warn] Socket creation failed.
Sep 15 13:02:47.293 [notice] Opening Directory listener on 0.0.0.0:9030
Sep 15 13:02:47.293 [warn] Socket creation failed.
Sep 15 13:02:47.293 [notice] Opening Control listener on 127.0.0.1:9051
Sep 15 13:02:47.293 [warn] Socket creation failed.
Sep 15 13:02:47.293 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Sep 15 13:02:47.293 [err] Reading config failed--see warnings above.

the machine in question is an up-to-date debian squeeze x64 VM running on a xen host. i'm currently strapped for time, hence no proper debugging on my part. the problem existed for the previous experimental version as well, so it wasnt the latest update that broke it

Child Tickets

Change History (7)

comment:1 Changed 8 years ago by nickm

I've pushed a quick patch that will make the "socket creation failed" message log the actual error that it's getting from the socket() call; that should help diagnose this.

Running under strace might also help, if you know how to do that: look for the places where tor calls socket() and gets an error.

comment:2 Changed 8 years ago by nickm

Milestone: Tor: 0.2.3.x-final
Priority: minornormal

comment:3 Changed 8 years ago by nickm

Status: newneeds_information

I need to know what the error message with the new code was, or what happens under strace() when socket() fails. Otherwise I can't do anything here.

comment:4 Changed 7 years ago by nickm

Ping? Did this ever happen again once I added the improved log message? I can't fix it without more info.

comment:5 Changed 7 years ago by nickm

Resolution: user disappeared
Status: needs_informationclosed

Please comment and/or reopen if you can help track this down with the information I asked for, or if you see this error message again with a recent 0.2.3.x Tor.

comment:6 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:7 Changed 7 years ago by nickm

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