SLP_Software/slp-modular-cms
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity

Adds systemd --user bus-connection troubleshooting

Browse Source 
Enabling lingering doesn't start the user manager retroactively, and
sudo -u often drops XDG_RUNTIME_DIR - both produce the same "Failed
to connect to bus" error when setting this up by hand.
This commit is contained in:
Sluijsens
2026-07-29 12:56:01 +02:00
parent 33d18ebbf8
commit 6882eda03f
2 changed files with 24 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aidlc-docs/features/gitea-deployment-workflow/audit.md
+11
View File
@@ -1356,3 +1356,14 @@ by Infrastructure Design. U5 carries REF-U3-01's Umami origin gate plus FR-21 an
**Context**: OPERATIONS — Deployment Setup revealed a genuine Construction-phase technology gap; resolved with application code changes (not just documentation), verified against a real database
---
## Deployment Setup — systemd --user Bus Connection Troubleshooting
**Timestamp**: 2026-07-29T00:10:00Z
**User Input**: "Als ik systemctl --user daemon-reload uitvoer krijg ik de volgende fout \"Failed to connect to bus: No medium found\""
**AI Response**: "Explained the likely causes (lingering not yet enabled, user manager not started since enabling lingering doesn't retroactively start it, or running via sudo -u instead of a real login shell losing XDG_RUNTIME_DIR) and gave concrete fix commands. Added a troubleshooting note to deployment-instructions.md § 1.3 covering this exact error for future readers doing manual host setup before the deploy workflow ever runs."
**Context**: OPERATIONS — Deployment Setup, host-setup troubleshooting captured in documentation
---