[smokeping-users] TCPPing Probe issue

[davek]

I am using TCPPing probe for a number of hosts and it works as expected
when the host is up and the port is open. If the host is offline or the
port is closed smokeping still graphs a value, 250ms. I would expect to see
no data in this case. Any ideas?

[Gregory Sloop]

It's been a billion years [ok, perhaps a few less than that] since I've has an active TCP Ping probe - but I never had that problem when I was using it, at least that I can recall.

Running smokeping in debug mode might allow you to see what's actually coming in - that may or may not be helpful.
How does your TCP ping behave when run at the CLI without smokeping? Does it produce the proper results?

Other than starting there as a troubleshooting/debug step, I don't have any other great ideas.
My gut feeling: I'm doubtful this is a smokeping issue. If I were to guess it's how your TCP probe is returning values - in a way that is either wrong or in a format that isn't as smokeping expects.

HTH

-Greg



I am using TCPPing probe for a number of hosts and it works as expected when the host is up and the port is open. If the host is offline or the port is closed smokeping still graphs a value, 250ms. I would expect to see no data in this case. Any ideas?

[davek]

so this issue is indeed with the tcpping script. I updated to a version
v2.2 i found on GitHub but that changes from tcptraceroute to traceroute,
which requires root (no good)

Here the patch for Richards tcpping script v1.7 referenced on the smokeping
website

***@SmokePingDiag:/etc/smokeping$ diff /usr/bin/tcpping ~/tcpping
80c80,84
< echo -n " $rtt"
---

if [ $rtt != "255" ]; then
echo -n " $rtt"
else
echo -n " -"
fi
I am using TCPPing probe for a number of hosts and it works as expected
when the host is up and the port is open. If the host is offline or the
port is closed smokeping still graphs a value, 250ms. I would expect to see
no data in this case. Any ideas?