I've also encountered this bug in current release of CentOS 7.4.1708
(3.10.0-693.11.1.el7.x86_64).
I'm running uptimed on a few units as well (Ubuntu 17.10 4.13.0-16-generic &
MacOSX 10.11.6 [15G17023] 15.6.0) - and I havn't had any problems with negative
uptime reports from those.
This problem/bug must be something that isn't always showing, since it hasnt
been fixed yet. I believe there's something 'else' that is interacting when it
shouldn't - that isn't something default in the system. I hope we, or someone,
can get to the bottom of this problem.
Thank you.
# Uptime | System Boot up
----------------------------+---------------------------------------------------
1 62 days, 04:57:20 | Linux 3.10.0-693.2.2.el7 Sat Sep 30 10:45:46 2017
2 10 days, 21:01:42 | Linux 3.10.0-693.5.2.el7 Fri Dec 1 14:41:04 2017
-> 3 4 days, 00:17:23 | Linux 3.10.0-693.11.1.el Tue Dec 12 11:45:33 2017
4 4 days, 00:17:11 | Linux 3.10.0-693.11.1.el Tue Dec 12 11:42:55 2017
----------------------------+---------------------------------------------------
1up in 6 days, 20:44:20 | at Sat Dec 23 08:47:15 2017
no1 in 58 days, 04:39:58 | at Mon Feb 12 16:42:53 2018
up 81 days, 02:33:36 | since Sat Sep 30 10:45:46 2017
down -4 days, 00:-16:-26 | since Sat Sep 30 10:45:46 2017
%up 105.203 | since Sat Sep 30 10:45:46 2017
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498439
Title:
uprecords reports >100% uptime
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/uptimed/+bug/498439/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
