Thanks for clearing that up.
Appears to be working now, interesting spikes to show my ISP.
Any chance we can give it a list of servers?
My city has 4 Speedtest servers and it would be nice to get a hit off
each every hour and have a combined graph of all servers instead of
just one.
-S
*From:*Adrian Popa [mailto:[email protected]]
*Sent:* Monday, October 12, 2015 7:37 PM
*To:* STR . <[email protected]>; [email protected]
*Subject:* Re: [smokeping-users] New probe speedtest
Thanks for posting.
Now I remember what else I changed:
This is from rrdtool info:
ds[ping1].index = 3
ds[ping1].type = "GAUGE"
ds[ping1].minimal_heartbeat = 7200
ds[ping1].min = 0.0000000000e+00
ds[ping1].max = 1.8000000000e+02
ds[ping1].last_ds = "0.0000000000e+00"
ds[ping1].value = 0.0000000000e+00
ds[ping1].unknown_sec = 0
As you can see, default RRDs are created with a max value of 180. This
means that values higher than 180 will be ignored.
I submitted a patch that was included in the official GIT repository
to remove this limit:
https://github.com/oetiker/SmokePing/commit/60419834f224a0735094fd4ad0aac8eac3b15289
Make the same change, delete the old RRDs and restart smokeping.
Good luck.
I will post this info in the project's readme...
On 10/12/15 14:10, STR . wrote:
Yes, the graphs are empty in both overview and detail pages.
Here are the RRDs:
https://dl.dropboxusercontent.com/u/314525/upload_to_Tata_Technologies_Pune.rrd
https://dl.dropboxusercontent.com/u/314525/download_from_Tata_Technologies_Pune.rrd
Thanks,
S
*From:*Adrian Popa [mailto:[email protected]]
*Sent:* Monday, October 12, 2015 4:18 PM
*To:* STR . <[email protected]> <mailto:[email protected]>;
[email protected]
<mailto:[email protected]>
*Subject:* Re: [smokeping-users] New probe speedtest
Strange... So, the graphs are empty both in overview and when
clicking on them to view details, right? The max_rtt setting only
affects the graphs viewed in overview. I will try to remember if I
changed anything else in smokeping's code, but I don't think so...
Can you share a rrd file/graph?
On 10/12/15 12:01, STR . wrote:
Thanks for clearing that up.
I had it configured correctly including max_rtt and its been a
few days but the graphs are empty/nan after a few days.
Obviously things are written to the rrd, I’m at a loss to
understand why the graphs show up empty.
Here are the relevant bits from my configuration:
/opt/smokeping/etc/config:
+ overview
width = 600
height = 50
range = 10h
max_rtt = 1000000000
*** Probes ***
+ speedtest
binary = /usr/bin/speedtest-cli
timeout = 300
step = 3600
offset = random
pings = 3
++ speedtest-download
measurement = download
++ speedtest-upload
measurement = upload
*** Targets ***
+ download_from_Tata_Technologies_Pune
menu = Speedtest download
title = download_from_Tata_Technologies_Pune
probe = speedtest-download
server = 6344
measurement = download
host = wrt.asuscomm.com
+ upload_to_Tata_Technologies_Pune
menu = Speedtest upload
title = upload_to_Tata_Technologies_Pune
probe = speedtest-upload
server = 6344
measurement = upload
host = wrt.asuscomm.com
Thanks,
S
*From:*smokeping-users
[mailto:[email protected]]
*On Behalf Of *Adrian Popa
*Sent:* Thursday, October 8, 2015 4:34 PM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [smokeping-users] New probe speedtest
Hello STR,
The Host is not used internally - you can set it to whatever
you like.
I can see you're running tests every hour. In order to see
data graphed, you need to wait for at least 2 polling
intervals to complete, so you'd see data only in the third hour.
One more thing, smokeping is designed to drop data that is
very large in value to prevent spikes from error readings. You
can disable this by setting this in the overview section (see
the readme):
|+overview|
|max_rtt = 1000000000|
On 10/07/15 10:40, STR . wrote:
Hi,
Interesting plugin, what is the value of host? The hostname the
smokeping
probe is launched from?
"host = dummy.com"
I see rrd updates but my graphs are empty/nan.
Snipped output below:
root@slack14:~# /opt/smokeping/bin/smokeping --debug
### parsing /usr/bin/speedtest-cli output... OK (version 0.3.4)
### parsing /usr/bin/speedtest-cli output... OK (version 0.3.4)
### parsing dig output...OK
Smokeping version 2.006011 successfully launched.
Not entering multiprocess mode with '--debug'. Use '--debug-daemon'
for
that.
speedtest-download: probing 1 targets with step 3600 s and offset
19 s.
speedtest-upload: probing 1 targets with step 3600 s and offset 19
s.
speedtest-download: forks 5, timeout for each target 901
speedtest-download: query=/usr/bin/speedtest-cli --server 6344 --simple
2>&1
speedtest-download: output: Ping: 42.967 ms
speedtest-download: output: Download: 7.96 Mbit/s
speedtest-download: Got value: 7.96, unit: Mbit/s -> 7960000
speedtest-download: time=7.9600000000e+06 7.9600000000e+06
7.9600000000e+06
speedtest-download: wrt.asuscomm.com: got 7.9600000000e+06
7.9600000000e+06
7.9600000000e+06
speedtest-upload: forks 5, timeout for each target 901
speedtest-upload: query=/usr/bin/speedtest-cli --server 6344 --simple
2>&1
speedtest-upload: output: Ping: 37.56 ms
speedtest-upload: output: Download: 6.66 Mbit/s
speedtest-upload: output: Upload: 0.37 Mbit/s
speedtest-upload: Got value: 0.37, unit: Mbit/s -> 370000
speedtest-upload: time=3.7000000000e+05 3.7000000000e+05
3.7000000000e+05
speedtest-upload: wrt.asuscomm.com: got 3.7000000000e+05
3.7000000000e+05
3.7000000000e+05
Calling
RRDs::update(/opt/smokeping/htdocs/data/download_from_Tata_Technologies_Pune
.rrd --template uptime:loss:median:ping1:ping2:ping3
1444202889:U:0:7.9600000000e+06:7.9600000000e+06:7.9600000000e+06:7.96000000
00e+06)
Calling
RRDs::update(/opt/smokeping/htdocs/data/upload_to_Tata_Technologies_Pune.rrd
--template uptime:loss:median:ping1:ping2:ping3
1444202889:U:0:3.7000000000e+05:3.7000000000e+05:3.7000000000e+05:3.70000000
00e+05)
So RRD appears to be updated but I don't see it log what the issue
may be
even with debug enabled, the graphs are all empty/nan.
Here's snipped debug plugin output:
Oct 7 11:53:12 slack14 speedtest[24762]: Init: version 0.3.4
Oct 7 11:53:12 slack14 speedtest[24762]: Init: version 0.3.4
Oct 7 11:54:59 slack14 smokeping[24789]:
query=/usr/bin/speedtest-cli
--server 6344 --simple 2>&1
Oct 7 11:55:59 slack14 smokeping[24789]: output: Ping: 60.647 ms
Oct 7 11:55:59 slack14 smokeping[24789]: output: Download: 3.07
Mbit/s
Oct 7 11:55:59 slack14 smokeping[24789]: output: Upload: 0.37
Mbit/s
Oct 7 11:55:59 slack14 smokeping[24789]: Got value: 0.37, unit:
Mbit/s ->
370000
Oct 7 11:55:59 slack14 smokeping[24789]: time=3.7000000000e+05
3.7000000000e+05 3.7000000000e+05
Oct 7 12:44:32 slack14 smokeping[29972]:
query=/usr/bin/speedtest-cli
--server 6344 --simple 2>&1
Oct 7 12:45:35 slack14 smokeping[29972]: output: Ping: 59.49 ms
Oct 7 12:45:35 slack14 smokeping[29972]: output: Download: 8.03
Mbit/s
Oct 7 12:45:35 slack14 smokeping[29972]: Got value: 8.03, unit:
Mbit/s ->
8030000
Oct 7 12:45:35 slack14 smokeping[29972]: time=8.0300000000e+06
8.0300000000e+06 8.0300000000e+06
Oct 7 12:55:38 slack14 speedtest[31340]: Init: version 0.3.4
Oct 7 12:55:38 slack14 speedtest[31340]: Init: version 0.3.4
Oct 7 12:55:38 slack14 speedtest[31416]:
query=/usr/bin/speedtest-cli
--server 6344 --simple 2>&1
Oct 7 12:56:24 slack14 speedtest[31416]: output: Ping: 42.967 ms
Oct 7 12:56:24 slack14 speedtest[31416]: output: Download: 7.96
Mbit/s
Oct 7 12:56:24 slack14 speedtest[31416]: Got value: 7.96, unit:
Mbit/s ->
7960000
Oct 7 12:56:24 slack14 speedtest[31416]: time=7.9600000000e+06
7.9600000000e+06 7.9600000000e+06
Oct 7 12:56:33 slack14 speedtest[31635]:
query=/usr/bin/speedtest-cli
--server 6344 --simple 2>&1
Oct 7 12:57:26 slack14 speedtest[31635]: output: Ping: 37.56 ms
Oct 7 12:57:26 slack14 speedtest[31635]: output: Download: 6.66
Mbit/s
Oct 7 12:57:26 slack14 speedtest[31635]: output: Upload: 0.37
Mbit/s
Oct 7 12:57:26 slack14 speedtest[31635]: Got value: 0.37, unit:
Mbit/s ->
370000
Oct 7 12:57:26 slack14 speedtest[31635]: time=3.7000000000e+05
3.7000000000e+05 3.7000000000e+05
It did log this in one of the runs when I left it running overnight:
Oct 6 12:01:16 slack14 speedtest[35113]: output: Traceback (most
recent
call last):
Oct 6 12:01:16 slack14 speedtest[35113]: output: File
"/usr/bin/speedtest-cli", line 11, in <module>
Oct 6 12:01:16 slack14 speedtest[35113]: output:
sys.exit(main())
Oct 6 12:01:16 slack14 speedtest[35113]: output: File
"/usr/lib64/python2.7/site-packages/speedtest_cli.py", line 790, in
main
Oct 6 12:01:16 slack14 speedtest[35113]: output: speedtest()
Oct 6 12:01:16 slack14 speedtest[35113]: output: File
"/usr/lib64/python2.7/site-packages/speedtest_cli.py", line 631, in
speedtest
Oct 6 12:01:16 slack14 speedtest[35113]: output: servers =
closestServers(config['client'], True)
Oct 6 12:01:16 slack14 speedtest[35113]: output: File
"/usr/lib64/python2.7/site-packages/speedtest_cli.py", line 436, in
closestServers
Oct 6 12:01:16 slack14 speedtest[35113]: output:
serversxml.append(uh.read(10240))
Oct 6 12:01:16 slack14 speedtest[35113]: output: File
"/usr/lib64/python2.7/socket.py", line 380, in read
Oct 6 12:01:16 slack14 speedtest[35113]: output: data =
self._sock.recv(left)
Oct 6 12:01:16 slack14 speedtest[35113]: output: File
"/usr/lib64/python2.7/httplib.py", line 567, in read
Oct 6 12:01:16 slack14 speedtest[35113]: output: s =
self.fp.read(amt)
Oct 6 12:01:16 slack14 speedtest[35113]: output: File
"/usr/lib64/python2.7/socket.py", line 380, in read
Oct 6 12:01:16 slack14 speedtest[35113]: output: data =
self._sock.recv(left)
Oct 6 12:01:16 slack14 speedtest[35113]: output: socket.timeout:
timed out
I'm not sure why graphs are generated.
Thanks,
S
-----Original Message-----
From: smokeping-users
[mailto:[email protected]] On
Behalf Of Adrian Popa
Sent: Monday, October 5, 2015 1:47 PM
To: Pacheco Bravo, Dago Javier<[email protected]>
<mailto:[email protected]>;
[email protected]
<mailto:[email protected]>
Subject: Re: [smokeping-users] New probe speedtest
The instructions can be found here:
https://github.com/mad-ady/smokeping-speedtest
The actual plugin (which needs to go in your probes dir - e.g
/opt/smokeping/lib/Smokeping/probes/ ) is here:
https://raw.githubusercontent.com/mad-ady/smokeping-speedtest/master/speedte
st.pm
Read the instructions and if you get stuck tell us what the problem
is.
I haven't had time to work out the bugs of this plugin and push it
upstream
- sorry. Maybe I will have time one day to polish it and include it
with the
official plugins
On 10/02/15 15:09, Pacheco Bravo, Dago Javier wrote:
Hello Adrian,
Thanks for this probe. I'm trying to enable it form my
smokeping
installation but I really don't know where can I get de
speedtest.pm file
you mention on installation instructions.
Can you help me with this?
Bye,
Dago
-----Mensaje original-----
De: smokeping-users
[mailto:[email protected]] En
nombre de Adrian Popa Enviado el: jueves, 11 de junio de 2015
5:42
Para:[email protected]
<mailto:[email protected]>
Asunto: [smokeping-users] New probe speedtest
Hello everyone,
I'd like to share with you a new probe I've been working on -
integrating
speedtest-cli project to work with smokeping. The idea was that we
needed to
run some tests to get the customer's "experience" when using
speedtest.net
with different test servers. We developed this probe, and measure
the
upload/download rate the client's connection supports.
Plugin description and examples are here:
https://github.com/mad-ady/smokeping-speedtest
There is a bit of a deviation from standard plugins - meaning
it ignores
the pings variable and does only one test. This was done in order
to prevent
the IP getting banned for too agressive behavior by the
speedtest.net
servers. It can be reactivated - I'm open to ideas.
Here's a sample graph from a slave probe (1 hour polling):
http://imgur.com/cTJdHCS
@tobi: if you feel this plugin could be useful and should be
included in
the main release, let me know and I'll see how I can merge it...
Feedback welcome,
Regards,
Adrian
_______________________________________________
smokeping-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
--
TELEKOM ROMANIA
Adrian Popa
Expert Engineer
Applications, Security & EMS
35-37 Calea Victoriei, Palatul Telefoanelor
Mobile: +40 766 673 290
Phone: +40 21 400 7567
_______________________________________________
smokeping-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
_______________________________________________
smokeping-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
.
--
TELEKOM ROMANIA
Adrian Popa
Expert Engineer
Applications, Security & EMS
35-37 Calea Victoriei, Palatul Telefoanelor
Mobile: +40 766 673 290
Phone: +40 21 400 7567
--
TELEKOM ROMANIA
Adrian Popa
Expert Engineer
Applications, Security & EMS
35-37 Calea Victoriei, Palatul Telefoanelor
Mobile: +40 766 673 290
Phone: +40 21 400 7567
--
TELEKOM ROMANIA
Adrian Popa
Expert Engineer
Applications, Security & EMS
35-37 Calea Victoriei, Palatul Telefoanelor
Mobile: +40 766 673 290
Phone: +40 21 400 7567
