Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-09-16 18:25 EDT
1. Feature Overview:
Feature Id: [201246]
a. Name of Feature: servicelog package
b. Feature Description
The servicelog package is used to store events that require a service action to be taken. For
example, in the case of a fan failure, the location and part number of the failing fan would be
noted, as well as a pointer to the repair procedure. Servicelog handles administrator notification
and call homes, and allows for repairs to be logged, to provide a complete history of failures and
repair actions for a system.
2. Feature Details:
Sponsor: PPC
Architectures:
ppc64
Arch Specificity: Purely Common Code
Delivery Mechanism: Direct from community
Category: Power Servicability
Request Type: Package - New
d. Upstream Acceptance: Accepted
Sponsor Priority 2
f. Severity: Medium
IBM Confidential: no
Code Contribution: IBM code
g. Component Version Target: servicelog 0.3
3. Business Case
Servicelog provides a central location to track hardware/firmware failures and repairs. Other
logging methods (such as syslog) are insufficient because they do not allow for the listing of open
(unrepaired) failures, or for indicating that a failure has been repaired. It is used to store the
output of certain diagnostics on Power (provided by the ibm-ppc-diag package), and is the basis for
a self-healing strategy for Linux.
4. Primary contact at Red Hat:
John Jarvis
jjarvis
5. Primary contacts at Partner:
Project Management Contact:
Mike Wortman, wortman.com, 512-838-8582
Technical contact(s):
Michael Strosaker, strosake.com
IBM Manager:
Larry Kessler, lkessler.com
This request says 'arch specificity: purely common code'. However, from where this is filed, it's implied this is ppc64-specific.
Does this work on other arches? How does it fit into frameworks such as web-based management (openwsman or similar), and other hardware interfaces (such as OpenHPI)?
This is odd; to me, it appears like the (463284) request was meant to add the servicelog package, but somehow it got garbled and resulted in the addition of only libservicelog.
To clarify, libservicelog and servicelog work together to provide the event storage database, notifications, and repair functions. Ideally we want both to be present.
From where things currently stand, it seems we need to rebase libservicelog to 1.1.9, then add servicelog-1.1.7 since, at least as of the RHEL6-snapshot1 (from may 7, ftp3), it is not yet present.
Comment 11releng-rhel@redhat.com
2010-07-02 18:58:38 UTC
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.