Repository navigation
v7.4.8 — "Hon3stMatters"
Pre-releasePre-release from the dev branch, like 7.4.1 to 7.4.7 before it. main and the Docker latest tag stay on 7.4.0 until the next main release, and no Docker image is published for this one. To run it, download the tarball below, or build an image from the tag: docker build -t remotepower:7.4.8 https://github.com/tyxak/remotepower.git#v7.4.8.
Check the download with sha256sum -c remotepower-7.4.8.tar.gz.sha256 and gpg --verify remotepower-7.4.8.tar.gz.asc remotepower-7.4.8.tar.gz (signing key E7B5AD456728B8462A8B54BFD488AF115D2CCDBF).
RemotePower v7.4.8 — "Hon3stMatters"
A patch release for three screens that said something that was not true: a Problems row that read "never" under Updated, a
sensor limit of 65261.8 °C on the Thermal page, and a host that read "Fully Patched" while a kernel update waited. The first two
came from the reporter of #54 and #56, who tried the releases and wrote back. The third was a question in Discussions (#30) that
had gone unanswered for two months.
After upgrading, hard-reload the dashboard once so the new front-end loads. Update the Linux agents too: the sensor limits and the
patch count are decided on the host.
The Problems list shows when
A problem that only Needs Attention or Checks list (pending updates, an old agent version) has no alert, and the Updated column
is the time of the newest alert, so it read "never". Such a row shows when its host last reported it now, and a dash when the
host has not said when. Sorting by the column uses the same time. See problems.md.
A limit that is not a temperature
An NVMe drive that sets no threshold reports 65535 K, which is 65261.85 °C, and a drivetemp sensor that has none reports 0. Both
reached the Thermal page as the sensor's critical value, so a host whose hottest sensor was one showed a threshold of 65261.8 °C
and a headroom of 65215.9. A limit outside 1 to 150 °C is dropped now, by the agent, by the server on the way in and by the page
for a value an older agent already stored. The hot and critical flags were never affected.
The nvme-* sensors of a host are held to the NVMe lines now, and the drivetemp-* sensors to the lines for any other drive
(that driver reads hard disks and SATA SSDs alike, so its name does not say which), on the Thermal page and in the risk score.
The temp_high alert and the reliability grade still judge them by the fleet's temperature settings. Nothing changes
until you set a drive line. See thermal.md.
A package apt keeps back is pending
apt-get upgrade never installs a package that is not installed yet. When an upgrade needs one (a new kernel image behind
linux-image-amd64, the split linux-firmware packages), apt keeps the package back, prints no error and exits 0, and the host
read Fully Patched, Pending: 0 while a security update waited. The agent counts a kept-back package as pending now, and as a
security update when apt lists it from a security archive. A package held with apt-mark hold stays out, and when the agent
cannot read the holds it counts none.
The patch button and auto-patch still run apt-get upgrade, so they do not install a kept-back package: it stays pending until
you run apt-get install <package> or apt-get full-upgrade on the host. Debian and Ubuntu hosts only; dnf, yum and pacman hosts
are unchanged. This was checked against the text the reporter posted and against stand-in apt programs, and not on a real
Debian or Ubuntu host. See patches.md.
Security review
One low issue was fixed before release. A stored sensor, drive or GPU reading, or a sensor limit, that is an integer of more than
308 digits cannot be converted by float(). The Thermal page and the risk score converted what they read, so the page answered 500
for every host for as long as the row stayed, and the Prometheus export raised on the same value. The server never writes such a
row; only a hand edit or an import can. The page and the score skip what is not a number a float holds now, and the export drops
it as it drops a NaN. The release adds no route and changes no permission, role or dependency. See
security-review-7.4.8.md.
Translations
This release adds no text to translate.