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:
When attempted to remove non-existing crash dir I got:
# abrt-cli rm sdfsdf
'sdfsdf' does not exist
Can't connect to '/var/run/abrt/abrt.socket': Connection refused
I find the last line confusing, the last-but-one alone should be OK.
Version-Release number of selected component (if applicable):
abrt-2.0.8-1.el6.x86_64
libreport-2.0.9-1.el6.x86_64
How reproducible:
always
The message appears only if the daemon is stopped, so I think it's not so critical, but fixing it might break things -> proposing for 6.4
Comment 6RHEL Program Management
2012-07-10 08:32:09 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 7RHEL Program Management
2012-07-10 23:02:51 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.
Fix has been verified on abrt-2.0.8-9.el6, libreport-2.0.9-11 packages versions.
No confusing "...Connection refused" messages are shown during crash dir removal.
# rpm -q abrt
abrt-2.0.8-9.el6
# rpm -q libreport
libreport-2.0.9-11.el6
# service abrtd status
abrtd is stopped
# abrt-cli rm somedir
'somedir' does not exist
#
Cause
Confusing error message appeared when trying to remove non existing problem directory
Consequence
Confused user
Fix
Don't show the "Connection refused" message when trying to delete non existing problem
Result
Only message about non existing directory is shown, so user is not confused by this message
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