Currently, there is a minor bug whereby if upstart is running in debug mode and trying to start a job that uses the 'cgroup' stanza will dump cgroup debug details into the jobs log [1].
This could be useful here though since it should be possible to either boot the session init in debug mode and see what turns up in ~/.cache/upstart/*.log. I've attached a patch to enable debug mode at session init startup but you can always enable at any time using 'initctl log-priority debug'.
It would also be worth enabling debug mode for cgmanager by tweaking /etc/init/cgmanager.conf and setting 'cgmanager_opts="--debug"' in that file as shown (or simply creating /etc/init/cgmanager.override containing 'env cgmanager_opts="--debug"'.
Currently, there is a minor bug whereby if upstart is running in debug mode and trying to start a job that uses the 'cgroup' stanza will dump cgroup debug details into the jobs log [1].
This could be useful here though since it should be possible to either boot the session init in debug mode and see what turns up in ~/.cache/ upstart/ *.log. I've attached a patch to enable debug mode at session init startup but you can always enable at any time using 'initctl log-priority debug'.
It would also be worth enabling debug mode for cgmanager by tweaking /etc/init/ cgmanager. conf and setting 'cgmanager_ opts="- -debug" ' in that file as shown (or simply creating /etc/init/ cgmanager. override containing 'env cgmanager_ opts="- -debug" '.
[1] - MP to resolve this is: https:/ /code.launchpad .net/~jamesodhu nt/upstart/ make-cgroups- quiet-in- debug-mode/ +merge/ 230762