Fix: Hyper-V Health plugin always reporting critical because of service exit code 1077

[LordHepipud]

Fixes Hyper-V Health plugin always reporting critical because of service exit code 1077, which simply means this service was never started on the host before.

It should be save to ignore and actuall makes the plugin useful.

Ressource: https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--1000-1299-

[wp-perc]

Hi, I don't know if things are related.

I just run the latest commit of plugin Invoke-IcingaCheckHyperVHealth, but I still get CRITICAL because of several services that are configured with Startup Type Manual (Trigger start).

This issue was meant to resolve this malfunction? If not, I think a new issue must be opened, because this check is almost unusable.

[LordHepipud]

Are you using the latest version for the plugin and the Framework and everything related?

Because it should look like this

Can you maybe run

Copy-IcingaFrameworkCacheTemplate;
icinga -RebuildCache { Invoke-IcingaCheckHyperVHealth -Verbosity 3; }:

[wp-perc]

My bad, I tried to just replace the ps1 file using the one from github, and now I understand this will never work. After updating to framework 1.10 and hyperv 1.2, the situation improves but it is not much better.

The warning on Health State still remains.

Any idea?

[wp-perc]

Resolved, it was just a problem of permissions.

Thanks for the help.

[LordHepipud]

You are welcome - happy it works now! :)