Bug#642223: [vidalia] vidalia cannot start tor

September 20th, 2011 - 10:10 am ET by ras | Report spam
Package: vidalia
Version: 0.2.14-2
Severity: normal

Since one of the recent Debian Wheezy updates vidalia is unable to start tor.

[Warning] Directory /var/run/tor does not exist.
[Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.)
[Notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050
[Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
[Error] Reading config failed--see warnings above.

And after I did
# mkdir /var/run/tor
# chown root:debian-tor /var/run/tor
# chmod 770 /var/run/tor

[Warning] /var/run/tor is not owned by this user (username, 1000) but by root (0). Perhaps you are running Tor as the wrong user?
[Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.)
[Notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050
[Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
[Error] Reading config failed--see warnings above.

Modifying vidalia settings to use TCP connection instead of Unix domain socket did not help. This way tor process is starting, but it seems that vidalia is unable to communicate with it.

$ getent passwd | grep debian-tor
debian-tor:x:112:121::/var/lib/tor:/bin/bash

$ getent group | grep debian-tor
debian-tor:x:121:username



System information.
Architecture: amd64
Kernel: Linux 3.0.4-custom-1

Debian Release: wheezy/sid
500 testing ftp.de.debian.org

Package information.
Depends (Version) | Installed
-+-==libc6 (>= 2.7) | 2.13-18
libgcc1 (>= 1:4.1.1) | 1:4.6.1-4
libqt4-network (>= 4:4.5.3) | 4:4.7.3-5
libqt4-xml (>= 4:4.5.3) | 4:4.7.3-5
libqtcore4 (>= 4:4.7.0~beta1) | 4:4.7.3-5
libqtgui4 (>= 4:4.7.0~beta1) | 4:4.7.3-5
libstdc++6 (>= 4.1.1) | 4.6.1-4
debconf (>= 1.5.11) | 1.5.40
OR debconf-2.0 |
ucf | 3.0025+nmu2
adduser | 3.113
tor (>= 0.2.2.29-beta-1) | 0.2.2.32-1


Package's Recommends field is empty.

Suggests (Version) | Installed
=-+-=iceweasel-torbutton |







To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 4 repliesReplies Make a reply

Replies

#1 Dererk
September 20th, 2011 - 10:40 am ET | Report spam
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)

On 20/09/11 11:01, ras wrote:
Package: vidalia
Version: 0.2.14-2
Severity: normal

Since one of the recent Debian Wheezy updates vidalia is unable to start tor.

[Warning] Directory /var/run/tor does not exist.
[Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.)
[Notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050
[Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
[Error] Reading config failed--see warnings above.

And after I did
# mkdir /var/run/tor
# chown root:debian-tor /var/run/tor
# chmod 770 /var/run/tor



Hi Ras.

Do you have any custom configuration on torrc, specifically overriding
defaults daemon's user/group, socket ownership, or something related?
Would you mind attaching into this thread the output of this commands
(as root)?

# file /var/run
# df | grep /run

I'm almost sure you don't have to perform any actions like the ones you
mention on Tor's version 0.2.2.32, weasel (cc'ed here) may address this
more accurately.

At risk of bringing a diagnostic prematurely, this appears to be related
to some strange _non-default_ behaviour on Tor's side.



Cheers,

Dererk

BOFH excuse #119:
evil hackers from Serbia.








To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics