Red Hat Bugzilla – Bug 1016680
MSG: add hint about 'reset-failed' when systemctl start fails due to rate limit
Last modified: 2015-11-19 09:55:26 EST
(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):
Steps to Reproduce:
1. for i in $(seq 1 10); do systemctl restart sshd; done
A generic error message.
A helpful error message that mentions the possibility of using "reset-failed".
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.