NEC-390: Container log lines are copied to /var/log/syslog and kept ~33 days, past the 30 privacy.md promises #353
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!353
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-390-container-log-lines-are-copied-to-varlog"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task: NEC-390 — https://projectron.nerchure.com/tasks/412
Container log lines were copied to /var/log/syslog. Ubuntu's own journald drop-in, /usr/lib/systemd/journald.conf.d/syslog.conf, turns on forwarding to rsyslog, and it sorts after our nectenda.conf. So since NEC-383 every container line also landed in /var/log/syslog, where logrotate keeps it about 33 days. That is outside the journal's caps and past the 30 days docs/privacy.md promises. The first copied line passes 30 days on 10 December. A drop-in of the same name in /etc, deploy/journald/syslog.conf, replaces Ubuntu's and turns the forward off. It is installed as a host-files.txt row on all three kinds and written by the ops box's cloud-init. host-logs.test.ts now merges the drop-ins the way systemd does, Ubuntu's included, and tests what is in force rather than our files alone. docs/manual-testing.md corrects the NEC-383 entry and records its run. A new entry holds the host steps: a read-only check that nothing reads syslog or auth.log, install, verify, and a cleanup of the copies already written. Each file is replaced only when its whole pipeline succeeded, which was rehearsed on synthetic logs in Ubuntu 24.04. Ride-along NEC-394: install-deployer.sh --check now reads systemd-analyze cat-config on every host. It fails unless our journald settings have the last word, reading values as systemd does (whitespace trimmed, [Journal] only), and fails a host it cannot read. That gap is how this bug went unreported. The fix and the read were rehearsed against a real systemd 255. Nothing changes on the fleet until deploy/install-deployer.sh is run after merge.
Spec:
docs/changes/NEC-390-container-lines-out-of-syslog/spec.mdAlso fixes NEC-394: install-deployer.sh --check does not see what journald reads, so a vendor drop-in can turn the syslog forward back on unreported
Changelog
NONE