Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

2016-11-07 Thread Michael Biebl
Am 07.11.2016 um 16:36 schrieb Yuri D'Elia: > On Mon, Nov 07 2016, Michael Biebl wrote: >>> Kernel: Linux 3.4.112-kvm-i386-20161024 >> >> I suspect your kernel is too old and/or doesn't have all necessary >> features enabled. Have you checked > > As written, this is 3.4. > >> See

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

2016-11-07 Thread Martin Pitt
Hello Yuri, Yuri D'Elia [2016-11-07 16:10 +0100]: > Nov 7 15:26:03 e systemd[18963]: systemd-resolved.service: Failed at step > NAMESPACE spawning /bin/sh: Bad file descriptor As Michael said, your kernel is likely too old. I suspect one of the new hardening options in

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

2016-11-07 Thread Yuri D'Elia
On Mon, Nov 07 2016, Michael Biebl wrote: >> Kernel: Linux 3.4.112-kvm-i386-20161024 > > I suspect your kernel is too old and/or doesn't have all necessary > features enabled. Have you checked As written, this is 3.4. > See /usr/share/doc/systemd/README.gz > It explicitly mentions 3.12 as

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

2016-11-07 Thread Yuri D'Elia
Package: systemd Version: 232-1 Severity: serious Upgrading systemd from 231-10 to either 232-1 or 232-2 breaks systemd-resolved and dovecot on my system, with the following error when the units are started: Nov 7 15:26:03 e systemd[18963]: systemd-resolved.service: Failed at step NAMESPACE