Strange Uptime Inconsistancy

(imported topic written by SystemAdmin)

Hello,

I observed a very strange occurrence where BigFix reports incorrectly the uptime for a Linux AS 4 machine:

root@LinuxAS4 ~

uptime

13:45:12 up 234 days, 19:23, 2 users, load average: 0.20, 0.25, 0.20

root@LinuxAS4 bin

./qna

BESClientConfigPath must be set

BESClientActionMastheadPath not set, using /etc/opt/BESClient/actionsite.afxm

Q: uptime of operating system

A: 1799 days, 17:07:05

T: 213076295

Q: boot time of operating system

A: Tue, 28 Feb 2006 20:43:14 -0500

T: 8471421

Have you seen anything like that before and any suggestions of what might be causing, and how to resolve it? Thanks.

(imported comment written by JackCoates91)

could this be it? https://bugzilla.redhat.com/show_bug.cgi?id=97373

(imported comment written by SystemAdmin)

Yes, it looks just about right. Thank you.

So, this very old forum post still seems to be applicable.

I have a Ubuntu linux system that is reporting similar odd results:
Uptime - Unix 1971 days

However, a separate custom analysis using:
(boot time of operating system) returns
Boot Time Tue, 05 Jun 2018 10:52:14 -0400

(uptime of operating system) returns
Uptime 00:01:38

Are there issues with the Linux inspectors?

Or do we truly need the calculation of:
(if it = 1 then it as string & " day" else it as string & " days") of ((now - boot time of operating system) / day)

@blair_heiserman - what do you see as the date on the device when you ssh in?
-jgo

Matches the more recent uptime / boot time as shown above.

But that’s through a custom property.