Differences

This shows you the differences between two versions of the page.

--- technical:operator_commands [2026/10/16 08:10] – Publish v7.1.1 hosting, defaults, opt-outs, automatic delivery and complete public-room occupancy documentation wikiadmin
+++ technical:operator_commands [2026/10/17 06:26] (current) – v7.1.8 maintenance/recovery release and current operator procedures; distinguish publication, queue and activation wikidocs
@@ Line 3: / Line 3: @@
 These are administrative commands on the hosting machine, **not dot commands to send in osu! or Discord**. Use the protected admin entry from the currently registered release, as root, with the exact instance selected. An entry from an old release intentionally refuses after upgrade. Get the entry path and artifact hashes from the qualified kit or maintainer; do not guess a release directory.
-^ Reference | v7.1.1 common runtime and retained v7.1.0 migration boundary, October 16, 2026 |
+^ Reference | v7.1.8 common runtime and retained v7.1.0 migration boundary, reviewed October 17, 2026 UTC |
 ^ Installation guide | Follow the exact kit's README and upgrade guide; this overview does not replace their admission checks or configuration schemas |
@@ Line 64: / Line 64: @@
 | ''update-recover'' | Resolve a bound held transaction using its documented operation ID and reviewed decision |
-Use the current release’s README and V7_1_1_OPERATOR_GUIDE.md for complete schemas. Missing v7.1.1 policies default to sharing and automatic updates, while saved false values, independent reading, pauses and stopped polling are retained. Local network-start can initialize a missing updater only after enrollment; it does not grant server contribution rights. Private diagnostics are scrubbed and bounded, not publicly visible chat.
+Use the current release’s README and V7_1_8_OPERATOR_GUIDE.md and MAINTENANCE_OPERATOR_GUIDE.md for complete schemas. Missing v7.1.1 policies default to sharing and automatic updates, while saved false values, independent reading, pauses and stopped polling are retained. Local network-start can initialize a missing updater only after enrollment; it does not grant server contribution rights. Private diagnostics are scrubbed and bounded, not publicly visible chat.
+===== Controller-owned maintenance — v7.1.8 =====
+These actions require the v7.1.8 controller already installed and running. They use its existing connection; never run a second OAuth/referee helper beside the live controller.
+<code sh>
+maintenance_id=$(python3 -c 'import uuid; print(uuid.uuid4())')
+$E maintenance-request --operation-id "$maintenance_id" --mode empty
+$E maintenance-status
+$E maintenance-cancel --operation-id "$maintenance_id"
+</code>
+Omit --room to select every configured alias, or repeat --room room1 --room room2 for a subset. Empty mode waits for safe empty/idle closure. For explicitly announced maintenance, choose --mode one-map instead: confirmed warning plus a real running-map/scoring/idle boundary precedes an occupied closure. An initially empty idle room uses the independently rechecked empty closure path. Late joins postpone it. Ordinary automatic updates never select occupied one-map maintenance.
+Reuse the same UUID for an identical request or its cancellation. Cancellation is acknowledged by workers and cannot reopen a closed room. A retained nonterminal request after controller restart requires review/cancellation before a fresh request. Expiry releases an uncommitted pause; uncertain provider closure still requires stopped ownership recovery. Existing worker/controller deployment admission blocks conflicting maintenance.
+status/support now separate installed and running controller, individual worker versions/ownership, queued target/blocker, maintenance progress and next action. Fresh journal/recovery evidence outranks a stale service observation. Lifetime counters do not reset on recovery and do not imply a new fault. See the current kit for complete schemas and safe failure codes.