unity-api-bugs team mailing list archive

[James Hunt <1357252@xxxxxxxxxxxxxxxxxx>]

The 'may not create under /run/cgmanager/fs/freezer' errors are caused
by the client (session init) cgmanager request "falling through"
may_access() in cgmanager.

Here's some debug first from upstart attempting to start a cgroup job by
first creating the cgroup:

init:cgroup_create:1172: cgmanager_create_sync(controller='freezer',
path='upstart/cgroup-ted-ted') returned -1

This operation failed. Details from the cgmanager server for the
cgmanager_create_sync() request:

do_create_main: do_create_main:263: controller='freezer', cgroup='upstart/cgroup-ted-ted', ucred p=(pid=1426, uid=0, gid=0), ucred r=(pid=3786, uid=32011, gid=32011)
do_create_main: do_create_main:315: r.pid=3786, r.uid=32011, r.gid=32011, dirpath='/run/cgmanager/fs/freezer'
may_access: may_access:925: uid=32011, gid=32011, path='/run/cgmanager/fs/freezer', mode=2
may_access: may_access:933
may_access: may_access:939
may_access: may_access:951
may_access: may_access:963
may_access: may_access:975
may_access: may_access:980
may_access: may_access:985
may_access: may_access:990
cgmanager:do_create_main: pid 3786 (uid 32011 gid 32011) may not create under /run/cgmanager/fs/freezer

-- 
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Ubuntu Application Launcher.
https://bugs.launchpad.net/bugs/1357252

Title:
  Upstart jobs specifying cgroup fail to start occasionally

Status in Ubuntu Application Launcher:
  Incomplete
Status in Upstart:
  New
Status in “cgmanager” package in Ubuntu:
  Confirmed

Bug description:
  After the ubuntu-app-launch landing in #188
  (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI
  Toolkit autopilot tests have started failing, see
  http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/
  and the #188 results too. It's different tests each time, but a bit
  above 10 of them tend to fail on each full run.

  Reproducable locally, where I got 11 such failures.

  To reproduce:
  [terminal 1]
  1. flash/update device if needed
  2. adb shell
  3. apt install ubuntu-ui-toolkit-autopilot
  4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown
  [terminal 2]
  5. phablet-config autopilot --dbus-probe enable # wait until finishes
  6. phablet-test-run ubuntuuitoolkit

  A full test suite run will take around 0.5h and should produce a bunch
  of 'Application failed to start.':s.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions