Closed wp-perc closed 1 year ago
Ok, I found the answer at my question:
the issue is in the content of CheckName
switch: a leading space in almost all commands.
So the issue is now different: why the basket has been created with the commands inside?
Hello
Thanks for the issue. Are you using an Icinga Shell
to generate the configuration? You will have to either make use of
icinga -Shell
or use
icinga {
Get-IcingaCheckCommandConfig -OutDirectory c:\temp -CheckName @("Invoke-IcingaCheckHyperVHealth", " Invoke-IcingaCheckHyperVOverCommitment", " Invoke-IcingaCheckHyperVSnapshot", " Invoke-IcingaCheckHyperVVirtualSwitches", " Invoke-IcingaCheckHyperVVMHealth", " Invoke-IcingaCheckHyperVVMM")
}
Otherwise the module components will not load inside the shell and therefor resulting in errors.
Is there a reason to compile the check commands yourself instead of using the ones shipped with each release and the master branch?
Hi all,
I am trying to export the command definitions for HyperV Plugins, but I am continuously getting the following error for every plugin:
The Basket is fulkly generated and seems usable, but a red line is not a good thing... Maybe I am missing something, but:
Get-IcingaCheckCommandConfig -OutDirectory c:\temp
) I got a basket that has no HyperV Plugins.The command I am using to force the basket generation with HyperV Plugins is:
Here the complete output:
Current system: Windows 10 with PS5.1.