https://bugzilla.wikimedia.org/show_bug.cgi?id=55709
--- Comment #6 from Tim Starling <[email protected]> --- 379 out of 391 apaches show the old config when you run "initctl show-config mw-cgroup", i.e. without the "stop on" trigger. This is apparently because upstart config changes only take effect after the job is stopped or restarted. The stop script of mw-cgroup will routinely fail since rmdir() fails with EBUSY if there are any tasks remaining in the cgroup. The cgdelete command can be used instead -- it attempts to move any tasks in the cgroup to the parent cgroup before executing the rmdir(). However, this is still prone to failure if new tasks are added to the cgroup while the cgdelete command is in progress: # cgdelete -r memory:mediawiki cgdelete: cannot remove group 'mediawiki': Device or resource busy cgclear, which is run from the stop script of the cgconfig upstart job, is also prone to failing for the same reason. This would not be a problem if cgconfig and mw-cgroup were started on boot and never touched again, but of course the cgroup-bin package has a prerm trigger which stops the cgconfig job, causing breakage on upgrade. Says mw1109: 2013-09-09 18:41:49 upgrade cgroup-bin 0.37.1-1ubuntu10 0.37.1-1ubuntu10.1 Per usual Debian convention, to fix a bug in cgrulesengd it is necessary to unmount and remount the entire cgroup filesystem. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
