Thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to  guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain  it receives the proper attention and prioritization to assure a timely resolution. 

For information on how to contact the Red Hat production support team, please visit:
      https://www.redhat.com/support/process/production/#howto

Hi Benjamin,

what exact version of libcgroup do you have? You can see the version with:
$ rpm -q libcgroup

If you have libcgroup-0.37-7.el6 please try to update to libcgroup-0.37-7.1.el6_4 version and reproduce the problem.

Thanks.

peter

Hi Peter,

Yes I am using the 6.4 version:

[benrose@bastion ~]$ rpm -q libcgroup
libcgroup-0.37-7.1.el6_4.x86_64

The upgrade from the 6.3 to the 6.4 package is what broke my config.

Thanks,
Ben

Thanks. If you try to downgrade the package to the RHEL-6.3 version, with the rest of the packages from RHEL-6.4, to you still see the problem?
# yum downgrade libcgroup-0.37-4.el6

Peter,

Downgrading to libcgroup-0.37-4.el6 does indeed fix the problem.

Ben

OK. You can use the old version as workaround for a while.
Also, could you attach the complete coredump so we can analyse the problem more deeply? Thanks.

Created attachment 703929 [details]
core dump

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Hi Benjamin,

could you try this test build and see whether it fixes the problem?

https://dl.dropbox.com/u/15321270/libcgroup-0.37-7.2.el6.x86_64.rpm
https://dl.dropbox.com/u/15321270/libcgroup-pam-0.37-7.2.el6.x86_64.rpm
https://dl.dropbox.com/u/15321270/libcgroup-devel-0.37-7.2.el6.x86_64.rpm
https://dl.dropbox.com/u/15321270/libcgroup-debuginfo-0.37-7.2.el6.x86_64.rpm

Thanks,

peter

Peter,

This appears to have fixed the segmentation fault, but now my /var/log/messages is overflowing with:

Mar  6 12:49:04 bastion CGRE[24168]: Warning: cannot write tid 24176 to /cgroup/cpu/system//tasks:No such process
Mar  6 12:49:04 bastion CGRE[24168]: Warning: cgroup_attach_task_pid failed: 50016
Mar  6 12:49:04 bastion CGRE[24168]: Warning: failed to apply the rule. Error was: 50016
Mar  6 12:49:04 bastion CGRE[24168]: Warning: cannot write tid 24180 to /cgroup/cpu/system//tasks:No such process
Mar  6 12:49:04 bastion CGRE[24168]: Warning: cgroup_attach_task_pid failed: 50016
Mar  6 12:49:04 bastion CGRE[24168]: Warning: failed to apply the rule. Error was: 50016
Mar  6 12:49:04 bastion CGRE[24168]: Warning: cannot write tid 24182 to /cgroup/cpu/system//tasks:No such process
Mar  6 12:49:04 bastion CGRE[24168]: Warning: cgroup_attach_task_pid failed: 50016
Mar  6 12:49:04 bastion CGRE[24168]: Warning: failed to apply the rule. Error was: 50016


Thanks,
Ben

Benjamin,

hm. This is enhanced logging system available in libcgroup since RHEL-6.4, but by default, only error messages should be logged. What contains your /etc/sysconfig/cgred.conf file?

peter

[root@bastion ~]# cat /etc/cgrules.conf 
@csstaff	cpu,blkio		csstaff/

@courseacct	cpu,memory,blkio	users/

@fac		cpu,memory,blkio	users/
@grad		cpu,memory,blkio	users/
@guest		cpu,memory,blkio	users/
@research	cpu,memory,blkio	users/
@ug		cpu,memory,blkio	users/
@office		cpu,memory,blkio	users/
@ug_alumni	cpu,memory,blkio	users/
@grad_alumni	cpu,memory,blkio	users/

*		cpu,blkio		system/






[root@bastion ~]# cat /etc/cgconfig.conf 
# See man cgconfig.conf for further details.
#
# By default, mount all controllers to /cgroup/<controller>

mount {
	cpuset	= /cgroup/cpuset;
	cpu	= /cgroup/cpu;
	cpuacct	= /cgroup/cpuacct;
	memory	= /cgroup/memory;
	devices	= /cgroup/devices;
	freezer	= /cgroup/freezer;
	net_cls	= /cgroup/net_cls;
	blkio	= /cgroup/blkio;
}

group . {
	perm {
		task {
			uid = root;
			gid = root;
		}
		admin {
			uid = root;
			gid = root;
		}
	}
	cpu {
	}
	blkio {
	}
}

group csstaff {
	cpu {
		cpu.shares = 20;
	}
	blkio {
		blkio.weight = 1000;
	}
}

group users {
	cpu {
		cpu.shares = 60;
	}
	memory {
		memory.limit_in_bytes = 40454789530;
		memory.memsw.limit_in_bytes = 40454789530;
	}
	blkio {
		blkio.weight = 100;
	}
}

group system {
	cpu {
		cpu.shares = 20;
	}
	blkio {
		blkio.weight = 1000;
	}
}

Sincere apologies, here is the file you actually asked for:

[root@bastion ~]# cat /etc/sysconfig/cgred.conf 
# /etc/sysconfig/cgred.conf - CGroup Rules Engine Daemon configuration file
# 
# The four options listed below (CONFIG_FILE, LOG_FILE, NODAEMON, LOG) are
# the only valid ones.  Defining anything else in this file will cause the
# CGroup Rules Engine program to fail.  So, don't do it.

# The pathname to the configuration file for CGroup Rules Engine
CONFIG_FILE="/etc/cgrules.conf"

# Uncomment the following line to log to specified file instead of syslog
#LOG_FILE="/var/log/cgrulesengd.log"

# Uncomment the second line to run CGroup Rules Engine in non-daemon mode
NODAEMON=""
#NODAEMON="--nodaemon"

# Set owner of cgred socket. 'cgexec' tool should have write access there
# (either using suid and/or sgid permissions or Linux capabilities).
SOCKET_USER=""
SOCKET_GROUP="cgred"

# Uncomment the second line to disable logging for CGroup Rules Engine
# Uncomment the third line to enable more verbose logging.
LOG=""
#LOG="--nolog"
#LOG="-v"

Hi Benjamin,

thanks. I'm sorry, I've lied to you. cgrulesengd has it's own default logging level which is WARNING and more severe messages. You can make it quieter by setting:
LOG="-q"
in /etc/sysconfig/cgred.conf file.

I'll think about how to unify this updated logging.

Thanks for bringing this up.

peter

Reproduced in libcgroup-0.37-7.el6.x86_64 and verified in 
libcgroup-0.37-10.el6.x86_64.

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.

http://rhn.redhat.com/errata/RHBA-2013-1685.html