You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had 4 rows in my uprecords output for a long time now.
# Uptime | System Boot up
----------------------------+---------------------------------------------------
1 44 days, 02:16:49 | Linux 4.8.17-hardened-r2 Wed May 10 13:33:31 2017
2 37 days, 00:45:32 | Linux 4.4.8-hardened-r1- Sun Jul 17 09:34:57 2016
3 27 days, 08:48:44 | Linux 4.4.8-hardened-r1- Fri Aug 26 13:12:51 2016
-> 4 3 days, 13:29:38 | Linux 4.12.12-gentoo-k1 Tue Oct 24 09:44:54 2017
----------------------------+---------------------------------------------------
1up in 23 days, 19:19:07 | at Mon Nov 20 17:33:38 2017
no1 in 40 days, 12:47:12 | at Thu Dec 7 11:01:43 2017
up 112 days, 01:20:43 | since Sun Jul 17 09:34:57 2016
down 355 days, 12:18:52 | since Sun Jul 17 09:34:57 2016
%up 23.966 | since Sun Jul 17 09:34:57 2016
A short bit of math would tell you that the days column does not match the expected value given that the first day listed is July 17 2016. This is a VM host, so it's pretty much always up.
I'm running on gentoo. My /var/spool/uptimed directory looks like this:
drwxr-xr-x 2 uptimed uptimed 4.0K Aug 29 08:50 .
drwxr-xr-x 6 root root 4.0K May 27 15:14 ..
-rw-r--r-- 1 uptimed uptimed 0 Aug 29 08:50 .keep_app-misc_uptimed-0
-rw-r--r-- 1 uptimed uptimed 139 Jun 23 15:50 records
-rw-r--r-- 1 uptimed uptimed 139 Jun 23 15:50 records.old
Maybe a permissions issue on the database?
The text was updated successfully, but these errors were encountered:
I've had 4 rows in my uprecords output for a long time now.
A short bit of math would tell you that the days column does not match the expected value given that the first day listed is July 17 2016. This is a VM host, so it's pretty much always up.
I'm running on gentoo. My /var/spool/uptimed directory looks like this:
Maybe a permissions issue on the database?
The text was updated successfully, but these errors were encountered: