[Dev] Unknown lvalue 'ControlGroup' in section 'Service'

Wu, Zhiwen zhiwen.wu at intel.com
Fri Dec 20 02:47:18 GMT 2013


Hi folks,
I created a minimal bootable image (just with sdb capability) from latest repos of devel:wayland:Mobile for our Intel reference device. And after boot-up and "sdb shell" to login the root user, I found the user-session at .service failed at booting. The related log from "journalctl" attached here:
==============================================================================================================
[/usr/lib/systemd/system/graphical.target.wants/../user-session at .service:15] Unknown lvalue 'ControlGroup' in section 'Service'
[/usr/lib/systemd/system/graphical.target.wants/../user-session at .service:16] Unknown lvalue 'ControlGroupModify' in section 'Service'
==============================================================================================================

If I remove the "ControlGroup" and "ControlGroupModify" entries from user-session at .service, I got these:
=======================================
Starting user-5000.slice.
Created slice user-5000.slice.
Starting User Manager for 5000...
Starting Session c1 of user app.
Started Session c1 of user app.
Failed to start Start the av system.
Unit avsystem.service entered failed state.
Started Generate environment from /etc/profile.d.
Starting user-5000.slice.
Created slice user-5000.slice.
Starting User Manager for 5000...
Starting Session c1 of user app.
Started Session c1 of user app.
pam_unix(login:session): session opened for user app by (uid=0)
Failed to create root cgroup hierarchy: Permission denied
Failed to create root cgroup hierarchy: Permission denied
Failed to allocate manager object: Permission denied
Failed to create root cgroup hierarchy: Permission denied
Failed to create root cgroup hierarchy: Permission denied
Failed to allocate manager object: Permission denied
Failed to allocate manager object: Permission denied
dbus[178]: [system] Rejected send message, 2 matched rules; type="method_call",
sender=":1.5" (uid=5000 pid=220 comm="(sd-pam)   ") interface="org.freedesktop.l
ogin1.Manager" member="ReleaseSession" error name="(unset)" requested_reply="0"
destination="org.freedesktop.login1" (uid=0 pid=180 comm="/usr/lib/systemd/syste
md-logind ")
[system] Rejected send message, 2 matched rules; type="method_call", sender=":1.
5" (uid=5000 pid=220 comm="(sd-pam)   ") interface="org.freedesktop.login1.Manag
er" member="ReleaseSession" error name="(unset)" requested_reply="0" destination
="org.freedesktop.login1" (uid=0 pid=180 comm="/usr/lib/systemd/systemd-logind "
)
pam_systemd(login:session): Failed to release session: Access denied
pam_unix(login:session): session closed for user app
Started User Manager for app.
Started User Manager for 5000.
Stopped Collect Read-Ahead Data.
Started Load Kernel Modules.
Mounted Configuration File System.
Started Set Up Additional Binary Formats.
Stopping Session c1 of user app.
Stopped Session c1 of user app.
=======================================

Version info:
tizen-mobile-session (provides user-session at .service) version: 1-3.1, commit number is 9e1de416dfc4c6e0a3ff110b70722b6e9cfef450, tag is submit/tizen/20131213.101720
systemd version: 208, commit number is 6b31acecb8f412f7843951e6f3bacc7d8b516f42, tag is submit/tizen/20131218.205849

I am not familiar with systemd mechanism, any comments and hints are appreciated.

Thanks







More information about the Dev mailing list