Troubleshooting, lac-doctor, and rollback

Manual / Troubleshooting, lac-doctor, and rollback

Start with static verification, then verify the full managed runtime only after the qualified dependencies and model assets are present.

Static checks

~/.local/bin/lac-doctor --static

Use this after installation even if the heavyweight managed model runtime is not yet provisioned.

Full checks

~/.local/bin/lac-doctor

A complete managed-runtime setup should report "ok": true.

Common failure classes

Pi or FreeToken pin mismatch: verify exact checkout commits; do not substitute revisions.
Missing Pi dependencies: install the pinned Pi checkout's required JavaScript dependencies.
Managed runtime unavailable: rc.12 expects already-provisioned qualified FreeToken/model/runtime assets.
Admin plane unavailable or wrong state identity: governed Pi fails closed rather than attaching to a mismatched authority store.
Permission discovery: the original request is denied; configure owner policy and use the bounded fresh-request continuation workflow.
Emergency paused: inspect/resume through owner administration. Resume does not revive already-closed requests.

Rollback

python3 ~/.local/share/local-agent-controller/current/app/scripts/lac-v1 rollback

rc.12 versioned installation preserves/restores the prior supported install state. The rc.12 productization path performs no controller database migration, so rollback does not need to rewrite canonical controller data.

Backup nuance: installation creates a preinstall controller-database backup as an install-safety artifact. Do not rely on the productization documentation's older wording that implies this backup necessarily remains after rollback; rollback cleanup may remove the productization backup directory.

Need help?

Public bugs and feature requests: GitHub Issues. Undisclosed vulnerabilities: Private Vulnerability Reporting. Commercial licensing: support@itecob.com.