Hi Seth,

maybe there are different output formats in tcpping ? we had that
with fping and added compensation to the module ... just guessing.

cheers
tobi


> Hi - does anyone have any information/help on this issue?
>
> Thanks.
>
> Seth
>
> From: Seth Lyons
> Sent: Wednesday, March 03, 2010 1:52 PM
> To: '[email protected]'
> Subject: update: tcpping reporting in seconds
>
> So I went back to the original TCPPing.pm file after trying to make a few 
> modifications, and now there is no data at all in the graphs.
>
> smokeping -debug shows:
> TCPPing: Executing /usr/local/bin/tcpping -C -x 5 193.108.158.113 443
> TCPPing: TCPPing.pm: pingone: Got output: '193.108.158.113 : 8.188 8.192 
> 8.136 8.158 42.831'
> TCPPing: TCPPing.pm: pingone: Parsed times: : 8.188 8.192 8.136 8.158 42.831
>
> I included the debugging found here: 
> https://lists.oetiker.ch/pipermail/smokeping-users/2008-June/003158.html
>
> A sample of rrdtool info XXXX shows:
> ds[ping1].value = NaN
>
> Please advise.
>
> From: Seth Lyons
> Sent: Tuesday, March 02, 2010 9:39 PM
> To: [email protected]
> Subject: tcpping reporting in seconds
>
> Hi all -
>
> I saw that last March someone posted that his tcpping graphs were showing the 
> correct values, but the graph was labeled in seconds instead of milliseconds. 
>  I am now having this problem as well.  Does anyone know if it was ever 
> resolved?  One thing that is interesting to note is that the graphs for 3 
> hours, 30 hours, and 10 days are labeled in seconds, while the graph for 400 
> days is properly labeled in milliseconds.
>
> My system is:
> FreeBSD 8.0-RELEASE amd64
> tcptraceroute-devel-1.5.b7
> smokeping-2.4.2_5
> tcpping v1.7
> apache-2.2.14_5
>
> Any help is appreciated.
>
> Thanks.
>
> Seth
>

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch [email protected] ++41 62 775 9902 / sb: -9900

_______________________________________________
smokeping-users mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

Reply via email to