Bug 961844 - after reboot cgred does not confine/move users' processes into relevant target...
Summary: after reboot cgred does not confine/move users' processes into relevant targe...
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libcgroup
Version: 6.4
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Peter Schiffer
QA Contact: Red Hat Kernel QE team
Depends On:
TreeView+ depends on / blocked
Reported: 2013-05-10 14:22 UTC by lejeczek
Modified: 2014-11-21 15:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: cgred service was starting too early in the boot process Consequence: some services might avoid restriction if started before the cgred service Fix: lower boot priority of cgred service Result: all services should be restricted correctly by cgred. Please note, that solution of this problem might change in the future versions of libcgroup.
Clone Of:
Last Closed: 2013-11-21 22:33:37 UTC

Attachments (Terms of Use)
libcgroup-0.37-cgred-order.patch (527 bytes, patch)
2013-08-27 17:41 UTC, Peter Schiffer
no flags Details | Diff

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1685 normal SHIPPED_LIVE libcgroup bug fix and enhancement update 2013-11-20 21:52:29 UTC
Red Hat Knowledge Base (Solution) 1275263 None None None Never

Description lejeczek 2013-05-10 14:22:10 UTC
Description of problem:

.. but suffice to service cgred restart
and it behaves as intended/expected

so, each time system reboots and services start by init and users log in they are not being control
restart cgred and all it a ok
there in no indication in logs that something went wrong at system startup time

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 2 lejeczek 2013-05-13 14:05:47 UTC
problematic appears to be userdb backend (slapd in my case)
fix is to reorder init, eg:
mv ./rc.d/rc3.d/S14cgred ./rc.d/rc3.d/S28cgred

in other words make sure cgred starts afterwards

or fix is for developers of cgroups to change rationale and reflect it in the code or maybe it's just a minor change


Comment 3 Peter Schiffer 2013-08-27 17:41:04 UTC
Created attachment 791128 [details]

Comment 6 Mike Gahagan 2013-09-19 19:49:51 UTC
Confirmed we are now starting cgred later in the boot process so it should start after slapd and related ldap services. Verified using version libcgroup-0.40.rc1-3.el6

Comment 7 errata-xmlrpc 2013-11-21 22:33:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.