3.1 KiB
DR Issue Log
Tracked issues found during DR audits. Each entry: date, problem, root cause, fix applied, verification.
2026-07-08 — Initial Full DR Audit
DR-001: Caddyfile not included in backup scripts
Problem: /etc/caddy/Caddyfile was not copied by hermes-backup.sh or hermes-live-sync.sh. If Core server fails, the full Caddy reverse proxy config would need to be rebuilt from scratch. Root cause: Backup scripts were written to cover hermes config and user directories but omitted system-level config files. Fix: Added /etc/caddy/Caddyfile to hermes-backup.sh and hermes-live-sync.sh Status: ✅ Fixed 2026-07-08 Verified by: Post-fix script syntax check and line reference
DR-002: Systemd service files backed up to wrong path
Problem: hermes-backup.sh collected systemd services from ~/.config/systemd/user/ instead of /etc/systemd/system/. The real service files were not backed up. Root cause: Backup script path pointed to user-level systemd vs system-level. Fix: Corrected path in hermes-backup.sh to /etc/systemd/system/*.service Status: ✅ Fixed 2026-07-08 Verified by: Post-fix script syntax check
DR-003: migration-creds.txt not in backup scope
Problem: /root/.hermes/migration-creds.txt existed but wasn't referenced by any backup script. Root cause: Added after backup script was written, never included in scope. Fix: Added to hermes-backup.sh file list Status: ✅ Fixed 2026-07-08 Verified by: Post-fix script syntax check
DR-004: dre-temp-passwords.txt exposed at 644 permissions
Problem: /root/.hermes/references/dre-temp-passwords.txt was readable by all users (644) instead of owner-only (600). Root cause: Script created the file without explicit permission setting. Fix: chmod 600 Status: ✅ Fixed 2026-07-08 Verified by: ls -la confirms 600
DR-005: migration-creds.txt at 644 permissions
Problem: Same as DR-004 — migration-creds.txt was 644. Root cause: Written without explicit permission setting. Fix: chmod 600 Status: ✅ Fixed 2026-07-08 Verified by: ls -la confirms 600
DR-006: Full backup stale (last ran Jul 5)
Problem: hermes-full-backup.tar.gz last uploaded to S3 on Jul 5. The daily 5AM cron has missed 3 days. Root cause: Script may have errored, cron may have stopped — [INVESTIGATING] Fix: [PENDING] Status: 🔄 Investigating
DR-007: home-router-daily-backup cron error
Problem: Cron job errored at 06:00 today — backup script failed. Root cause: [INVESTIGATING] Fix: [PENDING] Status: 🔄 Investigating
DR-008: MikroTik CCR backup stale (last Jul 5)
Problem: mikrotik-ccr-backups S3 bucket has no uploads since Jul 5. Root cause: [INVESTIGATING] Fix: [PENDING] Status: 🔄 Investigating
DR-009: app1-bu powered on when DR plan says offline
Problem: Warm standby server is running (3 days uptime) but DR plan says "offline, boots on demand." Root cause: Server was previously started and not powered back off. Fix: [PENDING — confirm with Germaine] Status: 🔄 Awaiting decision