make bao readers want swarm-bao-pki and drop its start limit
A pki start refused by its start limit failed every reader that Requires= it with `dependency`. That leaves a unit inactive, not failed, so Restart=on-failure never fired and readers without a refresh timer never ran again (#5381: grafana 502 for ~43 min). Readers and granting units now Wants= + After= pki; one whose leaf is still missing fails its login with exit 1 into its existing retry. pki gets StartLimitIntervalSec=0: it is deliberately not RemainAfterExit, so each reader's start re-runs it.
This commit is contained in:
parent
141be16c6d
commit
265f8a47cc
12 changed files with 95 additions and 46 deletions
|
|
@ -149,6 +149,11 @@ in
|
|||
before = [ "swarm-bao-certs.service" ];
|
||||
requiredBy = [ "swarm-bao-certs.service" ];
|
||||
wantedBy = [ "multi-user.target" ];
|
||||
# No start limit: a mass container start pulls this in once per unit it
|
||||
# starts, which outruns systemd's default of 5 starts in 10s. No
|
||||
# `Restart=`, so nothing here loops. `[Unit]` setting, hence not in
|
||||
# `serviceConfig`.
|
||||
startLimitIntervalSec = 0;
|
||||
path = [
|
||||
pkgs.openssl
|
||||
pkgs.coreutils
|
||||
|
|
|
|||
Loading…
Reference in a new issue