Unexpected Packet Loss? about smokeping-opensshmikrotikrouterosping HOT 4 OPEN

It's actually not a discrepancy but by design. I'll update the documentation. My apologies.

The default Smokeping code base creates it's RRD files to accept a 20 ping dataset (config/Database). The RRD (Round Robin Database) files are fixed in size, not like a MySQL, Postgres, Microsoft SQL and others, which grow in size. You define, in part, the RRD data file size in the Database config file. You can override that in the Probe or Target host definition. Since the RRD Update with a ping count greater than what's defined in Database or overridden in the Probe or Target host definition, will fail, at the time I just coded for the default. It's some code that needs some love. I had never had a scenario where a ping count over 20 was ever used, so adding that override was low on the list to get back to. I've got a number of new features in a private testing branch, but not ready to push today. There's a quick immediate solution. Download the source. Remove or comment the code that trims the @times array. I'll work on getting the module updated. So many "squirrel!'s" in a given day.

Lines 346-349

  my $length = @times;
  while (($length = @times) > 20) {
    pop @times;
  }

change to:

  #my $length = @times;
  #while (($length = @times) > 20) {
  # pop @times;
  #}

or

  my $length = @times;
  while (($length = @times) > 40) {
    pop @times;
  }

from smokeping-opensshmikrotikrouterosping.

Hello,

It looks as though you've resolved your original issue OpenSSH Error (Issue #9). I will close that.

As far as the packet loss, Two things. 1) I am not the developer of Smokeping and therefore cannot really dive into issues outside of the Probe Module I wrote. 2) Are you familiar with Smokeping? My experience with Smokeping is that the graph will show packet loss if there is no data for all or part of the graphs displayed period of time. If you are not seeing any missed data returned from the OpenSSHMikrotikRouterOSPing Probe, i.e. you are seeing a value for each ping request returned from the Mikrotik device in the debug log, then try to give it time for the graphs period displayed to fully populate with data and/or narrow the graphs time period to only the last few minutes of data.

Best

from smokeping-opensshmikrotikrouterosping.

Oh, no, I just disabled multiplexing for now. I intend to circle back on it once I make sure the rest of the system works as expected.

I am seeing discrepancies in the debugging data. 40 pings are performed successfully, but it looks like only 20 are sent upstream. I attached the debugging to the original post.

from smokeping-opensshmikrotikrouterosping.

I increased it from 20 to 40, and the graph now indicates 0% loss for the tests run since then.

I look forward to your update.

I know full well the effect of the squirrel.

from smokeping-opensshmikrotikrouterosping.