Ad Widget

Collapse

vfs.dev.read(write) - Not Supported after upgrade to 1.6.x

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • loshak
    Junior Member
    Zabbix Certified Specialist
    • Jun 2006
    • 21

    #1

    vfs.dev.read(write) - Not Supported after upgrade to 1.6.x

    Hi, after upgrading server and agent to v. 1.6.4 (from 1.4.5) vfs.dev.read and vfs.dev.write items are now in "Not Supported" state (on Linux - Centos 5.2).
    It looks like this:
    ---
    ./zabbix_agent_1_4_5 -t vfs.dev.write[sda2]
    vfs.dev.write[sda2] [u|2583749120]
    ---
    ./zabbix_agent_1_6_4 -t vfs.dev.write[sda2]
    vfs.dev.write[sda2] [m|Collector is not started!]
    ---
    Any suggestions?
    Thanks

    P.S.
    compile string:
    ./configure --enable-agent --enable-static
    Last edited by loshak; 07-04-2009, 18:53.
  • jroberson
    Senior Member
    • May 2008
    • 124

    #2
    Try vfs.dev.read[sda] & vfs.dev.write[sda]

    Comment

    • t2y
      Member
      • Feb 2009
      • 60

      #3
      Hi,

      Originally posted by jroberson
      Try vfs.dev.read[sda] & vfs.dev.write[sda]
      I also tried to get value. Here is my result. I want to know why this difference occurred.

      Code:
      # cat /etc/redhat-release
      CentOS release 5.3 (Final)
      # rpm -q zabbix                                          
      zabbix-1.6.4-1
      # df
      Filesystem           1K-blocks      Used Available Use% Mounted on
      /dev/sda1              7103744   5090624   1646440  76% /
      tmpfs                   257720         0    257720   0% /dev/shm
      # zabbix_agent -t vfs.dev.write[sda]
      vfs.dev.write[sda]                            [m|Collector is not started!]
      # zabbix_agent -t vfs.dev.write[sda1]
      vfs.dev.write[sda1]                           [m|Collector is not started!]
      # zabbix_agent -t vfs.dev.read[sda]
      vfs.dev.read[sda]                             [m|Collector is not started!]
      # zabbix_agent -t vfs.dev.read[sda1]
      vfs.dev.read[sda1]                            [m|Collector is not started!]
      Code:
      # cat /etc/asianux-release
      Asianux Server 3 (Quartet SP1)
      # rpm -q zabbix-agent
      zabbix-agent-1.4.6-1AXS3
      # df
      Filesystem           1K-blocks      Used Available Use% Mounted on
      /dev/sda1              7103744   5054880   1682184  76% /
      tmpfs                   257768         0    257768   0% /dev/shm
      # zabbix_agent -t vfs.dev.write[sda]
      vfs.dev.write[sda]                            [u|1210633720]
      # zabbix_agent -t vfs.dev.write[sda1]
      vfs.dev.write[sda1]                           [u|1210625896]
      # zabbix_agent -t vfs.dev.read[sda]
      vfs.dev.read[sda]                             [u|7952137]
      # zabbix_agent -t vfs.dev.read[sda1]
      vfs.dev.read[sda1]                            [u|7950138]

      Comment

      • loshak
        Junior Member
        Zabbix Certified Specialist
        • Jun 2006
        • 21

        #4
        Tried that.... it doesn't meter sda or sdaX.... result is always the same.
        ./zabbix_agent_1_4_5 -t vfs.dev.write[sda]
        vfs.dev.write[sda] [u|3097483148]
        ./zabbix_agent_1_6_4 -t vfs.dev.write[sda]
        vfs.dev.write[sda] [m|Collector is not started!]

        Comment

        • jroberson
          Senior Member
          • May 2008
          • 124

          #5
          I get the same thing when I use the "zabbix_agent -t" command with 1.6.x. Try
          Code:
           zabbix_get -s localhost -k vfs.dev.write[sda]
          I have seen evidence that the "zabbix_agent -t" does not work on recent versions.

          Comment

          • ittec
            Member
            • Mar 2008
            • 73

            #6
            Bad luck

            Hi all

            I have tested vfs.dev.write[sda] without success.

            Kernel:2.6.18-028stab070.4
            Zabbix Server: 1.8.3
            Zabbix Agetnd: 1.8.3
            CentOS release 5.5 (Final)
            # ./zabbix_get -s localhost -k vfs.dev.read[sda]
            no output


            Wow, im very frustated. :S

            Comment

            Working...