[ZBX-14548] cannot get refresh rate for Datastore. A specified parameter was not correct. Created: 2018 Jul 02 Updated: 2024 Apr 10 Resolved: 2018 Aug 05 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 3.0.19 |
| Fix Version/s: | 3.0.20rc1, 3.4.12rc1, 4.0.0alpha9, 4.0 (plan) |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Aleksey | Assignee: | Michael Veksler |
| Resolution: | Fixed | Votes: | 8 |
| Labels: | datastore, vmware | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
mysql Ver 14.14 Distrib 5.6.33, VMware ESXi 5.5.0 build-2068190, Ubuntu 14.05 LTS, zabbix-server 3.0.19 |
||
| Attachments: |
latency.PNG
pfree.PNG
|
||||||||
| Issue Links: |
|
||||||||
| Team: |  Team A |
||||||||
| Sprint: | Sprint 38, Sprint 39 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
Afte update from 3.0.18 to 3.0.19 don't work this elements:
vmware.hv.datastore.size[{$URL},{$UUID},{#DATASTORE},pfree]
vmware.hv.datastore.size[{$URL},{$UUID},{#DATASTORE}]
But
vmware.hv.datastore.write[{$URL},{$UUID},{#DATASTORE},latency]
work fine. Log: |
| Comments |
| Comment by Oleg Ivanivskyi [ 2018 Jul 06 ] |
|
FYI: There is a similar issue ( |
| Comment by Dirk Steinkopf [ 2018 Jul 07 ] |
|
I am experiencing the same (similar!?) problem with 3.4.11: vmware.hv.datastore.read/write are working but vmware.hv.datastore.size values not. Log file says "cannot get refresh rate for Datastore "584fb640...": A specified parameter was not correct." several times a minute. Downgrading to 3.4.10 resolved the problem for me. |
| Comment by Ankush Chaudhari [ 2018 Jul 18 ] |
|
Yes, I am also facing same issue. I have installed 3.4.11. Can someone help me to downgrade it to 3.4.10 without any loss of my current configuration. Thanks in advance. |
| Comment by gofree [ 2018 Jul 19 ] |
|
I know its not very clean solution - I downgraded just one proxy from 3.4.11 to 3.4.10 where the wmware is being monitoried
systemctl stop zabbix-proxy yum downgrade https://repo.zabbix.com/zabbix/3.4/rhel/7/x86_64/zabbix-proxy-mysql-3.4.10-1.el7.x86_64.rpm systemctl start zabbix-proxy
seems to be working, waiting for 3.4.12
|
| Comment by Michael Veksler [ 2018 Jul 23 ] |
|
Available in:
|
| Comment by Josh [ 2018 Jul 30 ] |
|
I'm having this issue as well.
2044:20180730:155350.436 Starting Zabbix Server. Zabbix 3.4.11 (revision 82160). 2069:20180730:155610.107 cannot get refresh rate for Datastore "51bef86d-8d065f48-db34-6c416a1f0f12": A specified parameter was not correct. Also, my Zabbix Server logs say 3.4.11 but on the website it says: Zabbix 3.4.12. © 2001–2018, Zabbix SIA
Thanks for your help |
| Comment by Celio di Cavalcanti [ 2018 Aug 08 ] |
|
I believe the problem continues in version 3.0.20. "Performance counter data is not available."
I already deleted the hosts and did the discovery again. |
