Ad Widget

Collapse

Invalid received value for net.if.in and net.if.out

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • capi
    Junior Member
    • Apr 2012
    • 2

    #1

    Invalid received value for net.if.in and net.if.out

    Hi,

    I face some invalid values on net.if.in and net.if.out keys when monitoring my server boxes. All those servers are debian 5 vms on vmware.

    In the server logs I have all those messages :
    Type of received value [3408684542354] is not suitable for value type [Numeric (float)]

    When I show interfaces statistics with ifconfig, I obtain data in TiB scale as you can see above.

    And 3 408 684 542 354 seems to be larger than a float can manage or a int to float conversion.

    ifconfig stats on one box :


    Those values seems to be incremental with time, perhaps total bytes since last boot up of the box.

    eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
    inet adr:xx.xx.xx.xx Bcast:xx.xx.xx.xx Masque:255.255.255.0
    adr inet6: xxxx::xxxx:xxxx:xxxx:16/64 Scope:Lien
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:6840279511 errors:0 dropped:0 overruns:0 frame:0
    TX packets:6124037849 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 lg file transmission:1000
    RX bytes:5466201576721 (4.9 TiB) TX bytes:2382616293066 (2.1 TiB)

    lo Link encap:Boucle locale
    inet adr:127.0.0.1 Masque:255.0.0.0
    adr inet6: ::1/128 Scope:Hôte
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:165956150 errors:0 dropped:0 overruns:0 frame:0
    TX packets:165956150 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 lg file transmission:0
    RX bytes:285330899234 (265.7 GiB) TX bytes:285330899234 (265.7 GiB)

    Are there any solutions to have those values accepted ? Is this a bug ? Or bad configurations ?

    Best regards
  • capi
    Junior Member
    • Apr 2012
    • 2

    #2


    Fixed in 1.8.3 version

    Debian squeeze still using 1.8.2 ...

    Regards

    Comment

    • vesa
      Junior Member
      • Apr 2012
      • 8

      #3
      Originally posted by capi
      https://support.zabbix.com/browse/ZBX-1126

      Fixed in 1.8.3 version

      Debian squeeze still using 1.8.2 ...

      Regards
      Ah yes, I have the same problem. What would be the best way to upgrade from 1.8.3 to for example 1.8.5? Maybe adding backports repo or something like that? Tips appreciated.

      Comment

      • vesa
        Junior Member
        • Apr 2012
        • 8

        #4
        Originally posted by vesa
        Ah yes, I have the same problem. What would be the best way to upgrade from 1.8.3 to for example 1.8.5? Maybe adding backports repo or something like that? Tips appreciated.
        I'll just patch the package, I'll post fix later.

        Comment

        • vesa
          Junior Member
          • Apr 2012
          • 8

          #5
          Originally posted by vesa
          I'll just patch the package, I'll post fix later.
          Ok here we go. You should create package on virtual machine or something because you need to install lots of packages and you don't need them on your production server.



          as root:
          apt-get install dpkg-dev
          apt-get install devscripts
          apt-get build-dep zabbix

          user:
          apt-get source zabbix

          cd zabbix/rc/libs/zbxsysinfo/
          edit sysinfo.c

          - register double pg_min_numeric = (double)-1E12;
          - register double pg_max_numeric = (double)1E12;
          + register double pg_min_numeric = (double)-1E16;
          + register double pg_max_numeric = (double)1E16;

          Replace 1E12 -> 1E16 and save.

          Now change its "version" in zabbix dir.

          debchange -v 1.8.2.2

          then run in the same dir

          dpkg-buildpackage -rfakeroot

          and voila.. you can upload zabbix-server-pgsql to your production server and run

          dpkg -i zabbix-server-pgsql

          and it is working.

          Comment

          Working...