Question -
Has anyone else noticed some strange behavior with the operating system inspector on Ubuntu?
Background -
We have noticed some reporting discrepancies between the “uptime” command on Ubuntu 20.04 and the client relevance “boot time of operating system”.
For example, one system in bigfix it shows “Tue, Apr 2004”(~7664days) but the uptime command on that devices says it is actually ~93 days. Time and date on the device seems to be set correctly.
Also of note, a fast query shows ~23 devices with a last boot time of Dec 31 2020 - yet all of them are new builds within the last year.
Just to check, do you have the Ubuntu agent loaded on them? I’ve seen cases where the generic Debian agent is installed instead, and it mostly functions but does give some incorrect results on other properties.
I believe BigFix uses the data from /proc/uptime as the source for calculating uptime. Just wondering how the data in that file compares to your uptime, or if suspending the OS (maybe if it a VM or has power saving enabled) may cause a skew that possibly the OS command caters for differently?
It is the Ubuntu agent but the package is deb… not sure if that makes a difference.
Thanks for that… I ran an endpoint upgrade to match our relay version and that seems to have cleared the issue. Possibly… will know for sure when we do some more… Nope, that did not work.
This relevance seems to be much more accurate than the out of the box analysis using the operating system property… no idea why though
preceding text of first "." of lines of file "/proc/uptime" as integer * second