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 818168 - The /etc/init.d/bmc-watchdog script does not store PID in the PIDFILE
Summary: The /etc/init.d/bmc-watchdog script does not store PID in the PIDFILE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: freeipmi
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ales Ledvinka
QA Contact: Branislav Blaškovič
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-02 11:19 UTC by Petr MOTEJLEK
Modified: 2016-09-20 04:32 UTC (History)
4 users (show)

Fixed In Version: freeipmi-1.2.1-1
Doc Type: Bug Fix
Doc Text:
Cause: Neither the bmc-watchdog daemon nor it's startup script did write pid into the pidfile. Consequence: Tools that are still relying on the missing value did not work reliably. Fix: Rebase to version of freeipmi 1.2.1 added the write. Result: PID file contains the PID
Clone Of:
Environment:
Last Closed: 2013-11-21 11:57:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1640 0 normal SHIPPED_LIVE freeipmi bug fix and enhancement update 2013-11-20 21:53:36 UTC

Description Petr MOTEJLEK 2012-05-02 11:19:51 UTC 
Description of problem:

Although the /etc/init.d/bmc-watchdog script defines a variable named PIDFILE
which points to /var/run/bmc-watchdog.pid when executing the script with the start parameter, the PIDFILE does not even get created (nor does it contain the actual PID for that matter).

At http://pastebin.com/AMPdPgDP it is possible to see what I did to make the script store the PID (lines 44 and 45) inside the PIDFILE. I don't think this is the correct approach (as I would think that the daemon function that gets called fron the script should be responsible for storing the PID). Also I would like to point out that storing the PID is not possible using the bmc-watchdog utility by itself (it does not have any command-line option for storing the PID in a PIDFILE).

Version-Release number of selected component (if applicable):
freeipmi-bmc-watchdog.x86_64 0.7.16-3.el6
Comment 2 RHEL Program Management 2012-09-07 05:11:49 UTC 
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.
Comment 3 Petr MOTEJLEK 2012-09-12 19:20:46 UTC 
Hello Aleš,

As proposed in the message from the RHEL Product and Program Management I would like to have this feature scheduled to be released as soon as possible. Could you please look into this and take this request further down the road?

Thanks
Comment 4 Ales Ledvinka 2012-09-18 12:29:05 UTC 
Thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to  guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain  it receives the proper attention and prioritization to assure a timely resolution. 

For information on how to contact the Red Hat production support team, please visit:

https://www.redhat.com/support/process/production/#howto
Comment 7 errata-xmlrpc 2013-11-21 11:57:16 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-2013-1640.html
Note You need to log in before you can comment on or make changes to this bug.