[ZBX-7719] VMWare monitoring bug (timeout reached) Created: 2014 Jan 29  Updated: 2017 May 30  Resolved: 2015 Feb 06

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.2.0, 2.2.1
Fix Version/s: 2.2.9rc1, 2.4.4rc1, 2.5.0

Type: Incident report Priority: Blocker
Reporter: Vladislav Vodopyan Assignee: Unassigned
Resolution: Fixed Votes: 7
Labels: timeout, vmware
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix 2.2.1-MySQL on CentOS release 6.4

Issue Links:
Duplicate
is duplicated by ZBX-8552 VMWare CURL Timeout sometimes too low... Closed

 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.

 Comments   
Comment by Evgeny Molchanov [ 2014 Feb 13 ]

С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.

Comment by Henrik Johansen [ 2014 Mar 04 ]

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.

Comment by richlv [ 2014 Jul 30 ]

ZBX-8057 might be related

Comment by PavelSalkov [ 2014 Aug 15 ]

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

Comment by Steven Kamalsky [ 2015 Jan 20 ]

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

Comment by Andris Zeila [ 2015 Feb 03 ]

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

Comment by Alexander Vladishev [ 2015 Feb 05 ]

(1) Documentation:

@2.2

@2.4

@3.0

sasha Looks good for me. CLOSED

Comment by Andris Zeila [ 2015 Feb 06 ]

Released in:

  • pre-2.2.9rc1 r52032
  • pre-2.4.4rc1 r52033
  • pre-2.5.0 r52034
Comment by Oleksii Zagorskyi [ 2015 Feb 21 ]

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.

Generated at Fri Apr 26 23:42:06 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.