DongHyeonkaandClaude Opus 5
faf55dc1be
The forced renewal did work. What did not work was anything making nginx
notice.
disk cert2.pem written 2026-09-04 17:22:13 KST
network old serial through 08:58:47 UTC, new serial from 08:58:52 UTC
gap 2199 seconds, and the old certificate was observed 428 times in it
The gap closed only because a person ran `nginx -s reload`. Nothing else
would have: certbot-renew.service is just `ExecStart=/usr/bin/certbot -q
renew` with no ExecStartPost, all three of renewal-hooks/{deploy,post,pre}
are empty, and certbot 5.7.0 here has no nginx plugin (dns-cloudflare,
manual, null, standalone, webroot). Three paths, all empty. Any one of them
would have been enough.
nginx holds the certificate in memory from startup, and certbot swaps the
live/ symlink rather than the path — so the config still looks right while
the served certificate is stale. Master 585 and worker 586 sharing a start
time 22.4 hours old is what proved no reload had happened.
This is invisible for 88 days. The timer ran twice today and exited
0/SUCCESS both times, because a renewal is not due yet. The day it becomes
due, the symptom is an expired certificate and the log still says SUCCESS.
The other half of the plan's question now has a measurement rather than an
expectation. The reload is genuinely graceful: 8856 polled connections, zero
non-200, p95 205.7ms before against 204.3ms after. And an in-flight request
— 845KB pulled at 20k/s, so still transferring 12 seconds in when the reload
landed — completed with all 845361 bytes over a single connection.
The earlier note that nginx reload "is graceful by design but must not be
written that way without checking" was right to hold back. The neighbouring
belief, that renewing gets the new certificate served, was the one that was
false, and there was no way to tell in advance which it would be.
Adds diagrams/d4-renewal-gap.svg and evidence 09-13.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
42 lines
2.0 KiB
Plaintext
42 lines
2.0 KiB
Plaintext
Saving debug log to /var/log/letsencrypt/letsencrypt.log
|
|
|
|
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
|
Found the following certs:
|
|
Certificate Name: auth.hyeonworks.com
|
|
Serial Number: 6c7cb6df1da8a6d7995d93c264bb9ecea1d
|
|
Key Type: ECDSA
|
|
Identifiers: auth.hyeonworks.com app1.hyeonworks.com app2.hyeonworks.com
|
|
Expiry Date: 2026-12-03 07:21:52+00:00 (VALID: 89 days)
|
|
Certificate Path: /etc/letsencrypt/live/auth.hyeonworks.com/fullchain.pem
|
|
Private Key Path: /etc/letsencrypt/live/auth.hyeonworks.com/privkey.pem
|
|
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
|
|
|
=== renewal-hooks ===
|
|
/etc/letsencrypt/archive/auth.hyeonworks.com/:
|
|
total 48
|
|
drwxr-xr-x 2 root root 4096 2026-09-04 17:22:13.508658811 +0900 .
|
|
drwx------ 3 root root 4096 2026-09-03 10:47:40.915270972 +0900 ..
|
|
-rw-r--r-- 1 root root 1359 2026-09-03 10:47:40.915923507 +0900 cert1.pem
|
|
-rw-r--r-- 1 root root 1359 2026-09-04 17:22:13.508494637 +0900 cert2.pem
|
|
-rw-r--r-- 1 root root 3523 2026-09-03 10:47:40.916215769 +0900 chain1.pem
|
|
-rw-r--r-- 1 root root 3523 2026-09-04 17:22:13.508658811 +0900 chain2.pem
|
|
-rw-r--r-- 1 root root 4882 2026-09-03 10:47:40.916339551 +0900 fullchain1.pem
|
|
-rw-r--r-- 1 root root 4882 2026-09-04 17:22:13.508821612 +0900 fullchain2.pem
|
|
-rw------- 1 root root 241 2026-09-03 10:47:40.916079294 +0900 privkey1.pem
|
|
-rw------- 1 root root 241 2026-09-04 17:22:13.507717972 +0900 privkey2.pem
|
|
|
|
/etc/letsencrypt/renewal-hooks/deploy/:
|
|
total 8
|
|
drwxr-xr-x 2 root root 4096 2026-09-03 10:46:54.658474560 +0900 .
|
|
drwxr-xr-x 5 root root 4096 2026-09-03 10:46:54.658520760 +0900 ..
|
|
|
|
/etc/letsencrypt/renewal-hooks/post/:
|
|
total 8
|
|
drwxr-xr-x 2 root root 4096 2026-09-03 10:46:54.658505772 +0900 .
|
|
drwxr-xr-x 5 root root 4096 2026-09-03 10:46:54.658520760 +0900 ..
|
|
|
|
/etc/letsencrypt/renewal-hooks/pre/:
|
|
total 8
|
|
drwxr-xr-x 2 root root 4096 2026-09-03 10:46:54.658474560 +0900 .
|
|
drwxr-xr-x 5 root root 4096 2026-09-03 10:46:54.658520760 +0900 ..
|