Closed LioZha closed 2 years ago
I have never encountered this particular issue on systems using the Hyper-V plugins so far. I get the point for this, but I would not want to modify this state on a hardcoded base, because if for some reason a service is not started, but should be, noone would get a notification about this,
Anyone else having an oppinion on this?
On all my Hyper-V hosts (Windows 2019 v.1809 build: 17763.2114) Hyper-V Guest services all are in "Stopped" state, this is familiar behavior. Services startup type is: "Manual (triggered start)" and exit code exists and is eq 1077. This triggers CRITICAL output of pulgin.
According to https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--1000-1299- Exit code 1077 ERROR_SERVICE_NEVER_STARTED means that the service was never tried to start, which I believe is normal. Could you, please re-define unnecessary service detection in https://github.com/Icinga/icinga-powershell-hyperv/blob/838c86f4164dcf01dea514cfb1b1760d31f9bde3/plugins/Invoke-IcingaCheckHyperVHealth.psm1#L78 For example this line can be re-writed as