Your message dated Fri, 23 Sep 2011 07:06:01 +0700
with message-id <[email protected]>
and subject line Re: Bug#642325: [tor] /etc/init.d/tor refuses to start,
complaining about /var/run/tor directory
has caused the Debian Bug report #642325,
regarding [tor] /etc/init.d/tor refuses to start, complaining about
/var/run/tor directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
642325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642325
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tor
Version: 0.2.2.32-1
Severity: normal
"# invoke-rc.d tor start" command refuses to start tor, complaining about wrong
permissions of /var/run/tor directory:
"the directory "/var/run/tor" needs to exist, and to be accessible only by the
user and group account that is running Tor."
I should notice, that no such directory existed before, so I created it and
assigned needed permissions. Before that tor was complaining about missing
directory.
So, now
$ ls -ld /var/run/tor
drwxrwx--- 2 debian-tor debian-tor 40 Sep 20 20:51 /var/run/tor
But if I do
# invoke-rc.d tor start
it fails:
Raising maximum number of filedescriptors (ulimit -n) to 32768.
Starting tor daemon: tor...
Sep 21 22:13:49.495 [notice] Tor v0.2.2.32 (git-84a279ff87e5bfea). This is
experimental software. Do not rely on it for strong anonymity. (Running on
Linux x86_64)
Sep 21 22:13:49.497 [notice] Initialized libevent version 1.4.14b-stable using
method epoll. Good.
Sep 21 22:13:49.497 [notice] Opening Socks listener on 127.0.0.1:9050
Sep 21 22:13:49.497 [warn] Permissions on directory /var/run/tor are too
permissive.
Sep 21 22:13:49.498 [warn] 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 and group account that is running Tor. (On some
Unix systems, anybody who can list a socket can conect to it, so Tor is being
careful.)
Sep 21 22:13:49.498 [notice] Closing partially-constructed listener Socks
listener on 127.0.0.1:9050
Sep 21 22:13:49.498 [warn] Failed to parse/validate config: Failed to bind one
of the listener ports.
Sep 21 22:13:49.498 [err] Reading config failed--see warnings above.
invoke-rc.d: initscript tor, action "start" failed.
--- 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.8) | 2.13-18
libevent-1.4-2 (>= 1.4.14b-stable) | 1.4.14b-stable-1
libssl1.0.0 (>= 1.0.0) | 1.0.0d-3
zlib1g (>= 1:1.1.4) | 1:1.2.3.4.dfsg-3
adduser | 3.113
Recommends (Version) | Installed
==========================-+-===========
polipo (>= 1) | 1.0.4.1-1.1
OR privoxy |
socat | 1.7.1.3-1.1
logrotate | 3.7.8-6
tor-geoipdb | 0.2.2.32-1
torsocks | 1.1+git20110826-1
OR tsocks | 1.8beta5-9.1
Suggests (Version) | Installed
================================-+-===========
mixmaster |
xul-ext-torbutton | 1.4.1-1
--- End Message ---
--- Begin Message ---
> Ok, that script looks like it creates /var/run/tor - what happens when
> you remove the one you created and try to run the init script?
All is fine now. Thanks. Tor still complains about wrong permissions of
/var/run/tor directory when started by vidalia under regular user,
but that is completely different issue, I guess:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642223
--- End Message ---
