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.
Description of problem:
This is a *VERY MINOR* output formatting issue. When running "service sblim-sfcb status|start|stop" the newlines are suppressed in the output. This causes the output to display incorrectly.
Version-Release number of selected component (if applicable):
sblim-sfcb-1.3.11-2.el6.i686
How reproducible:
Run: service sblim status
Steps to Reproduce:
1.
2.
3.
Actual results:
[root@rhlinbox ~]# service sblim-sfcb status
sfcb (11636 11629) is running[root@rhlinbox ~]#
[root@rhlinbox ~]# service sblim-sfcb start
[root@rhlinbox ~]# _ [ OK ]
Expected results:
[root@rhlinbox ~]# service sblim-sfcb status
sfcb (11636 11629) is running
[root@rhlinbox ~]#
[root@rhlinbox ~]# service sblim-sfcb start
Starting sblim-sfcb: [ OK ]
[root@rhlinbox ~]# _
Additional info:
Comment 2RHEL Program Management
2012-09-07 05:07:31 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 3Vitezslav Crhonek
2013-10-08 11:28:40 UTC
*** Bug 1016574 has been marked as a duplicate of this bug. ***
Comment 4RHEL Program Management
2013-10-14 00:45:25 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 6Vitezslav Crhonek
2016-10-03 12:26:35 UTC
I've also noticed that there is faulty check for "/var/run/tog-pegasus.pid" in "service sblim-sfcb status". If tog-pegasus is running and sblim-sfcb is stopped, then partially incorrect information is returned:
# service sblim-sfcb status
sfcb is not running, but pid file exists
Verified with sblim-sfcb-1.3.11-5.el6:
* all `service` messages are formatted properly,
* the status described in comment 6 does not mention PID file
anymore.
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.
https://rhn.redhat.com/errata/RHBA-2017-0648.html