Package: dante-server Version: 1.4.2+dfsg-6 Severity: important Dear Maintainer,
Systemd couldn't start danted service after I upgraded to buster from stretch (which itself was upgraded from the previous release). journalctl -xe showed following: Jul 16 07:31:39 s0 systemd[1]: Starting SOCKS (v4 and v5) proxy daemon (danted)... -- Subject: A start job for unit danted.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit danted.service has begun execution. -- -- The job identifier is 601246. Jul 16 07:31:39 s0 systemd[8289]: danted.service: Failed to set up mount namespacing: No such file or directory Jul 16 07:31:39 s0 systemd[8289]: danted.service: Failed at step NAMESPACE spawning /bin/sh: No such file or directory -- Subject: Process /bin/sh could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /bin/sh could not be executed and failed. -- -- The error number returned by this process is ERRNO. Jul 16 07:31:39 s0 systemd[1]: danted.service: Control process exited, code=exited, status=226/NAMESPACE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStartPre= process belonging to unit danted.service has exited. -- -- The process' exit code is 'exited' and its exit status is 226. Jul 16 07:31:39 s0 systemd[1]: danted.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit danted.service has entered the 'failed' state with result 'exit-code'. Jul 16 07:31:39 s0 systemd[1]: Failed to start SOCKS (v4 and v5) proxy daemon (danted). -- Subject: A start job for unit danted.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit danted.service has finished with a failure. -- -- The job identifier is 601246 and the job result is failed. After some research I found out that the problem is in following line of /lib/systemd/system/danted.service file: ReadOnlyDirectories=/bin /etc /lib /lib64 /sbin /usr /var Because my system doesn't have /lib64 directory. Changing /lib64 to -/lib64 in the service lets systemd start the deamon. But I'm not sure if /lib64 is optional directory on Debian in general or on some architectures or it should have been created during previous release upgrades or it's just me :-) -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (990, 'stable'), (100, 'testing') Architecture: armhf (armv7l) Foreign Architectures: i386 Kernel: Linux 4.9.182-mainline-rev1 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set$ Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dante-server depends on: ii init-system-helpers 1.56+nmu1 ii libc6 2.28-10 ii libpam0g 1.3.1-5 ii libwrap0 7.6.q-28 ii lsb-base 10.2019051400 dante-server recommends no packages. dante-server suggests no packages. -- Configuration Files: /etc/danted.conf changed [not included] -- no debconf information
