The server exits 2 while the authorization table is empty, which is the
right call: a listener that 401s every request is almost always a
forgotten `token mint`, and "connection works, auth fails" is far worse
to debug than a `systemctl status` naming the remedy.
But that puts a freshly provisioned machine in a failed state, and
systemd's default start-rate limit -- five starts in ten seconds, then
give up -- would leave it there permanently. So minting the first token
would ALSO have needed a `systemctl start` that nothing told anyone
about, and the refusal would have turned from a helpful message into a
trap on every machine that enables the option.
`StartLimitIntervalSec = 0` with `RestartSec = 5` is what makes the trade
sound: the unit retries indefinitely and comes up on its own within one
interval of the first mint. The cost is a journal line every five
seconds while the table is empty, which names exactly what is wrong.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KchcvnbfhhZhUHy83YL3Ya