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.
signature.asc
Description: OpenPGP digital signature
