Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[Michael Biebl]

Am 04.06.2015 um 23:00 schrieb Michael Biebl:
> Am 04.06.2015 um 20:36 schrieb nusenu:
>> Package: systemd
>> Version: 215-17
>>
>> when using a multi-instance systemd service file with
>> ReadOnlyDirectories the service fails if it is attempted to start on a
>> Debian 8 system that has been upgraded from a previous release.
>>
>> Error message is:
>> Failed at step NAMESPACE spawning /usr/bin/tor: No such file or directory
>> service: main process exited, code=exited, status=226/NAMESPACE
>>
>> The same config works on a fresh Debian 8 installation.
> 
> Can you find out what is different between the upgraded and fresh Debian
> installation?
> Can you post the complete service file you are using, please?

Do you maybe have anything installed on your upgraded system which might
interfere with systemd, like cgmanager, lxc, cgroup-bin etc.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150604/f7d6105f/attachment-0002.sig>