severity 654830 minor tags 654830 upstream quit Hi,
The uptime percentage and dowtime values are bogus, upstream is aware of that and I believe they will be removed in the next release. The double entry is puzzling though, thanks for reporting. I wonder if that's just the addition of the current exact uptime at the moment you ran uprecords which tops out max recorded uptime + the display of the last recorded highest uptime. Need to check the code. On Fri, Jan 6, 2012 at 12:59 AM, Axel Beckert <a...@debian.org> wrote: > Package: uptimed > Version: 1:0.3.16-3.2 > Severity: normal > > Hi, > > on a netbook which I suspend to RAM quite often (not sure if that's > relevant :-), I found the following strange output of uprecords: > > $ uprecords > # Uptime | System Boot up > ----------------------------+-------------------------------------------------- > -> 1 6 days, 05:04:09 | Linux 3.2.0-rc7-amd64 Fri Dec 30 19:42:06 > 2011 > 2 6 days, 05:03:35 | Linux 3.2.0-rc7-amd64 Fri Dec 30 19:42:10 2011 > 3 1 day , 09:16:42 | Linux 3.1.0-1-amd64 Fri Dec 23 03:26:52 2011 > 4 1 day , 05:32:43 | Linux 3.2.0-rc4-amd64 Sat Dec 24 12:43:57 2011 > 5 0 days, 19:12:32 | Linux 3.2.0-rc7-amd64 Thu Dec 29 23:09:59 2011 > 6 0 days, 05:43:05 | Linux 3.1.0-1-amd64 Thu Dec 22 21:25:32 2011 > 7 0 days, 01:42:10 | Linux 3.2.0-rc4-amd64 Wed Dec 28 21:52:54 2011 > 8 0 days, 01:08:25 | Linux 3.2.0-rc4-amd64 Thu Dec 29 15:50:37 2011 > 9 0 days, 00:51:51 | Linux 3.2.0-rc7-amd64 Thu Dec 29 16:59:50 2011 > 10 0 days, 00:35:10 | Linux 3.2.0-rc4-amd64 Tue Dec 27 04:04:43 2011 > ----------------------------+-------------------------------------------------- > NewRec 0 days, 00:00:33 | since Fri Jan 6 00:45:41 > 2012 > up 16 days, 06:36:17 | since Thu Dec 22 21:25:32 2011 > down -2 days, -03:-16:- | since Thu Dec 22 21:25:32 2011 > %up 115.108 | since Thu Dec 22 21:25:32 2011 > > The first entry seems to be duplicated more or less, leading to wrong > uptime percentage (115%) and wrong downtime (-2 days). > > I though can't find this duplicated entry in the > /var/spool/uptimed/records file, so I suspect a bug in the statistics > part of uprecords: > > $ cat /var/spool/uptimed/records > 536855:1325270530:Linux 3.2.0-rc7-amd64 > 119802:1324607212:Linux 3.1.0-1-amd64 > 106363:1324727037:Linux 3.2.0-rc4-amd64 > 69152:1325196599:Linux 3.2.0-rc7-amd64 > 20585:1324585532:Linux 3.1.0-1-amd64 > 6130:1325105574:Linux 3.2.0-rc4-amd64 > 4105:1325170237:Linux 3.2.0-rc4-amd64 > 3111:1325174390:Linux 3.2.0-rc7-amd64 > 2110:1324955083:Linux 3.2.0-rc4-amd64 > 802:1324833446:Linux 3.2.0-rc4-amd64 > 753:1325056802:Linux 3.2.0-rc4-amd64 > $ > > -- System Information: > Debian Release: wheezy/sid > APT prefers unstable > APT policy: (990, 'unstable'), (900, 'testing'), (110, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-rc7-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages uptimed depends on: > ii debconf [debconf-2.0] 1.5.41 > ii libc6 2.13-24 > ii libuptimed0 1:0.3.16-3.2 > > uptimed recommends no packages. > > uptimed suggests no packages. > > -- debconf information: > uptimed/mail/do_mail: Never > uptimed/mail/address: root@localhost > uptimed/mail/milestones_info: > uptimed/maxrecords: 50 > uptimed/interval: 60 > > -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
