docs
cairnobs.org Demo Source
Esc

Install · 8 of 8

Upgrading and removing

Upgrade the server first, then the agents. What a restart costs, why going back works, and what removing a package keeps.

2 min read

Upgrading

Upgrade obs-beacond before the agents. A newer server ignores what an older agent doesn't send, but an older server may refuse what a newer agent does.

Where How
Packages Install the newer package with apt or dnf. It restarts the service on the new version
A container Stop and remove the container, then run the same line with the new tag (The server in a container)
Kubernetes Change the tag and apply again. With one copy the pod is replaced; with several they roll one at a time (Kubernetes and OpenShift)
Linux agents Install the newer obs-beacon-agent package. Your configuration tool can do this, or run the release's package by hand
Windows agents .\obs-beacon-agent.exe service install from the new zip
Cluster agents curl -fsSL https://obs.example.org/cluster.yaml | kubectl apply -f -, no token

Read the release notes on the Releases page first: they say when a release needs anything more.

What a restart costs

With one copy, the web interface is away for as long as the restart takes, usually under a second. Nothing is lost:

  • Agents keep each report they can't send, on disk, and send the backlog once obs-beacond answers. After an outage each waits a random few seconds first, so the fleet doesn't arrive at once.
  • Incidents and held alerts are in the database, so they carry on.
  • No host is called silent for stale_after after a start, so a host that went quiet only during the gap isn't.

With several copies on PostgreSQL there's no gap at all (Scale and several copies).

Going back

The database schema only ever grows, so the previous release runs on a database the newer one has upgraded. To go back, install the older package or run the older tag the same way.

Removing

Removing a package stops and disables its services, but keeps the config in /etc/obs-beacon, the database in /var/lib/obs-beacon and the obs-beacon user, so installing it again picks up where it left off. Delete those yourself to remove everything; the state key is in /etc/obs-beacon, so check your backups have a copy first.

Remove a host under Configure › Hosts before or after taking the agent off it: that revokes its certificate at once and takes it off the screens.