Ad Widget

Collapse

Unit Issues

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • adambmedent
    Junior Member
    • Jun 2012
    • 22

    #1

    Unit Issues

    I have 4 linux servers under Template_Linux. I am trying to get an accurate reading on free space for a specific mount. 3 of the 4 servers are reporting the value in MB and one of them is reporting the value in GB. Im quite confused on how this is happening when all 4 of the servers are using the same template. Any suggestions or ideas are greatly appreciated.

    If I add a multiplyer of 1024 the 3 servers start reporting in GB, but the other server then starts reporting in TB's.

    Thanks,
    Adam
  • adambmedent
    Junior Member
    • Jun 2012
    • 22

    #2
    Originally posted by adambmedent
    I have 4 linux servers under Template_Linux. I am trying to get an accurate reading on free space for a specific mount. 3 of the 4 servers are reporting the value in MB and one of them is reporting the value in GB. Im quite confused on how this is happening when all 4 of the servers are using the same template. Any suggestions or ideas are greatly appreciated.

    If I add a multiplyer of 1024 the 3 servers start reporting in GB, but the other server then starts reporting in TB's.

    Thanks,
    Adam
    No one has any input, I would think Im either missing something quite simple or this is some type of bug.

    Comment

    • ahowell
      Member
      • Jan 2011
      • 66

      #3
      Originally posted by adambmedent
      No one has any input, I would think Im either missing something quite simple or this is some type of bug.
      Are they running the same version of Linux? Same version of agent?

      What do you get if you run this from server

      zabbix_get -s <Linux host name> -k vfs.fs.size[<file system>,free]

      It should return free space in bytes

      Comment

      • adambmedent
        Junior Member
        • Jun 2012
        • 22

        #4
        Not sure what I am missing. Do I need to be in a specific directory?

        [root@zabbix ~]# zabbix_get -s <medentvpn> -k vfs.fs.size[<file system>,free]
        -bash: medentvpn: No such file or directory

        Comment

        • JBo
          Senior Member
          • Jan 2011
          • 310

          #5
          Hi,

          Originally posted by adambmedent
          Not sure what I am missing. Do I need to be in a specific directory?

          [root@zabbix ~]# zabbix_get -s <medentvpn> -k vfs.fs.size[<file system>,free]
          -bash: medentvpn: No such file or directory
          Are you sure that your host is named <medentvpn> (with enclosing <>) ?
          You should also replace <file system> with a real file system name.
          It would probably work better with:
          Code:
          zabbix_get -s medentvpn -k vfs.fs.size[/,free]
          Regards,
          JBo

          Comment

          • adambmedent
            Junior Member
            • Jun 2012
            • 22

            #6
            The machine reporting the correct values is CentOS6. The machines reporting the incorrect values are CentOS5. Is there any known issues with the 1.4.7 CentOS5 zabbix agent?

            CentOS5 Agent Version:1.4.7
            CentOS6 Agent Version:1.8.14

            I installed both of them from yum.

            CentOS5 Machine
            [root@zabbix ~]# zabbix_get -s webmail -k vfs.fs.size[/usr/medent,free]
            181426692
            /dev/hda4 259G 73G 174G 30% /usr/medent

            CentOS6 Machine
            [root@zabbix ~]# zabbix_get -s medentvpn -k vfs.fs.size[/usr/medent,free]
            184671432704
            /dev/sda4 223G 39G 172G 19% /usr/medent

            Comment

            • JBo
              Senior Member
              • Jan 2011
              • 310

              #7
              vfs.fs.size reported size in bytes in old versions.
              Starting with 1.8, it is reported in Kbytes.

              JBo

              Comment

              • adambmedent
                Junior Member
                • Jun 2012
                • 22

                #8
                Originally posted by JBo
                vfs.fs.size reported size in bytes in old versions.
                Starting with 1.8, it is reported in Kbytes.

                JBo
                That answers it for me! Appreciate all the help guys!!

                Comment

                Working...