skic-v1-playground/knowledge-wiki
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wiki: sync 2026-08-19 03:04 UTC — 3 file(s) updated

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-19 03:04:18 +00:00
parent accf39d5bc
commit 01ab922efd
3 changed files with 139 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
channels/1519072621130547220.md
+8 -1
View File
@@ -1,6 +1,6 @@
# Channel Wiki: #jarvis-jr-truenas
_Channel ID: 1519072621130547220_
_Last sync: 2026-08-18 03:05 UTC_
_Last sync: 2026-08-19 03:03 UTC_
## Purpose
TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discussions.
@@ -21,6 +21,13 @@ TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discuss
- TrueNAS application deployment patterns.
- Harbor/container-registry architecture and certificate/routing requirements.
- **CONFIRMED capacity objective (RootAtSkic, 2026-08-17):** maximize this TrueNAS host's memory. For the documented W680D4U-2L2T/G5 / i9-14900KS platform, the target is `192 GB ECC` (`4 × 48 GB DDR5 ECC UDIMM`), not a smaller diagnostic kit. Procurement and validation constraints are recorded below.
- **OPEN investigation request (RootAtSkic, 2026-08-18):** review the attached Hermes container startup log and identify improvements, but **do not change anything yet**. No response or approved implementation was present in the fetched history; RootAtSkic followed up twice asking whether Hermes was alive. Source attachment: Discord message `1539151473189978142`, `message.txt`.
## Hermes startup-log investigation — 2026-08-18 (read-only)
- **CONFIRMED log observations:** container setup exited successfully and the supervised gateway started, but setup spent `424.296399` seconds between “Changing hermes UID to 568” and “Changing hermes GID to 568” (`425.036112` seconds from the UID step through setup completion). The cause is **UNKNOWN** from this log alone; recursive ownership work is a candidate to investigate, not a confirmed diagnosis.
- The lifecycle ledger reported the previous gateway life as an unclean exit consistent with `SIGKILL / OOM / VM death`, while recording `suspected_oom=False`, about 297,604 KiB RSS, abundant available memory and no swap use at its last heartbeat. The exact exit cause remains **UNKNOWN**.
- Startup marked two interrupted cron executions `unknown` after restart. It also logged repeated operational friction: `hermes: command not found` in tool shells, `discord.server_actions` configured with unsupported action `all`, unavailable web-dependent tools because `check_web_api_key` returned false, Git commands launched outside a repository, and one command held for security approval.
- **CONFIRMED security warning:** the API server was bound to `0.0.0.0` while `terminal.backend` was `local`/unsandboxed, meaning trusted-network firewalling or a sandboxed terminal backend should be evaluated. This is an investigation finding only; RootAtSkic explicitly prohibited configuration changes at this stage.
## TrueNAS Stability Incident — 2026-08-17
- TrueNAS `26.0.0-BETA.2` on `nas.lego-cloud.eu` underwent full-host boots at 11:02:52, 12:16:18, 12:32:13, and 13:52:25 Europe/Vilnius time. Docker/containerd restarts were consequences, not the initial cause.