image-2019-03-22-11-26-49-279.png
image-2019-03-22-11-40-59-515.png
[ZBX-15860] vmware.version[{$URL}] - Simple check is not supported. Created: 2019 Mar 22 Updated: 2019 Jun 10 Resolved: 2019 Jun 10 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 4.0.5 |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Major |
| Reporter: | Marco Hofmann | Assignee: | Arturs Lontons |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Zabbix Server & Proxy 4.0.5 in Debian 9 amd64 VMware vCenter 6.7 |
||
| Attachments: |
image-2019-03-22-11-26-49-279.png
image-2019-03-22-11-40-59-515.png
|
| Description |
|
Since Zabbix 3.4.13 I believe, I have the problem that one single vCenter, won't tell me its Moreversion number. I monitor about 10 vCenter, at 10 customer,s with 10 different proxys. All of them are Debian 9 on Zabbix 4.0+. One of them tells me for vmware.fullname[\{$URL}] & vmware.version[\{$URL}]: Simple check is not supported. I tried a lot: Different updates to vCenter. Recreating the Read-Only user. Rebooting and patching the Zabbix Proxy. Recreating the Host in Zabbix Frontend. Reading the Zabbix Proxy Log. Raising the debug level for "vmware collector" and pressing "check now" heavily, which generates no information at all in the logs. I am completely blind to this error, Zabbix gives me no Feedback. ** Can anyone help me to troubleshoot this? Steps to reproduce:
Result: (The 3m Interval was from testing, it's normally 1h) Expected: |
| Comments |
| Comment by Glebs Ivanovskis [ 2019 Mar 22 ] |
|
Dumb question. Is your Zabbix (server or proxy, whoever executes these Simple checks) compiled with libcurl and libxml? Does it say on startup that VMware monitoring support is enabled? |
| Comment by Marco Hofmann [ 2019 Mar 25 ] |
|
I'm sorry, after weeks of searching, the issues vanished. And I don't know how exactly. But I will post as much as possible, I hope the language barrier won't hurt my description, because I encountered similar behavior in the past. This Debian Zabbix Proxy was 3.4.X several weeks ago. With the Release of 4.0.3 we decided to finally make the transition to 4.0. With the switch, we still hat the problem "Simple check is not supported." for vmware.version. In the meantime I did a few "apt update && apt upgrade" to stick with the latest updates. Ai I had finally no further idea, I created this support ticket here. After I created the ticket, I restarted the Zabbix Proxy daemon once more, but this time it was different. And this is something I spectated several times in the past! Although the Zabbix binary already told me, it's 4.0.5 root@zabprox:~# zabbix_proxy -V It was still running 4.0.3! How do I know? Because when I restarted the daemon this time, I could see the version switch in the log! (Notice the time, this was last Friday) 14447:20190322:160526.625 Got signal [signal:15(SIGTERM),sender_pid:1112,sender_uid:0,reason:0]. Exiting ... After this restart the error vanished, and all items became supported once more! Maybe this helps anyone, I can't explain it, but it works now. |
| Comment by Vladislavs Sokurenko [ 2019 Mar 26 ] |
|
This code looks suspicious: /* return NULL if the service is not ready yet */ if (0 == (service->state & (ZBX_VMWARE_STATE_READY | ZBX_VMWARE_STATE_FAILED))) service = NULL; Could it be that service is in failed state, that's why version cannot be retrieved ? |
| Comment by Marco Hofmann [ 2019 Mar 28 ] |
|
I still have the old logs. There are sever entries for vmware_service_update But not one of them seems to be negative. Examples: 14652:20190322:160035.366 End of vmware_service_update_perf_entities() entities:51 And so on |
| Comment by Arturs Lontons [ 2019 Jun 04 ] |
|
Hi, |
| Comment by Arturs Lontons [ 2019 Jun 10 ] |
|
Closing for now due to lack of activity. Feel free to leave a comment and reopen the ticket. |
