Updates
Updates waiting on each server, and the buttons to install them.
About this page
Every package each server could upgrade, by name, because a count of fourteen does not tell you that one of them is openssl. Servers with security updates come first, and so do the security updates inside each list.
The list is grouped by server rather than by package, because a server is what gets patched, waits for a reboot, and can be down while it happens.
{{ cmd.tail }}
{{ h.name }}
Installing asks for the action password and a fresh authenticator code, and leaves the NVIDIA driver, Jellyfin and Docker out unless you include them.
About installing
Re-check asks the server to re-read its package lists and installs nothing, so it needs neither the password nor a code.
Installing needs both: the action password and a fresh authenticator code, the same pair that guards deleting a Jellyfin account. The server only upgrades packages that are already installed, refuses anything that would remove a package, and never restarts itself.
The NVIDIA driver, Jellyfin and the Docker engine are held back unless you include them, because upgrading each one breaks something straight away: GPU transcoding until a restart, Jellyfin’s streams and transcoding settings, or every container on the server, the agent included.
Updates are queued rather than run on the spot. The agent picks the command up on its next wake, and this list clears once the server reports what it has afterwards.
While an install runs, the box at the top shows how far apt has got: what it is doing, to which package, how many of how many, and how long it has been running. It is checked every few seconds while the install runs, and the server reports only what changed, so a package that is slow to set up holds the bar still until apt moves on.