pcp
[Top] [All Lists]

Re: [pcp] qa/842 - another pmiostat/python issue

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] qa/842 - another pmiostat/python issue
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 17 Mar 2016 18:36:00 -0400 (EDT)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <56EA1B2B.106@xxxxxxxxxxxxxxxx>
References: <56EA1B2B.106@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: pwW5blOtHpeGVaP2uN1pGkPHaYOd6g==
Thread-topic: qa/842 - another pmiostat/python issue

----- Original Message -----
> This time on FreeBSD (with the struct timeval tv_sec fix in place, although
> that won't have changed anything because the type remains c_long here) ...
> 
> Timestamps and no headers
> Fri Aug  1 14:34:51 2014 sda              0.0     0.0    0.0    0.0      0.0
> 0.0     0.00     0.00     0.0     0.0     0.0   0.0
> Fri Aug  1 14:34:51 2014 sdb              0.0     0.0    5.0    6.0     24.0
> 8.0     2.91     0.00     0.4     0.4     0.3   0.4
> Fri Aug  1 04:34:52 2014 sda              0.0     0.0   24.0    0.0    816.0
> 0.0    34.00     0.23     9.6     9.6     0.0  19.0
> Fri Aug  1 04:34:52 2014 sdb              5.0     0.0 1308.0    5.0  53363.0
> 7.0    40.65     1.15     0.9     0.9     0.2  61.1
> Fri Aug  1 04:34:53 2014 sda              0.0     0.0    7.0    0.0    517.0
> 0.0    73.86     0.09    12.1    12.1     0.0   6.2
> 
> This is all correct EXCEPT the time spontaneously changes from 14 hr to 04 hr
> after the 2nd sample ... and stays at 04 hr for the rest of the archive.
> 
> 14 is correct, 10 is wrong.
> 
> I have no clue on this one!
> 

Bizarre - I wonder if this is reproducible with pmval or something simpler?
AFAICT, src/pcp/iostat/pcp-iostat.py is using pmCtime and has done all the
same timezone-setting steps (via pmGetOptions) that the C tools would do.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>