Package: systemd Version: 221-1 Severity: normal Dear Maintainer,
I installed tor (The onion router) the other day and when i started it (either via /usr/sbin/service or systemctl) i went through this: $ sudo systemctl start tor.service Job for tor.service failed because the control process exited with error code. See "systemctl status tor.service" and "journalctl -xe" for details. $ systemctl status tor.service ● tor.service - Anonymizing overlay network for TCP Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since Sun 2015-07-12 01:47:54 CEST; 45s ago Process: 19035 ExecStartPre=/usr/bin/install -Z -m 02750 -o debian-tor -g debian-tor -d /var/run/tor (code=exited, status=226/NAMESPACE) $ sudo journalctl -xe [...] Jul 12 01:47:54 blade systemd[1]: Starting Anonymizing overlay network for TCP... -- Subject: Unit tor.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tor.service has begun starting up. Jul 12 01:47:54 blade systemd[19030]: tor.service: Failed at step NAMESPACE spawning /usr/bin/install: Too many levels of symbolic links -- Subject: Process /usr/bin/install could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The process /usr/bin/install could not be executed and failed. -- -- The error number returned by this process is 40. Jul 12 01:47:54 blade kernel: Chromium OS LSM: Mount path with symlinks prohibited - pid=19030 cmdline="(install) " Jul 12 01:47:54 blade systemd[1]: tor.service: Control process exited, code=exited status=226 Jul 12 01:47:54 blade systemd[1]: Failed to start Anonymizing overlay network for TCP. -- Subject: Unit tor.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tor.service has failed. -- -- The result is failed. Jul 12 01:47:54 blade systemd[1]: tor.service: Unit entered failed state. Jul 12 01:47:54 blade systemd[1]: tor.service: Failed with result 'exit-code'. Jul 12 01:47:54 blade systemd[1]: tor.service: Service hold-off time over, scheduling restart. [...] At first i thought it was a kernel issue (beware also that my kernel is a chrome os kernel, not the one shipped by Debian, if that matters). Anyways running the commands in the tor unit file by hand, one by one in a terminal, leads to a correct execution. The same renaming/removing the tor unit file and starting the service using the init file in /etc/init.d. After a quick jump on the #tor IRC channel we concluded that this may be an issue on the systemd side, and after reading something around the web we tried to tweak the Hardening section of the unit file. And indeed we found that ReadWriteDirectories is set to /var/run which on my system is a link to /run. Changing ReadWriteDirectories to /run and running 'systemctl daemon-reload' solved the issue and now the service is starting fine. Let me know if more infos are needed. Thanks. -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.8.11 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.113+nmu3 ii libacl1 2.2.52-2 ii libapparmor1 2.9.2-3 ii libaudit1 1:2.4.2-1 ii libblkid1 2.26.2-6 ii libc6 2.19-18 ii libcap2 1:2.24-9 ii libcap2-bin 1:2.24-9 ii libcryptsetup4 2:1.6.6-5 ii libgcc1 1:5.1.1-12 ii libgcrypt20 1.6.3-2 ii libkmod2 20-1 ii liblzma5 5.1.1alpha+20120614-2.1 ii libmount1 2.26.2-6 ii libpam0g 1.1.8-3.1 ii libseccomp2 2.2.1-2 ii libselinux1 2.3-2+b1 ii libsystemd0 221-1 ii mount 2.26.2-6 ii sysv-rc 2.88dsf-59.2 ii udev 221-1 ii util-linux 2.26.2-6 Versions of packages systemd recommends: ii dbus 1.8.18-1 ii libpam-systemd 221-1 Versions of packages systemd suggests: pn systemd-ui <none> -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
