Keep a node up to date
Each node runs Jaah's software, and Jaah publishes new releases of it. By default a node installs each new release by itself. You can turn that off for a node you want to hold on its version, and ask a node that has fallen behind to update now instead of waiting.
Who can do this: requires the org admin role. Auto-update also needs the permission to edit nodes, and is read-only on a Jaah Cloud node, one the operator allocated, or a node on a machine shared with other organizations.
Set whether a node updates itself
-
In the sidebar, select Directory, then the Machines tab.
-
Select the node's name. Its details open on the Overview tab.
-
Select the Properties tab.
-
Under Host, pick Auto-update:
- Default follows your organization's setting, shown in brackets, for example Default (On).
- On installs each new Jaah release by itself.
- Off keeps the node on its version until you change this. Update is then unavailable for it.

-
Select Save. Saved shows at the top.
A node on a host has no choice of its own: it reads Auto-update: On (or Off) · follows host and the host's name. Change it on the host, where it applies to every node on that host.
Ask one node to update now
- On the Machines tab, find the node's row and select ⋯ at its end.
- Select Update. It appears only while the node runs an older Jaah version than the latest. It is greyed, with the reason, while the node is offline, has never connected, or has Auto-update set to Off.
- Read the message: Update requested — applies on the node’s own schedule. The node installs it on its own schedule; Update leaves the menu once it runs the latest version.
Update many nodes at once
-
On the Machines tab, tick the box at the end of each node's row, or the one in the column's heading for every node on the page.
-
A bar above the list says how many are selected. Select ⋯ at its end, then Update.

-
Only the ticked nodes that are behind and can update now are asked. When none can, Update is greyed with No picked node is behind with its update gate open.
-
Read the report: each node that refused is listed with the reason.
To check the node is online again after its update, see Read a node's status. If an update leaves a node misbehaving, restart it; to keep new tasks off a node while you deal with it, drain or disable it. Where nodes come from, and their statuses, is in How nodes work.