Details

      Description

      I monitor 1 vSphere 5.1 site directly from server, 2 vSphere 5.1 sites via proxies and 10 standalone ESXi 5.1. There are over 250 VMs and over 20 hosts.

      In period with ~1 hours i see that count of unsupported items for vmware hosts increasing very much. This looks in 5-10 minutes and then decrease back. When it increasing, CURL error shown in sever log like that: "Item beaCannot set cURL option [10015]: Timeout was reached" and simply "Timeout was reached". Example:

      "17185:20140129:143255.360 item [5005be02-9556-753b-0627-e91dd850ba2c:vmware.vm.vfs.fs.size[{$URL},{HOST.HOST},/home,total]] became not supported: a timeout was reached"

      My server works on CentOS installed in VMWare VM that running on BL460c G8 server. VM have 10GB of RAM, 2 vCPU and storage on SAN SAS10K disks. DB is MySQL, running on the same server. DB is optimized for innodb_file_per_table

      Proxies runs on the same hardware configuration, but have 2GB of RAM.

      I don't see that CPU, memory or disk I/O overloaded on server or proxies when error appears.

      This error appears only with VMWare hosts, vcenters and vms.

        Issue Links

          Activity

          Hide
          Evgeny Molchanov added a comment -

          –°onfirm the problem. I have VMware vSphere 5.1 (on Windows) and vSphere 5.5 (on Linux).
          VMware on vSphere 5.1 (on Windows) - no problems, the data arrives without interruption.
          vSphere 5.5 (on Linux) periodically get an error "Timeout was reached" when receiving data.

          Show
          Evgeny Molchanov added a comment - –°onfirm the problem. I have VMware vSphere 5.1 (on Windows) and vSphere 5.5 (on Linux). VMware on vSphere 5.1 (on Windows) - no problems, the data arrives without interruption. vSphere 5.5 (on Linux) periodically get an error "Timeout was reached" when receiving data.
          Hide
          Henrik Johansen added a comment - - edited

          Same issue here - and it looks like the timeout value is hardcoded and cannot be changed using the server / proxy config file ?

          After upgrading to 2.2.2 the issue persists.

          Show
          Henrik Johansen added a comment - - edited Same issue here - and it looks like the timeout value is hardcoded and cannot be changed using the server / proxy config file ? After upgrading to 2.2.2 the issue persists.
          Hide
          richlv added a comment -

          ZBX-8057 might be related

          Show
          richlv added a comment - ZBX-8057 might be related
          Hide
          PavelSalkov added a comment -

          I had the same problem (Zabbix 2.2.5 + vCenter 5.5)
          "... error: a timeout was reached"

          The solution is simple!
          Change timeout (from 10 to 60):

          1. Find that file: /src/zabbix_server/vmware/vmware.c
          2. Find row: "int err, opt, timeout = 10, ret = FAIL;"
          3. Replace "10" to "60": "int err, opt, timeout = 60, ret = FAIL;"
          4. Compile and install

          Show
          PavelSalkov added a comment - I had the same problem (Zabbix 2.2.5 + vCenter 5.5) "... error: a timeout was reached" The solution is simple! Change timeout (from 10 to 60): 1. Find that file: /src/zabbix_server/vmware/vmware.c 2. Find row: "int err, opt, timeout = 10, ret = FAIL;" 3. Replace "10" to "60": "int err, opt, timeout = 60, ret = FAIL;" 4. Compile and install
          Hide
          Steven Kamalsky added a comment -

          Does anyone know if this was fixed in Zabbix 2.4.1 on Redhat ? I'm running into this now.
          connect to vCenter 5.1 works fine, but 5.5 gets the "Timeout was reached."

          Or do I have to change the value stated above and recomplie ?

          Thanks

          Show
          Steven Kamalsky added a comment - Does anyone know if this was fixed in Zabbix 2.4.1 on Redhat ? I'm running into this now. connect to vCenter 5.1 works fine, but 5.5 gets the "Timeout was reached." Or do I have to change the value stated above and recomplie ? Thanks
          Hide
          Andris Zeila added a comment -

          Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7719

          Show
          Andris Zeila added a comment - Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7719
          Show
          Alexander Vladishev added a comment - - edited (1) Documentation: @2.2 What's new in Zabbix 2.2.9 Zabbix server Zabbix proxy Virtual machine monitoring @2.4 What's new in Zabbix 2.4.4 Zabbix server Zabbix proxy Virtual machine monitoring @3.0 Zabbix server Zabbix proxy Virtual machine monitoring Alexander Vladishev Looks good for me. CLOSED
          Hide
          Andris Zeila added a comment -

          Released in:

          • pre-2.2.9rc1 r52032
          • pre-2.4.4rc1 r52033
          • pre-2.5.0 r52034
          Show
          Andris Zeila added a comment - Released in: pre-2.2.9rc1 r52032 pre-2.4.4rc1 r52033 pre-2.5.0 r52034
          Hide
          Oleksiy Zagorskyi added a comment -

          Well, it introduces new server config parameter VMwareTimeout.

          That's fine, but there are other type of checks which would want to take their own similar Timeout configuration parameter.

          I recall we had discussions that would be good to add configurable Timeout parameter (in frontend) for every host.
          It would be much more universal way, however it's more complex to implement.

          Show
          Oleksiy Zagorskyi added a comment - Well, it introduces new server config parameter VMwareTimeout. That's fine, but there are other type of checks which would want to take their own similar Timeout configuration parameter. I recall we had discussions that would be good to add configurable Timeout parameter (in frontend) for every host. It would be much more universal way, however it's more complex to implement.

            People

            • Assignee:
              Unassigned
              Reporter:
              Vladislav Vodopyan
            • Votes:
              7 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: