Hide Forgot
Description of problem: This is different bug from 637959, although symptoms are the same. Workaround is to move $InputTCPServerRun 6514 behind other directives. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: Following /etc/rsyslog.conf seems to be enough to reproduce the bug $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat $ModLoad imuxsock.so $ModLoad imklog.so $ModLoad imtcp $InputTCPServerRun 6514 $DefaultNetstreamDriver gtls *.* /var/log/messages 1. service rsyslog start 2. top Actual results: rsyslog eats memory and CPU is 100% Additional info: also described here http://bugzilla.adiscon.com/show_bug.cgi?id=194#c22 and probably also https://bugzilla.redhat.com/show_bug.cgi?id=637959#c24
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux.
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.