FS#54746 - [systemd] message - "Cgroup: Remount Is Not Allowed" on shutdown/reboot

Attached to Project: Arch Linux
Opened by Peter Weber (hoschi) - Sunday, 09 July 2017, 14:00 GMT
Last edited by Dave Reisner (falconindy) - Monday, 17 July 2017, 12:03 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:
Hello!
The message "Cgroup: Remount Is Not Allowed" appears on the terminal during shutdown and reboot. It seems not releated to a change in configuration through users or the kernel. Probably a false positive? If yes, it worries and panics users unnecessarily.


Additional info:
* package version(s): >= 233.75-3
* config and/or log files etc.: log from journalctrl -b, doesn't include this message


Steps to reproduce:
1. reboot with "systemctl reboot"

Thank you

Related:
https://bbs.archlinux.org/viewtopic.php?id=227974
   systemd_log.txt (122.9 KiB)
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 17 July 2017, 12:03 GMT
Reason for closing:  Upstream
Comment by Peter Weber (hoschi) - Sunday, 09 July 2017, 14:08 GMT
To make it clear, it don't actively use CGROUPS on this system.
Comment by Dave Reisner (falconindy) - Sunday, 09 July 2017, 15:52 GMT
This causes precisely zero problems, and it's certainly not a packaging issue...

> To make it clear, it don't actively use CGROUPS on this system.
Well, you use systemd, so you're using cgroups.
Comment by Peter Weber (hoschi) - Sunday, 09 July 2017, 16:09 GMT
Thanks Dave, so you confirmed my assumption and I will test my luck with Lennart upstream :)
Comment by Peter Weber (hoschi) - Sunday, 09 July 2017, 20:25 GMT
https://github.com/systemd/systemd/issues/6314
Comment by Peter Weber (hoschi) - Thursday, 13 July 2017, 13:50 GMT
Upstream think this is probably caused by downstream e.g. initramfs or shutdown
https://github.com/systemd/systemd/issues/6314#issuecomment-314482026

Maybe a already existing misbehaviour caused this?

Please note, the message printed by the kernel will change with 4.13
Comment by Alif (alive4ever) - Thursday, 13 July 2017, 15:12 GMT
I managed to solve my cgroup related problem by adding systemd.legacy_systemd_cgroup_controller to the boot parameter [1].

After adding the boot flag, systemd-run --user --scope is working and I don't see "cgroup: remount is not allowed" shutdown message anymore.

It seems that default cgroup hierarchy needs to be specified during systemd compile time to prevent this type of problem. This implies `legacy` cgroup instead of `unified`.

[1] https://bbs.archlinux.org/viewtopic.php?id=227953

Loading...