aboutsummaryrefslogtreecommitdiff
path: root/docs/workflows/system-health-check.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-09 14:02:20 -0500
committerCraig Jennings <c@cjennings.net>2026-07-09 14:02:20 -0500
commita8f7e9b9c089577b299afc04bd1e1be040197995 (patch)
tree9506262da100139f793926cfb8b75e2f92330044 /docs/workflows/system-health-check.org
parent9f07851cdb7863fafe046cf83199e3e5a730f49d (diff)
downloadarchsetup-main.tar.gz
archsetup-main.zip
docs: remove personal paths and false co-authorship before releaseHEADmain
The repo carries an open task to publish it, and docs/ leaked things a clone could neither use nor should see. Absolute paths under one user's home become the repo root, a home-relative path, or a named variable, so the snippets stay runnable for anyone. The testinfra example takes its user from an env var instead of hardcoding one. References into a private sibling project and into the gitignored tooling directory are replaced by what they mean; as written they were dead links in any clone but the author's. Five documents claimed a co-author who is not a person. An #+AUTHOR line survives conversion into docx, a wiki page, or a PDF, so it is worth being exact about: these documents have one author.
Diffstat (limited to 'docs/workflows/system-health-check.org')
-rw-r--r--docs/workflows/system-health-check.org4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/workflows/system-health-check.org b/docs/workflows/system-health-check.org
index 98fa17f..b4f34a5 100644
--- a/docs/workflows/system-health-check.org
+++ b/docs/workflows/system-health-check.org
@@ -1,5 +1,5 @@
#+TITLE: System Health Check Workflow
-#+AUTHOR: Craig Jennings & Claude
+#+AUTHOR: Craig Jennings
#+DATE: 2026-02-27
* Overview
@@ -1030,7 +1030,7 @@ Each entry is scoped to one host (or =any=). When Phase 1 cross-references findi
** 2026-06-13: ratio — dockerized telega-server SIGSEGVs in musl build
:host: ratio
-- Symptom: =coredumpctl= shows repeated SIGSEGVs from =telega-server -O 31 -l /home/cjennings/.telega/telega-server.log -v 3= running inside the Telega Docker container. Example stack is entirely in the container's musl loader plus =/usr/bin/telega-server=, not host kernel, GPU, storage, or memory paths.
+- Symptom: =coredumpctl= shows repeated SIGSEGVs from =telega-server -O 31 -l ~/.telega/telega-server.log -v 3= running inside the Telega Docker container. Example stack is entirely in the container's musl loader plus =/usr/bin/telega-server=, not host kernel, GPU, storage, or memory paths.
- Evidence: =~/.telega/telega-server.log= ends with =Unexpected char 'm' in plist value= followed by =Assertion failed: false (telega-dat.c: tdat_plist_value: 500)=. Surrounding TDLib traffic includes sticker/custom-emoji metadata such as =documentAttributeCustomEmoji= and =PhotoSizeSourceThumbnail[Thumbnail, type = m]=.
- Prior local triage: =~/.emacs.d/todo.org= recorded the same issue on 2026-06-11 as spontaneous memory-corruption crashes in =zevlg/telega-server:latest='s musl build, with several coredumps occurring without action-verb traffic. Telega package installed at the 2026-06-13 health check was =20260513.509=; MELPA had =20260604.2321= available.
- Functional status at 2026-06-13 check: no coredumps yet that day; Telegram scans still worked from cached chat state. Treat as an app/server-container crash, not a machine-health fault.