Right so the bug her eis that your session-c2.scope was created without
giving you ownership of the directory and the tasks and cgroup.procs
files. Manually changing those permissions fixes it for me.
So this may actually be a regression in systemd itself.
--
You received this bug notification
Right so the bug her eis that your session-c2.scope was created without
giving you ownership of the directory and the tasks and cgroup.procs
files. Manually changing those permissions fixes it for me.
So this may actually be a regression in systemd itself.
--
You received this bug notification
** Package changed: lxc (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
** Changed in: systemd (Ubuntu)
Status: New = Confirmed
** Summary changed:
- lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid
requestUser
** Package changed: lxc (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
** Changed in: systemd (Ubuntu)
Status: New = Confirmed
** Summary changed:
- lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid
requestUser
I suppose the user container runs upstart (from the template), as that's
still the ubuntu vivid default. But I have a feeling it's not even
getting that far; when I start with --logfile /dev/stdout --logpriority
debug it all just seems to be early setup:
$ lxc-start -n v1 --logfile /dev/stdout
I suppose the user container runs upstart (from the template), as that's
still the ubuntu vivid default. But I have a feeling it's not even
getting that far; when I start with --logfile /dev/stdout --logpriority
debug it all just seems to be early setup:
$ lxc-start -n v1 --logfile /dev/stdout
The lxcsyslog.txt attachment might be worth a look though, there are
several cgmanager errors there. vivid-systemd is the name of my system
container (standard vivid plus apt install systemd-sysv).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The lxcsyslog.txt attachment might be worth a look though, there are
several cgmanager errors there. vivid-systemd is the name of my system
container (standard vivid plus apt install systemd-sysv).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
$ cat /proc/self/cgroup
10:blkio:/user.slice/user-1000.slice/session-c2.scope
9:memory:/user.slice/user-1000.slice/session-c2.scope
8:freezer:/user.slice/user-1000.slice/session-c2.scope
7:cpu,cpuacct:/user.slice/user-1000.slice/session-c2.scope
$ cat /proc/self/cgroup
10:blkio:/user.slice/user-1000.slice/session-c2.scope
9:memory:/user.slice/user-1000.slice/session-c2.scope
8:freezer:/user.slice/user-1000.slice/session-c2.scope
7:cpu,cpuacct:/user.slice/user-1000.slice/session-c2.scope
can you paste your /proc/self/cgroup and /var/log/upstart/cgmanager.log?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1413927
Title:
lxc_cgmanager_enter: 694 call to
can you paste your /proc/self/cgroup and /var/log/upstart/cgmanager.log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413927
Title:
lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync
12 matches
Mail list logo
