RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 698705 - rsyslog creates invalid subsys lock file
Summary: rsyslog creates invalid subsys lock file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rsyslog
Version: 6.2
Hardware: All
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Tomas Heinrich
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 650509
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-21 14:53 UTC by Tomas Heinrich
Modified: 2011-12-06 16:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 650509
Environment:
Last Closed: 2011-12-06 16:51:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1673 0 normal SHIPPED_LIVE rsyslog bug fix and enhancement update 2011-12-06 00:50:13 UTC

Description Tomas Heinrich 2011-04-21 14:53:37 UTC
Version-Release number of selected component (if applicable):
rsyslog-4.6.2-3.el6

+++ This bug was initially created as a clone of Bug #650509 +++

Description of problem:
rsyslog's initscript creates a lock file named rsyslogd. The initscript's name is rsyslog, and because these two don't match, rc will not run the stop action when shutting down the system.

Version-Release number of selected component (if applicable):
rsyslog-3.22.1-3.el5
rsyslog-4.4.2-6.fc13.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot with rsyslog enabled
2. Check /var/lock/subsys

Comment 3 Karel Srot 2011-08-16 15:43:15 UTC
Since lockfile is changed also /etc/init.d/rsyslog should be updated with:

rhstatus() {
        status -p "${PIDFILE}" -l $prog $prog
}

Comment 6 errata-xmlrpc 2011-12-06 16:51:39 UTC
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-2011-1673.html


Note You need to log in before you can comment on or make changes to this bug.