Description of problem: It appears that there is some type of circular logging problem occurring with the rsyslog configuration of aeolus. When both of these are enabled (which is the default and in puppet): # setup relp server $ModLoad imrelp $InputRELPServerRun 20514 # setup relp client $ModLoad omrelp *.* :omrelp:localhost:20514;RSYSLOG_ForwardFormat The logs grow extremely rapidly, quickly filling up whatever filesystem the logs are on. When either one is commented out, the logs stop growing out of control, and return to a normal pace. Version-Release number of selected component (if applicable): [root@qeblade33 rsyslog.d]# rpm -qa | grep aeolus-configure aeolus-configure-2.3.0-0.20111110143552git219f023.fc15.noarch How reproducible: Consistently Steps to Reproduce: 1. Install aeolus-configure 2. Run aeolus-configure (any configuration will do) 3. Actual results: Logs growing rapidly Expected results: Log don't grow rapidly Additional info:
this seems to be filling up our / partitions .. making this blocker
commit dc6726982792e7026773a8a2f33d75bf3e47da74 Author: Jason Guiditta <jguiditt> Date: Fri Nov 11 16:49:13 2011 -0500 BZ 753273 - rsyslog configuration causes messages log to grow rapidly. https://bugzilla.redhat.com/show_bug.cgi?id=753273 There were a number of small things causing this: * We were logging relp output to localhost * We were logging it to messages instead of /var/log/aeolus.log * There was a syntax error * We were spinning up an input relp server on a port that we don't yet have an selinux policy for I fixed the main issues and commented all the enabling bits out. The user/admin really needs to put where to output, and they are unlikely to actually use the input module, but it is harmless to leave as an example.
Verified. Logs no longer grow out of control. relp is there but disabled. commit 9bdb7d01
removing bugs from ce-sprint from the tracker.. you can find these bugs by querying the "qa whiteboard" for ce-sprint-60
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/RHEA-2012-0586.html