Upgrade and uninstall

You only upgrade the master. Agents update themselves to the master's version a few moments later (auto_update = true in agent.conf).

Since 1.1.1, agents only install agent programs signed by 3R Soft: the release package contains the signature (SHA256SUMS.sig), and the installer copies it to the master with the agent packages. So a master that was taken over can't push a program of its own to your servers. System → Connections and components → Agent packages shows Downloadable, signed; if it shows Not signed, agents don't update from that master: upgrade the master from the official release package.

From the panel (one click)Copy Anchor Link

The master checks 3rsoft.com.pa for a new version every 6 hours. When there is one, administrators see Update x.y.z in the top bar, and System → Software updates shows the release notes and an Update now button.

When you click it:

1. the master downloads the package and checks it against the release signed by 3R Soft (Ed25519 signature and SHA-256). The card shows each step, with a percentage and a progress bar while it downloads;
2. when the package is ready, the panel asks Install 3R Monitor x.y.z now?. Nothing is installed until you click Install. If you close the question, the card says "x.y.z is downloaded and its signature checked. It is installed only after you confirm." and Install now… (or the Install button) asks again. The downloaded package is kept if the master restarts;
3. a small root service (3rmonitor-update.path / 3rmonitor-update.service, installed by install.sh) checks the signature again and runs the new package's install.sh upgrade;
4. the panel reloads by itself when the master is back, usually after a few seconds. Agents then update themselves to the same version.

The question before installing is shown by the version that does the update, so you see it from the first update after 1.1.1. An update from an older version installs right after the download, as before.

A display screen in full screen doesn't reload, because that would leave full screen: it shows Live · new version ready and loads the new version when full screen is exited. See Display mode.

Only versions published by 3R Soft, and newer than the installed one, can be installed this way. If a newer version is published after you downloaded one, the card offers the newer one. If an update fails, the card shows the error and the installer output.

To stop checking for updates, turn Check for updates automatically off on the same card. The check sends only the installed version, the operating system and the architecture.

By handCopy Anchor Link

Download the new release package, extract it and run the upgrade in its directory. The command is the same on the master and on agent servers:

curl -fL -o 3rmonitor.tar.gz https://3rsoft.com.pa/download/3r-monitor
tar xzf 3rmonitor.tar.gz && cd 3rmonitor-*/
sudo bash install.sh upgrade

The program is replaced and the services are restarted. Configuration and data are kept.

Upgrading to 1.1.0Copy Anchor Link

From 1.1.0 on, the agent no longer runs as root. When an older agent updates itself, it switches by itself to the unprivileged user 3rmonitor-agent and installs the root helper 3rmonitor-helper; sudo bash install.sh upgrade does the same on a server you upgrade by hand.

If the switch fails, the agent keeps monitoring the server as before, but the AI runs nothing on it, and the server's page and AI → On-call show why. Fix the cause and run:

sudo 3rmonitor agent secure

To let the AI run the repairs you approve on servers that were installed before 1.1.0, register a passkey and run sudo 3rmonitor approvers trust on each of them.

Upgrading to 1.1.1Copy Anchor Link

• Traffic usage starts counting when the master is upgraded: the server page says "Counted since" that day. Counting only one network interface needs agent 1.1.1, which the agents install by themselves.
• The 3rmonitor command is also linked in /usr/bin, so sudo 3rmonitor … works on AlmaLinux, Rocky, RHEL and CentOS. Agents add the link by themselves when they update.
• install.sh upgrade (also the one-click update) runs the master in a stricter systemd sandbox, /etc/systemd/system/3rmonitor-master.service.d/hardening.conf. On the few systems that don't support it, for example some LXC containers, the installer removes it by itself and the master runs as before.

Check the versionCopy Anchor Link

3rmonitor version
3rmonitor status

The Servers page shows each agent's version. An agent that stays on an older version usually can't reach the master, or has auto_update = false in /etc/3rmonitor/agent.conf.

UninstallCopy Anchor Link

sudo bash /opt/3rmonitor/install.sh uninstall           # uninstall, keep configuration and data
sudo bash /opt/3rmonitor/install.sh uninstall --purge   # also delete the configuration and the data

Without --purge, the installer asks whether to delete the configuration and data too. If you keep them, a later reinstall uses them again.

Uninstalling also removes:

• the services (3rmonitor-master with its sandbox settings, 3rmonitor-agent, 3rmonitor-helper and the update service);
• the blocklist firewall rules (the inet threermonitor nftables table, or the 3RM-INPUT iptables chain and its ipsets);
• the Nginx or Apache reverse proxy configuration created by the installer;
• the 3rmonitor command (in /usr/local/bin and /usr/bin) and /opt/3rmonitor.

With --purge it also deletes /etc/3rmonitor, /var/lib/3rmonitor, /var/lib/3rmonitor-helper and the 3rmonitor and 3rmonitor-agent users. Make a backup first if you may need the history again.

To remove an agent server from the panel as well, delete it in Servers (⋯ → Delete).