group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1673357@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package munin - 2.0.25-2ubuntu0.16.04.4

---------------
munin (2.0.25-2ubuntu0.16.04.4) xenial; urgency=medium

  * Add patch to avoid reporting speed below 0 for network devices
    (LP: #1673357).

 -- Lucas Kanashiro <kanashiro@xxxxxxxxxx>  Mon, 20 Jul 2020 10:04:10
-0300

** Changed in: munin (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1673357

Title:
  [SRU] Munin core plugin "if_" doesn't work

Status in munin package in Ubuntu:
  Fix Released
Status in munin source package in Xenial:
  Fix Released
Status in munin source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]

  The network interface traffic metric plugin reports invalid values for
  network speed interface (negative values).

  This is the upstream fix for this issue:

  https://github.com/munin-monitoring/munin/commit/78c3c3aa

  [Test Case]

  Install munin and call the plugin checking for the network interface
  config:

  $ multipass launch -n munin-test daily:16.04
  $ multipass shell munin-test
  $ sudo apt update && sudo apt upgrade -y
  $ sudo apt install munin -y
  $ sudo munin-run if_ens4 config | tail -n 3
  up.max -1000000
  up.info Traffic of the ens4 interface. Maximum speed is -1 Mb/s.
  down.max -1000000

  
  [Regression Potential]

  The risk of a regression is quite small, it is one-line change and it
  now checks if the value is greater than 0 instead of checking for the
  size of the returned string. However, if a regression is going to
  happen it will be in the network interface traffic metric plugin, more
  specifically regarding the interface speed metric.

  [Original description]

  The munin core plugin for network interface traffic metric, "if_",
  registers invalid values on the master side because the configuration
  phase does not report valid network speed interface. Reports negative
  range (up.max is negative, while up.min is 0), and thus registers as
  NaN by the master, even though the node itself sends valid numbers:

  # munin-run if_ens3 config
  .
  .
  .
  up.min 0
  up.max -1000000
  up.info Traffic of the ens3 interface. Maximum speed is -1 Mb/s.
  down.max -1000000

  # munin-run if_ens3

  down.value 107758093
  up.value 77710387

  See also: https://github.com/mail-in-a-box/mailinabox/issues/896

  The bug has been fixed upstream:

  https://github.com/munin-
  monitoring/munin/commit/290d5ac2be02ced4d09fda68dc561fcf082c9cbf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1673357/+subscriptions