recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
fffd83fe4bd65af053e16ea9d730dec22add1570
cc-ci-orchestrator/cc-ci-plan/REBOOTS.md
autonomic-bot e7f05ceffe orchestrator-migration: Phase A COMPLETE (cc-ci-orchestrator VM up + ssh) + reboot #3 log 
Phase A done before the Pi's reboot #3 (commit was interrupted): the loops VM
cc-ci-orchestrator is on the tailnet (100.116.55.106) and ssh-able; TS-key
finding recorded (VM-creator .test.env key revoked; cc-ci .testenv key valid +
persisted). REBOOTS.md carries the auto-logged 2026-05-30 17:03 reboot
(cc-ci-loops.service auto-recovered the loops at phase 2; swapfile persisted).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-30 17:07:02 +01:00

1.1 KiB
Raw Blame History

Reboot log — cc-ci orchestrator Pi

One line per genuine reboot of the orchestrator Pi (raspberrypi), appended automatically by reboot-log.sh (ExecStartPre of cc-ci-loops.service, boot_id-gated so manual service restarts are NOT counted). The Pi hosts the Builder + Adversary loops + watchdog; a reboot drops the tmux sessions (and this orchestrator session), and cc-ci-loops.service restarts the loops on boot. Count the lines below to see how often it's happening.

Reboots

  • 2026-05-28 (~19:?? BST) — reboot (backfilled from memory; mid-Phase-2). Orchestrator + loops were down until manually relaunched. This pre-dates the systemd auto-restart service.
  • 2026-05-28 (~20:02 BST) — reboot (backfilled from memory; uptime showed 5 min at 20:07). Loops manually relaunched at phase 2; this is what prompted adding cc-ci-loops.service + auto-logging. Auto-logging is live from the next reboot onward.
  • 2026-05-30 17:03:05 BST — reboot detected; loops auto-started by systemd (resuming phase index 6). boot_id=f565f752-0463-42db-b787-9e0db35a5e3f