Closed K0nne closed 7 months ago
The bug leads to a constant "OK <-> UNKNOWN" flapping, sometimes with fake alerts:
Hello,
I found a strange behaviour in Invoke-IcingaCheckProcess.
The following arguments are definded:
..but the check shows sometimes this error and recovers from it, without any config change.
Framework: 1.11.0 Plugins: 1.11.0
Invoke-IcingaCheckProcess -process @('powershell') -Verbosity 2
[OK] Process Overview: 1 Ok
\_ [OK] powershell
\_ [OK] powershell [5772]
\_ [OK] CPU Usage: 0%
\_ [OK] Memory Usage: 132.57MiB
\_ [OK] Page File Usage: 170.04KiB
\_ [OK] Thread Count: 20c
\_ [OK] powershell [6188]
\_ [OK] CPU Usage: 0%
\_ [OK] Memory Usage: 223.63MiB
\_ [OK] Page File Usage: 336.54KiB
\_ [OK] Thread Count: 26c
\_ [OK] powershell [6420]
\_ [OK] CPU Usage: 0%
\_ [OK] Memory Usage: 90.93MiB
\_ [OK] Page File Usage: 127.11KiB
\_ [OK] Thread Count: 22c
\_ [OK] powershell Summary
\_ [OK] CPU Usage: 0%
\_ [OK] Memory Usage: 447.13MiB
\_ [OK] Page File Usage: 633.70KiB
\_ [OK] Process Count: 3c
\_ [OK] Thread Count: 68c
| 'powershell::ifw_process::cpu'=0%;;;0;100 'powershell::ifw_process::memory'=468848600B;;;0;34359200000 'powershell::ifw_process::pagefile'=648904B;;;0;36507220000 'powershell::ifw_process::count'=3c;; 'powershell::ifw_process::threads'=68c;;
0
1. I dont know of a 'inspect' Button. We don't use the director.
2. I also observed this behaviour on the commandline with the same error output. Executing the same command twice worked without an error.
At first I thought it was maybe a one time-mistake of the plugin, but seeking the flapping in icingaweb2, this has to be a bug.
Its reproduceable :
It even happens with conversion units:
ref/NC/806910
Hello,
I found a strange behaviour in Invoke-IcingaCheckProcess.
The following arguments are definded:
..but the check shows sometimes this error and recovers from it, without any config change.
Framework: 1.11.0 Plugins: 1.11.0