-
-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ss_fping.php script times out when there is a lot of packet loss #5221
Comments
yea, that's the whole problem with doing Advanced ping in Cacti.
Adding @xmacan and @thurban to the thread. I know they've got some other solutions. I would do some of this "stuff" Async myself and write a plugin to store it in a table :) But then, I would need time to write it ;) |
@jdcoats are these icmp pings? If so, do you have a problem maybe pinging the ssh port instead? ICMP relies on the 'ping' command which does not have a sub-second timeout. Best to use the TCP or UDP. Also, watch the Script Timeout in Cacti. If it's too high, everything start to break. The other enhancement is maybe instead of inserting "0" we insert "U". I like the second half. That way we could add an area fill to show when the host was down. That would be a nice 1.3.0 feature enhancement. |
Maybe what web need to do is exit after two failed ping attempts. |
This version of the script will exit if more than 25% of ping sweeps failed. |
@jdcoats any update? |
I will try to confirm this tomorrow, sorry for the delay |
now if only i could force some packet loss :) |
😂 |
I'm going to defer this to 1.3.x as 1.2.x is EODL. |
This fix should work pretty well when Cacti starts using the `fping` binary now.
Okay, this should be resolved now in the develop branch. |
When monitoring using Advanced Ping and there is significant packet loss happening instead of recording it I get script server timeouts and broken graphs instead documented latency or loss. Also note the bad line breaks in the log.
Example
Pinging 104.170.44.161 with 32 bytes of data:
Reply from 104.170.44.161: bytes=32 time=51ms TTL=120
Request timed out.
Request timed out.
Reply from 104.170.44.161: bytes=32 time=52ms TTL=120
Request timed out.
Request timed out.
Reply from 104.170.44.161: bytes=32 time=52ms TTL=120
Reply from 104.170.44.161: bytes=32 time=51ms TTL=120
Request timed out.
Request timed out.
Request timed out.
Reply from 104.170.44.161: bytes=32 time=51ms TTL=120
Reply from 104.170.44.161: bytes=32 time=52ms TTL=120
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 104.170.44.161: bytes=32 time=51ms TTL=120
Request timed out.
Request timed out.
Request timed out.
Reply from 104.170.44.161: bytes=32 time=52ms TTL=120
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 104.170.44.161: bytes=32 time=50ms TTL=120
Request timed out.
Reply from 104.170.44.161: bytes=32 time=52ms TTL=120
The text was updated successfully, but these errors were encountered: