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):
abrtd is not running, but I agree that the message is confusing
Just a note that I was able to remove (real) $crash_dir that time.
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
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.
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.
Author: Jiri Moskovcak <firstname.lastname@example.org>
Date: Mon Aug 6 16:43:23 2012 +0200
don't try to delete dump dir which doesn't exist rhbz#799909
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
# rpm -q libreport
# service abrtd status
abrtd is stopped
# abrt-cli rm somedir
'somedir' does not exist
Confusing error message appeared when trying to remove non existing problem directory
Don't show the "Connection refused" message when trying to delete non existing problem
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.