Error message
In the message, %s marks a value that the engine fills in when it raises the error.
The story
A child process of yours keeps failing, and rush has finally given up on restarting it. Here is the story. When you start a process with a restart policy, always or on failure, you also give it a budget: this many restarts within this much time. The supervisor watches, and each time the child fails, it starts it again, until the budget is spent. One more failure after that, and the supervisor stops trying. But it does not hide the problem. It writes the child's id on its own parent's record, and the parent's next step refuses with this very message. That refusal travels up the same road as any other, parent to parent, until it reaches the root, where the program exits with code one. Unless someone along the way catches it and carries on. A process with restart never, or with no policy, never reaches this point, it just stays dead. The first slot shows which child gave up, the second says why. The fix is to find why the child keeps failing, or to catch the refusal and decide what the parent should do.
Text from the Rush engine's error catalogue.