ACME logger path repeatedly duplicates "maintenance" segments
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
No source file or test is named. Start by searching the Go code for ACME renewal or maintenance logging, then reproduce the renewal/maintenance cycle with default settings. Done means the tls.loader.acme entries use a single maintenance segment across update cycles and the relevant tests or reproduction pass.
Written by the indexing model from the issue text.
Description
Logger path accumulates repeated "maintenance" segments (tls.loader.acme/maintenance/maintenance/...), producing noisy lines when ACME renewals run.
Repro (assume defaults):
Enable ACME in maddy.
Wait for renewal/maintenance cycle.
Observe tls.loader.acme log entries.
Observed:
tls.loader.acme/maintenance/maintenance/...: got renewal info { ... }
tls.loader.acme/maintenance/maintenance/...: updated and stored ACME renewal information { ... }
Expected:
tls.loader.acme/maintenance: got renewal info { ... }
tls.loader.acme/maintenance: updated and stored ACME renewal information { ... }
Sanitized example:
tls.loader.acme/maintenance/maintenance/...: got renewal info {"cert_expiry":"","identifiers":[""],"next_ari_update":"","remote_ip":""}
tls.loader.acme/maintenance/maintenance/...: updated and stored ACME renewal information {"cert_expiry":"","next_update":"","remote_ip":""}
maintenance line grows every update cycle
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 327
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from foxcpp/maddy
-
ready-for-release
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
bug invalid
-
bug
-
new feature
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
🤔 refinement needed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
equinor/radix-operator#1979 ·