"QueryPerf" with "1" argument(s): "A specified parameter was not correct: querySpec.interval""

[patwes]

get this error on a new deploy of higway 17, connected to a vcenter 7.0U3c

PowerShell transcript start
Start time: 20220328114002

---

Transcript started, output file is /var/log/sexigraf/ViPullStatistics.log
2022-03-28T11:40:02.0657215+00:00 [INFO] ViPullStatistics v0.9.988
2022-03-28T11:40:02.0772975+00:00 [INFO] Importing PowerCli and Graphite PowerShell modules ...
2022-03-28T11:40:03.1316396+00:00 [INFO] Looking for another ViPullStatistics for ...
2022-03-28T11:40:03.1562942+00:00 [INFO] SessionToken found in SessionFile, attempting connection to ...
2022-03-28T11:40:06.0103680+00:00 [INFO] Connected to vCenter version 7.0.3 build 19234570
2022-03-28T11:40:06.0158574+00:00 [INFO] Start processing vCenter/ESX ...
2022-03-28T11:40:06.1160121+00:00 [INFO] Processing SessionManager & EventManager ...
2022-03-28T11:40:06.4192514+00:00 [INFO] vCenter objects collect ...
2022-03-28T11:40:07.5949518+00:00 [INFO] Building objects tables ...
2022-03-28T11:40:07.6337098+00:00 [INFO] vCenter objects relationship discover ...
2022-03-28T11:40:07.6556526+00:00 [INFO] Performance metrics collection ...
2022-03-28T11:40:07.8549020+00:00 [INFO] All hosts multi metrics collected in 0.1973262 sec for vCenter
2022-03-28T11:40:08.1404067+00:00 [INFO] All vms multi metrics collected in 0.2817676 sec for vCenter
PS>TerminatingError(): "Exception calling "QueryPerf" with "1" argument(s): "A specified parameter was not correct: querySpec.interval""

TerminatingError(Measure-Command): "Exception calling "QueryPerf" with "1" argument(s): "A specified parameter was not correct: querySpec.interval""
2022-03-28T11:40:08.2072524+00:00 [ERROR] VM MultiQueryPerf failure
2022-03-28T11:40:08.2080086+00:00 [ERROR] Exception calling "QueryPerf" with "1" argument(s): "A specified parameter was not correct: querySpec.interval"
2022-03-28T11:40:08.2105539+00:00 [ERROR] Exit

---

PowerShell transcript end
End time: 20220328114008

---

[rschitz]

it looks like you can't query vmop.numSVMotion.latest or vmop.numXVMotion.latest on your clusters. can you check in the vcenter if you got any metrics at all on those metrics?

[patwes]

ok, hmm it's a home lab install so only one host per cluster, so there won't be any metrics

[rschitz]

you should have 0 nonetheless

[patwes]

ok, do i have to hack the vcsa db ? to zero it out?

[rschitz]

no no for now just check that in the UI:

[rschitz]

did you modify Statistics intervals?

[patwes]

Had the first one set to 1 minute.. changed it to 5 minutes and now it works, thanks..

[rschitz]

ok that's interesting anyway, maybe i'll change the behavior in that situation