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.

(This is related to bug 821723, which asked for ignoring the services' rate limit for systemctl invocations, but was closed as NOTABUG.)

Currently when "systemctl restart foo.service" fails due to the rate limit, a generic error message is printed:

  Job for foo.service failed. See 'systemctl status foo.service'
  and 'journalctl -xn' for details.

In http://lists.freedesktop.org/archives/systemd-devel/2012-September/006530.html Lennart suggested a more helpful error message should be shown:

"Starting foobar.service has been attempted too often too quickly, the
repeated start of the unit has been refused. To force a start please
invoke 'systemctl reset-failed foobar.service' followed by 'systemctl
start foobar.service' again."


Version-Release number of selected component (if applicable):
systemd-208-2.fc20.x86_64

How reproducible:
always

Steps to Reproduce:
1. for i in $(seq 1 10); do systemctl restart sshd; done
2.
3.

Actual results:
A generic error message.

Expected results:
A helpful error message that mentions the possibility of using "reset-failed".

http://cgit.freedesktop.org/systemd/systemd/commit/?id=d5cad22109749faffb7563e4b2a3a728486d47b5

https://github.com/lnykryn/systemd-rhel/commit/8946c35e525c2a14b12ed425f11af152e37d8583

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-2015-2092.html