On 2020-05-11 20:11, Darac Marjal wrote: > On 11/05/2020 08:40, Reco wrote: >> Hi. >> >> On Mon, May 11, 2020 at 09:33:59AM +0200, Dmitry Katsubo wrote: >> >>> root@debian:~ # systemctl status binfmt-support >>> * binfmt-support.service - Enable support for additional executable binary >>> formats >>> Loaded: loaded (/lib/systemd/system/binfmt-support.service; enabled; >>> vendor preset: enabled) >>> Active: failed (Result: exit-code) since Sun 2020-05-10 21:54:27 CEST; >>> 10h ago >>> Docs: man:update-binfmts(8) >>> Process: 353 ExecStart=/usr/sbin/update-binfmts --enable (code=exited, >>> status=2) >>> Main PID: 353 (code=exited, status=2) >>> >>> May 10 21:54:27 debian update-binfmts[353]: update-binfmts: unable to open >>> /var/lib/binfmts: No such file or directory >>> >>> Any help is appreciated. >> This should help your problem: >> >> mkdir /etc/systemd/system/binfmt-support.service.d >> >> cat > /etc/systemd/system/binfmt-support.service.d/override.conf << EOF >> [Unit] >> RequiresMountsFor=/var >> EOF > > As another alternative, one can run "systemctl edit > binfmt-support.service", which will create the intervening folders and > files for you, and reload the daemon if the editor exits with success.
Thanks for suggestion! I have tried the advise and it actually worked (I will keep an eye on that because one reboot may not be representative). I wonder nevertheless what is the problem with this specific unit? It has dependency on local-fs.target which in turn should mount /var. So what exactly went wrong? -- With best regards, Dmitry