Power in the SoAI WebUI separates application lifecycle actions from actions that affect the entire host. It is
available only to an Administrator with
System power control
(SYSTEM_POWER). An eligible Administrator can open
it from the sidebar's System section or from Restart / Shutdown in the header settings menu on
any page, so the sidebar entry can be hidden in sidebar customization.
Choose the correct scope
| Action | Effect | Options |
|---|---|---|
| Restart SoAI | Restarts SoAI and its services. The host stays running. | Delay in seconds, default 0 |
| Shut down SoAI | Stops SoAI. Another host process or service must start it again. | Delay in seconds, default 10 |
| Restart system | Reboots the whole host and reloads the operating system. | Delay in seconds, default 10; optional Force restart |
| Shut down system | Stops host processes and powers off the machine. | Delay in seconds, default 10; optional Force shutdown |
| Suspend system | Pauses processes in a low-power state until the host resumes. | Delay in seconds, default 10 |
| Hibernate system | Saves memory to disk and powers off most hardware. | Delay in seconds, default 10 |
Run an action
- Open Power and select the intended action.
- Read the confirmation and set the delay or force option. System actions warn that they affect the whole machine.
- Confirm. An accepted delayed shutdown, suspend, or hibernate can show a countdown with Cancel.
- Keep the page open if you need to observe the accepted operation. The status progresses through scheduled, executing, and a truthful terminal state.
When a change needs a restart, the header shows a restart button, and the restart notification offers the same shortcut. Both open Power with the required action focused and highlighted, and a notice beside Cancel states the first recorded reason. The confirmation of that action repeats the reason in place of the delay control. Use Restart SoAI for ordinary SoAI configuration changes. A SoAI OS operation can explicitly require a full system restart.
Host actions are conditional
The page lists the host action cards, but acceptance still depends on runtime policy and operating-system support.
When
SYSTEM.RUNTIME.HOST_SYSTEM_ACTIONS_DISABLED
is enabled, SoAI rejects restart, shutdown, suspend, and hibernate requests for the host. A platform that cannot
construct the requested system command also rejects that action. The WebUI reports the failure; it does not pretend
the host changed state.
Force restart and Force shutdown can interrupt other host work. Use them only when a normal operation cannot complete and you have accounted for active tasks, database writes, model downloads, and other users.
A forced action also has a cost on the way back up, because SoAI treats the run it ended as an unclean shutdown. The next start verifies the core database before it serves anything, which can take several minutes on a large instance, and it returns saved GPU settings to safe defaults. After an unclean shutdown describes what to expect and why the check should not be interrupted.