+++ This bug was initially created as a clone of Bug #537731 +++ Description of problem: Running service rsyslog start | cat starts up rsyslogd successfully but then hangs forever. Apparently rsyslogd messes up some part of the double-fork dance that all daemons are supposed to perform. Version-Release number of selected component (if applicable): 3.22.1-1.fc11 How reproducible: Every time. --- Additional comment from tps on 2010-02-12 10:26:26 EST --- same here: service rsyslog start | cat hangs for a long time or forever. Makes systems stop responding while booting up after syslogd start. Found it on Fedora-rawhide, rsyslog-4.4.2-5.fc13.i686. Since this is new since Feb, 10th 2010 and it was some time ago there for rsyslog-3.22.1-1.fc11 I suppose it is a regression. --- Additional comment from werner.no on 2010-04-23 07:37:44 EDT --- We have also noticed this. It seems like rsyslog doesn't close it's stderr and stdout properly. Any ETA for a fix? :)
Created attachment 475972 [details] Patch from later version (4.2.1) of rsyslog A fix to this issue was referenced in Bug 136141 - see <http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=6511278082a7e1e9602385cd24cdb5e363cb702f> The patch attached here is just a re-diff against the RHEL5 3.22.1 source
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.
*** Bug 719906 has been marked as a duplicate of this bug. ***
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The previous version of rsyslog didn't close stdout and stderr properly when running in background mode. This caused the OS to hang at boot. The outputs are now closed properly which resolves this issue.
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-2012-0228.html
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,4 @@ -The previous version of rsyslog didn't close stdout and stderr properly when running in background mode. This caused the OS to hang at boot. The outputs are now closed properly which resolves this issue.+The previous version of rsyslog didn't close stdout and stderr +properly when running in background mode. This caused the OS to +hang at boot. The outputs are now closed properly which resolves +this issue.