Sentry updates
Sentries keep themselves up to date. You do not need to log in to them to install new versions.
How updates work
- Each sentry checks for a new version every few hours, and again in every update window, so a window is never skipped.
- A new version is installed automatically during the cluster's update window (see below), unless you force it or turn automatic updates off.
- Every release is digitally signed by stillorigin. Before replacing itself, the sentry checks the signature, the file's checksum and size, and that the version is newer than the one it is running. If any check fails, it refuses the update and keeps running its current version.
- After updating, the sentry restarts its own service. Nginx and the firewall rules keep running while it restarts, so traffic is not interrupted.
- The installer checks the same signature when you first install a sentry.
Update window
Each cluster has its own update window, set on Clusters → Edit under Automatic sentry updates:
| Setting | Default | What it does |
|---|---|---|
| Install new sentry versions automatically | On | When off, a new version is installed only when you click Force |
| Time zone | UTC | The time zone the window is in, for example Australia/Sydney. Type to search the list. Daylight saving is handled for you |
| Window start / Window end | 02:00 / 04:00 | When updates may be installed. The window must be at least 1 hour long and can run past midnight, for example 23:00 to 01:00 |
When you edit a cluster that still uses UTC, the form suggests your browser's time zone. Nothing changes until you click Save.
The cluster list shows each cluster's next update window in the cluster's time zone and in your own local time.
Sentries update one after another
The sentries in a cluster do not all update at once. The window is shared out between them, and each sentry always uses the same part of it, so one finishes before the next one starts. The last few minutes of the window are kept free so a late update still finishes inside it. In a cluster with many sentries and a short window, the slots are short, so use a longer window if you have many sentries.
Changes to the window reach the sentries within about a minute.
Seeing and forcing updates
On Clusters, and on each cluster's Edit page, the Released version is shown, and each sentry row shows its Version and Update status:
| Update status | Meaning |
|---|---|
| up to date | The sentry runs the released version |
| waiting to update | A newer version is available; the sentry will install it in the cluster's update window |
| waiting for force update | You asked for an immediate update; it happens on the sentry's next check-in (usually within a minute) |
| unknown | The sentry has not reported its version yet |
To update without waiting for the update window, click Force on a sentry's row on the cluster's Edit page (or Manage sentries), or Force update all at the top of Clusters. This also works when automatic updates are off. A forced update still goes through every signature check.
If a sentry stays on an old version, check that it is Online, that its clock is right, and that automatic updates are on for its cluster. On the sentry, journalctl -u stillorigin-sentry | grep "update window" shows the window and time zone it is using and when it will next update.