diff options
| author | Pjotr Prins <pjotr.public01@thebird.nl> | 2026-11-19 12:02:34 +0000 |
|---|---|---|
| committer | Pjotr Prins <pjotr.public01@thebird.nl> | 2026-11-19 12:02:34 +0000 |
| commit | a621bb36303ad6c45fee88e9d3700abd36799a26 (patch) | |
| tree | 3adb8f8e69f8bc1d648549457616ac40f7e6af25 /test/data/parity-fixtures/Q21.json | |
| parent | 333965fa18fa2d837b9fda7935bb6bbc4c8ca9ce (diff) | |
| download | genenetwork4-main.tar.gz | |
run.sh restart replaces the two instances only. On 2026-11-19 the stub on
:8081 was down, so every authenticated endpoint answered
401 invalid_token: fetching http://127.0.0.1:8081/auth/public-jwks:
io: Connection refused (os error 111)
while /version and /mapping-methods still answered -- the deployment looked
alive and the read surface was entirely dark. A monitor run is what names
it, so the checklist now says what to look for (18 failed, all 401), how to
start the stub, and that its key is fixed, which is why tokens minted before
the outage were still valid afterwards.
The stub's token file belongs under the deployment's state directory: /run
does not survive a reboot, and this is the failure that follows.
Diffstat (limited to 'test/data/parity-fixtures/Q21.json')
0 files changed, 0 insertions, 0 deletions
