Processor Queue UNKN - Missing information from agent: 'system_perf'
| Info |
|---|
In some Windows Systems, the Service "Processor Queue" might vanish, and the "Processor Queue" goes UNKN. In this case, we will give you a short guidance. |
| Status |
|---|
| colour | Green |
|---|
| title | LAST TESTED ON CHECKMK 2.1.0P1 |
|---|
|
Processor Queue UNKN - Missing information from agent: 'system_perf'
Open the Windows agent's log file and see if you find this:
| Code Block |
|---|
|
2021-08-03 17:15:35.063 [Err ] Timeout [3] seconds broken when query WMI
...
...
...
2021-08-03 15:02:44.435 [Warn ] Object 'Win32_PerfRawData_PerfOS_System' in 4ms sends NO DATA
2021-08-03 15:02:44.436 [Warn ] Sub Section 'system_perf' has no data to provide, status = [2] |
...
You will find the source code of the Windows Agent in our githubGit Hub. There you will find all the System and Performance counters. For wmi_cpuload, we need the following counters:
| Code Block |
|---|
root@klappanas |
|---|
|
root@mylinuxhost:/# grep -A5 "CPULOAD" /home/anastasiosmylinuxuser/git/check_mk/agents/wnx/src/engine/providers/wmi.cpp
// WMI CPULOAD group
{"system_perf", //
{kWmiPathStd, L"Win32_PerfRawData_PerfOS_System"}},
{"computer_system", //
{kWmiPathStd, L"Win32_ComputerSystem"}},
|
Now you can run both commands. What's the output? Do you see all the data like described here: https://docs.microsoft.com/de-de/windows/win32/cimwin32prov/win32-computersystem ?
| Code Block |
|---|
|
Get-WmiObject -class Win32_PerfRawData_PerfOS_System -computername WIN-MOP95J96UQA -namespace root\cimv2 |Format-List *
Get-WmiObject -class Win32_ComputerSystem | Format-List * |
...
How long does the query run? You can use the measurement command for this
| Code Block |
|---|
|
Measure-Command {Get-WmiObject -class Win32_PerfRawData_PerfOS_System -computername WIN-MOP95J96UQA -namespace root\cimv2 |Format-List *}
Measure-Command {Get-WmiObject -class Win32_ComputerSystem | Format-List *} |
...
- Increase the wmi timeout as described here: Increase WMI Timeout
- Reboot the system
- WMI Database is broken → Use the WMI Explorer for further debugging
...