[ZBX-8552] VMWare CURL Timeout sometimes too low .... Created: 2014 Jul 30 Updated: 2017 May 30 Resolved: 2014 Jul 30 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 2.2.5 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Minor |
Reporter: | Andras Fabian | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 0 |
Labels: | timeout, vmware | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Linux nbg-web07 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
Issue Links: |
|
Description |
Since about some weeks (beginning with Zabbix 2.2.3 and now with Zabbix 2.2.5) we have observed a slow "creeping up" of "Not supported items" in the Zabbix Internal graph. I did also a lot of poking around in the source code, and found a single line, which made me curious (in vmware\vmware.c ): int err, opt, timeout = 10, ret = FAIL; CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = CURLOPT_TIMEOUT, (long)timeout)) || Thats where the timeout for CURL is set (which is obviously used to get the data from the VMWare API) ... and timeout is hard coded to be 10.
int err, opt, timeout = 30, ret = FAIL;
And recompiled the Zabbix Server. After an hour of watching the server, it seems this single setting completely "fixed" the problem. The number or "unsupported items" went back to normal (without any spikes since then), in the log, all VMWare related items became "supported" again, and I now regularly get updated values for my items. So, after all, I would recommend to:
This problem could be related to: |
Comments |
Comment by richlv [ 2014 Jul 30 ] |
seems to be a duplicate of |