[smokeping-users] empty graph for DNS.pm and TCPPing.pm
Xuefer
xuefer at gmail.com
Thu Feb 21 06:32:29 CET 2019
i did try --debug but failed to figure out what's wrong. i thought i
copied pasted the output, LOL, must have been thinking too many
things. here we go:
====================== BEFORE fix:
# chpst -u smokeping smokeping --debug
### assuming you are using an tcpping copy reporting in milliseconds
### assuming you are using an tcpping copy reporting in milliseconds
### parsing /etc/smokeping/fast-cli output... OK (version 0.0.1)
Smokeping version 2.006009 successfully launched.
Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that.
PingNormal: probing 0 targets with step 300 s and offset 181 s.
Curl_fast_com: probing 0 targets with step 1200 s and offset 181 s.
Curl_small: probing 0 targets with step 60 s and offset 181 s.
PingFreq: probing 1 targets with step 10 s and offset 181 s.
PingFreq: forks 5, timeout for each target 181
PingFreq: Executing /etc/smokeping/tcpping -C -x 3 58.60.9.21
PingFreq: Received: GLOB(0x1bbb6b8)
PingFreq: 58.60.9.21: got 7.3530000000e-03 7.3670000000e-03 8.4730000000e-03
Calling RRDs::update(/var/lib/smokeping/Global/qq-com.rrd --template
uptime:loss:median:ping1:ping2:ping3
1550726988:U:0:7.3670000000e-03:7.3530000000e-03:7.3670000000e-03:8.4730000000e-03)
====================== AFTER fix:
# chpst -u smokeping smokeping --debug
### assuming you are using an tcpping copy reporting in milliseconds
### assuming you are using an tcpping copy reporting in milliseconds
### parsing /etc/smokeping/fast-cli output... OK (version 0.0.1)
Smokeping version 2.006009 successfully launched.
Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that.
Curl_small: probing 0 targets with step 60 s and offset 212 s.
PingFreq: probing 1 targets with step 10 s and offset 212 s.
PingNormal: probing 0 targets with step 300 s and offset 212 s.
Curl_fast_com: probing 0 targets with step 1200 s and offset 212 s.
PingFreq: forks 5, timeout for each target 181
PingFreq: Executing /etc/smokeping/tcpping -C -x 3 58.60.9.21
PingFreq: Received: GLOB(0x1bba328)
PingFreq: 58.60.9.21: got 0.0070280000 0.0073690000 0.0080560000
Calling RRDs::update(/var/lib/smokeping/Global/qq-com.rrd --template
uptime:loss:median:ping1:ping2:ping3
1550727004:U:0:0.0073690000:0.0070280000:0.0073690000:0.0080560000)
====================== FPing don't need fix:
# chpst -u smokeping smokeping --debug
### parsing /etc/smokeping/fast-cli output... OK (version 0.0.1)
Smokeping version 2.006009 successfully launched.
Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that.
Curl_small: probing 0 targets with step 60 s and offset 292 s.
PingNormal: probing 0 targets with step 300 s and offset 292 s.
PingFreq: probing 1 targets with step 10 s and offset 292 s.
Curl_fast_com: probing 0 targets with step 1200 s and offset 292 s.
PingFreq: Executing /etc/smokeping/fping -C 3 -q -B1 -r1 -t60000 -i10 58.60.9.21
PingFreq: Got fping output: '58.60.9.21 : 5.91 5.69 8.00'
Calling RRDs::update(/var/lib/smokeping/Global/qq-com.rrd --template
uptime:loss:median:ping1:ping2:ping3
1550727021:U:0:5.9100000000e-03:5.6900000000e-03:5.9100000000e-03:8.0000000000e-03)
======================
%e a floating-point number, in scientific notation
%f a floating-point number, in fixed decimal notation
but i suppose rrdtool accept scientific notation
# rrdtool --version
RRDtool 1.6.01.6.0 Copyright by Tobias Oetiker <tobi at oetiker.ch>
Compiled Feb 7 2019 00:14:34
the above log were reproduced under system: gentoo
i can also reproduce it in in openwrt
On Thu, Feb 21, 2019 at 1:14 PM Gabriel Filion <gabster at lelutin.ca> wrote:
>
> On 2019-02-21 12:12 a.m., Gabriel Filion wrote:
> > On 2019-02-20 12:52 p.m., Xuefer wrote:
> >> FPing.pm works fine but DNS and TCPPing is producing empty graph. i
> >> failed to find the actual clause since i'm not a perl guy, but i
> >> manage to workaround it by changnig "%.10e" into ".10f", can any
> >> developer take a look into this?
> >
> > you should start smokeping with the --daemon argument to get more
>
> oops sorry I'm too tired to type :\ that should have been --debug (not
> --daemon)
>
> > information. it'll show you what commands it's running, but also the
> > probe binary's output if it's erroring out.
> >
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
More information about the smokeping-users
mailing list