Hello,
I just had a tor instance exit with these error messages:
[warn] Failed to parse/validate config: Failed to bind one of the listener ports. [err] Reading config failed--see warnings above. For usage, try -h. [warn] Restart failed (config error?). Exiting.
Above that, the log contains an endless stream of these errors:
[warn] Permissions on directory /var/run/tor are too permissive. [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 connect to it, so Tor is being careful.)
When I checked, the /var/run/tor directory had the mode "rwxr-sr-x". After removing the permissions for "other", tor started without problems.
Did anyone else see this? I'm using Ubuntu packages from the deb.torproject.org repository.
Best regards, Alexander
On Wed, 31 Aug 2016, Alexander Dietrich wrote:
Hello,
I just had a tor instance exit with these error messages:
[warn] Failed to parse/validate config: Failed to bind one of the listener ports. [err] Reading config failed--see warnings above. For usage, try -h. [warn] Restart failed (config error?). Exiting.
Above that, the log contains an endless stream of these errors:
[warn] Permissions on directory /var/run/tor are too permissive. [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 connect to it, so Tor is being careful.)
When I checked, the /var/run/tor directory had the mode "rwxr-sr-x". After removing the permissions for "other", tor started without problems.
This most likely means that you have a non-standard control socket configuration. The package should have this:
/usr/share/tor/tor-service-defaults-torrc:ControlSocket /var/run/tor/control GroupWritable RelaxDirModeCheck /usr/share/tor/tor-service-defaults-torrc:ControlSocketsGroupWritable 1
Did you set ControlSocket elsewhere?
On 2016-08-31 14:33, Peter Palfrader wrote:
On Wed, 31 Aug 2016, Alexander Dietrich wrote:
When I checked, the /var/run/tor directory had the mode "rwxr-sr-x". After removing the permissions for "other", tor started without problems.
This most likely means that you have a non-standard control socket configuration. The package should have this:
You're right, my torrc also had a ControlSocket line, only without the additional arguments.
Thanks, Alexander
tor-relays@lists.torproject.org
-
Alexander Dietrich -
Peter Palfrader