Machine states
A machine’s row answers three questions at once, and they move on their own schedules. Reading them apart is what stops an ordinary start from looking like a fault.
The three answers
Section titled “The three answers”| Where you read it | Whose answer it is | Values |
|---|---|---|
| Status in the machines list | the machine, by whether its agent is answering | Online, Offline |
| Power on the machine page | the cloud, about the instance | Booting, Running, Stopping, Stopped, No longer exists |
| Last action on the machine page | Machinery, about the last power call it made | Starting, Booting, Ready, Stopping, Stopped, and a failure with the cloud’s own sentence |
Offline is not stopped
Section titled “Offline is not stopped”They are different facts, and they move apart:
- Online or Offline is whether the machine is reachable. Machinery reads it from the agent’s check-ins, so it answers “is anything running on the box”.
- Running or Stopped is whether the cloud instance is powered. The provider owns that answer, so it answers “is the box switched on”.
A machine can be Offline and Running (the agent stopped answering while the instance stayed powered, and it is still billing), Offline and Stopped (the ordinary state of a stopped machine), or Online and Running (everything normal). One never implies the other: read Power to know what the instance is doing, and Status to know whether anything is answering.
Online and offline
Section titled “Online and offline”The machine’s agent reports in while it runs, and the machine reads Online while those reports arrive. Two minutes without one marks it Offline.
That is the detection time for a crash or a lost network. A clean shutdown is reported as it happens and flips the machine within about a second, and a stop Machinery itself asked for does not raise a disconnect warning at all.
The power state
Section titled “The power state”The cloud’s answer, normalized so the same word means the same thing on every provider:
| Wire value | What it means | What the console shows |
|---|---|---|
pending | the provider is bringing the instance up | Booting |
running | the provider says the instance is up | Running |
stopping | the provider is shutting it down | Stopping |
stopped | the instance is powered off, and its disks are intact | Stopped |
moving | the instance is moving to another host, or into or out of a worker pool, and is stopped for part of it | Moving |
gone | the provider no longer returns the instance | No longer exists |
unknown | nothing has been read for this machine | nothing |
unknown is the answer for a machine with no cloud identity: one enrolled by hand, or a machine Machinery did not create. There is no instance to ask about, so the field stays empty rather than claiming a state.
A stop settles on the cloud, not on the agent. The instance stays Stopping until the provider says it stopped, which is tens of seconds after the guest has already gone quiet.
The last action
Section titled “The last action”Machinery records what it asked the instance to do, and how that turned out:
| Outcome | What it means |
|---|---|
pending | the call is in flight, and the machine is on its way to the state you asked for |
succeeded | the machine arrived: a start is Ready once the agent connects, and a stop is Stopped once the cloud says so |
failed | it did not arrive, and the message beside it is the reason, written by the service |
A start reads Starting, then Booting when the cloud says the instance is up, then Ready when the agent connects. A stop reads Stopping, then Stopped. There is no timer behind any of these words: each one is a fact the server already recorded.
How far a launch got
Section titled “How far a launch got”A machine’s create is recorded first and launched after, so its row carries the step it reached:
| Status | What it means | What the console shows |
|---|---|---|
pending, launching | Machinery is creating the machine now | Launching… |
launched | the launch finished, and the machine is running normally | nothing |
failed | the launch stopped, and the step names what was being attempted | Launch failed |
terminate-pending, terminating | a destroy was accepted and has not finished | Terminating |
terminated | the destroy finished and the record is retired | Deregistered |
unknown | nothing recorded a status, which is what a client older than the field reads | nothing |
Launch failed is worth reading closely, because a launch can fail after the cloud created an instance. The message beside it says whether an instance may exist that Machinery never recorded, and it is the reason that state is never shown as a calm Deregistered.
The record itself
Section titled “The record itself”Independently of all of the above, a machine is either active or deregistered. A deregistered machine has been retired from the account and is removed from the list about an hour later.
The order the console applies
Section titled “The order the console applies”One row can qualify for several of these at once, so the console reads them in a fixed order and shows the first that applies:
- a destroy that was asked for and could not be carried out, as Terminate failed
- a failed launch, as Launch failed
- the record, when it is no longer active
- a destroy in progress, as Terminating
- a launch in progress, as Launching…
- the machine’s own answer, Online or Offline
That is why the status column shows a transition in place of the presence badge: a machine being started is genuinely not answering yet, and Offline is the least useful thing to say about a box somebody is watching boot.
Next steps
Section titled “Next steps”- Launch your first machine walks through the states in order.
- Let a machine stop itself explains when an idle machine stops.
- Machine and ssh failures names the causes behind a state that does not move.