Invoke-IcingaCheckDiskHealth Returns Inappropriate Output on Timeout

[iperry-indigex]

If the disk health check times out after obtaining a value, it will return [OK] in the output, but because of the timeout, will return with status code 3.

[iperry-indigex]

Anyone wanna take a shot at this?

[Lord Hepipud]

Thank you for the issue. I'm not even sure on how this can happen. Is this reproducible on a constant frame or does it happen random?

It looks to me output is written to the CLI and during that time, Icinga will read everything from the buffer and kills the plugin at the same moment. <Timeout exceeded> is an Icinga thing. Which means, the plugin output is generated and killed before exit code 0 is reached.

[iperry-indigex]

I have only seen it happen in this one occasion when my boss found it. So in all reality, the output is correct? The plugin itself returns good information and then while cleaning up, icinga kills it for a timeout? Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Lord Hepipud ***@***.***> Sent: Saturday, February 3, 2024 4:56:00 AM To: Icinga/icinga-powershell-plugins ***@***.***> Cc: Ian Perry ***@***.***>; Author ***@***.***> Subject: Re: [Icinga/icinga-powershell-plugins] Invoke-IcingaCheckDiskHealth Returns Inappropriate Output on Timeout (Issue #382) Thank you for the issue. I'm not even sure on how this can happen. Is this reproducible on a constant frame or does it happen random? It looks to me output is written to the CLI and during that time, Icinga will read everything from the buffer and kills the plugin at the same moment. <Timeout exceeded> is an Icinga thing. Which means, the plugin output is generated and killed before exit code 0 is reached. — Reply to this email directly, view it on GitHub<#382 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATVWIRRYXBINOGCBXSXONQLYRYJUBAVCNFSM6AAAAABCHN6MVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGI3TOMBZGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Lord Hepipud]

Yeah, the plugin itself reports a healthy state, but before it is exited with code 0 in this case, it is terminated by Icinga with exit code 3 and a timeout exceeded message.

Didn't even know Icinga reads plugin outputs while in a timeout scenario.

@Al2Klimov do you have an idea on how this can happen? To me it looks like the chances to win a lottery is higher than achieving this behaviour😂

[Alexander Aleksandrovič Klimov]

Exactly. xD But seriously, too late by 1ms is still too late, technically. So you seem to be right: #382 (comment)