Arch Linux

bartus

Member

Registered: 2013-05-13

Posts: 57

Systemd container stops working randomly (makechrootpkg)

Recently encounter a problem with systemd-nspawn when using makechrootpkg.
After the failed build chroot stops working all together and produces this error message:

Failed to attach 24858 to compat systemd cgroup /user.slice/user-1000.slice/session-c1.scope/payload: No such file or directory
Failed to attach 24836 to compat systemd cgroup /user.slice/user-1000.slice/session-c1.scope/supervisor: No such file or directory
Failed to chown() cgroup /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-c1.scope/payload: No such file or directory

I can recover from it by killing c1 session with loginctl kill-session c1.
I traced this issue to systemd-nspawn invocation in makechrootpkg and find out that removing --keep-unit flag seems to fix the issue for me.

Last edited by bartus (2018-05-19 17:52:15)

anatolik

Developer

Registered: 2012-09-27

Posts: 458

Re: Systemd container stops working randomly (makechrootpkg)

I use [testing] repo and confirm the same issue. Could you please file an Arch bug for easier progress tracking?

---

Read it before posting http://www.catb.org/esr/faqs/smart-questions.html
Ruby gems repository done right https://bbs.archlinux.org/viewtopic.php?id=182729
Fast initramfs generator with security in mind https://wiki.archlinux.org/index.php/Booster

bartus

Member

Registered: 2013-05-13

Posts: 57

Re: Systemd container stops working randomly (makechrootpkg)

Done. https://bugs.archlinux.org/task/58892
Also, the issue was mentioned on mailing list lately: #. Supposedly it affects only packages that have systemd in their dependencies. #

Last edited by bartus (2018-06-06 16:48:08)