Bug 553219

Summary: rsyslogd SIGSEGVs on SIGHUP
Product: [Fedora] Fedora Reporter: Ales Kozumplik <akozumpl>
Component: rsyslogAssignee: Tomas Heinrich <theinric>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 13CC: akozumpl, bojan, jzeleny, pvrabec, theinric
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-06 12:36:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
rsyslog configuration for reproducing the bug none

Description Ales Kozumplik 2010-01-07 13:10:07 UTC
Created attachment 382221 [details]
rsyslog configuration for reproducing the bug

Steps to reproduce

1) copy the attached rsyslog.conf to the system's /etc
2) stop all rsyslogd instances on your system
3) start rsyslog daemon:
rsyslogd -c 4
4) send it a SIGHUP

Result:
rsyslogd crashes (running it in debug mode reveals a SIGSEGV during the restart phase)

Comment 1 Bug Zapper 2010-03-15 13:46:41 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2011-06-02 16:58:36 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Ales Kozumplik 2011-06-03 08:31:08 UTC
I can not tell if this thing still happens at the rawhide versions, I have not tried in  a while

Comment 4 Tomas Heinrich 2011-06-06 12:36:47 UTC
Should be fixed upstream since rsyslog 4.6.3.