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 820475 - "abrt-ccpp status" returned no status messages
Summary: "abrt-ccpp status" returned no status messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: abrt
Version: 6.3
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Denys Vlasenko
QA Contact: Iveta Wiedermann
URL:
Whiteboard:
: 854623 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-10 05:52 UTC by masanari iida
Modified: 2013-02-21 07:53 UTC (History)
9 users (show)

Fixed In Version: abrt-2.0.8-7.el6
Doc Type: Bug Fix
Doc Text:
Cause: No status messages was emitted from the abrt-ccpp init script Consequence: Running command $ service abrt-ccpp status didn't show any message, so user can't check the status of the service Fix: Add code which emits message describing the current status of the service. Result: The output of the command $ service abrt-ccpp status is now: [root@localhost ~]# service abrt-ccpp status abrt-ccpp hook is installed [root@localhost ~]# service abrt-ccpp stop [root@localhost ~]# service abrt-ccpp status abrt-ccpp hook is not installed
Clone Of:
Environment:
Last Closed: 2013-02-21 07:53:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0290 0 normal SHIPPED_LIVE abrt, libreport and btparser bug fix and enhancement update 2013-02-20 20:55:47 UTC

Description masanari iida 2012-05-10 05:52:23 UTC
Description of problem:
/etc/init.d/abrt-ccpp status returns nothing because
of verbose=false setting in /usr/sbin/abrt-install-ccpp-hook.


Version-Release number of selected component (if applicable):
abrt-2.0.8-4.el6 (from RHEL6.3 beta)
abrt-addon-ccpp-2.0.8-4.el6. (from RHEL6.3 beta)

How reproducible:
Always


Steps to Reproduce:
1. Install RHEL6.3 beta
2. Login to the system with root user
3. Check abrtd is running  ( ps ax |grep abrt) 
   This one is auto starting while booting the OS.
4. Manually start abrt-ccpp ( # /etc/init.d/abrt-ccpp start)
5. Manually check abrt-ccpp is running or not. (# /etc/init.d/abrt-ccpp status)
  
Actual results:
It returns nothing.

Expected results:
Some messages which indicates abrt-ccpp is working or not should be display.

Additional info:
After modify verbose=false to true in /usr/sbin/abrt-install-ccpp-hook,
either "Installed" or "Not installed" are display.

From user's point of view, I wanted to checkout what kind of process is running 
for abrt-ccpp servoce , and try " ps ax |grep abrt" but I couldn't find 
the "abrt-ccpp" daemon. And "abrt-ccpp status" returns nothing. 
This is very confused. 
Then I followed the script and learned that the script "installed" the hook,
instead of starting some daemon.

I hope this is documented somewhere (ex. Update Deployment Guide or KB.)
If we can find the good documentation, I don't request to modify the default
setting. (And ask the customer to read the manual before making a question.)

Business impact: None

Comment 2 RHEL Program Management 2012-05-14 04:04:33 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2012-07-10 08:32:05 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2012-07-10 23:03:16 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 6 Denys Vlasenko 2012-07-29 20:20:37 UTC
Fixed in git:

commit da9a95a08fa6f4d566101ebbe2bc457dfc4ea0f2
Author: Denys Vlasenko <vda.linux>
Date:   Sun Jul 29 22:19:29 2012 +0200

    Make "abrt-ccpp status" tell user whether hook is currently installed

Comment 9 Jakub Filak 2012-09-05 14:13:32 UTC
*** Bug 854623 has been marked as a duplicate of this bug. ***

Comment 13 errata-xmlrpc 2013-02-21 07:53: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-2013-0290.html


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