Red Hat Bugzilla – Bug 753273
rsyslog configuration causes messages log to grow rapidly
Last modified: 2012-05-15 16:43:47 EDT
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
# setup relp client
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
Steps to Reproduce:
1. Install aeolus-configure
2. Run aeolus-configure (any configuration will do)
Logs growing rapidly
Log don't grow rapidly
this seems to be filling up our / partitions .. making this blocker
Author: Jason Guiditta <email@example.com>
Date: Fri Nov 11 16:49:13 2011 -0500
BZ 753273 - rsyslog configuration causes messages log to grow rapidly.
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
Logs no longer grow out of control. relp is there but disabled.
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.