Cannot load field "CommandLine" into a "string": unsupported type

Hi

I've installed the version 6.1.1 of metricbeat on Win2012R2 but we get a lot of these errors in the log

2018-01-17T15:25:21+01:00 ERR  Error getting process details. pid=4672: error getting process arguments for pid=4672: ProcArgs failed for pid=4672: could not get Win32_Process WHERE ProcessId = 4672: wmi: cannot load field "CommandLine" into a "string": unsupported type (<nil>)
2018-01-17T15:25:21+01:00 ERR  Error getting process details. pid=4708: error getting process arguments for pid=4708: ProcArgs failed for pid=4708: could not get Win32_Process WHERE ProcessId = 4708: wmi: cannot load field "CommandLine" into a "string": unsupported type (<nil>)
2018-01-17T15:25:31+01:00 ERR  Error getting process details. pid=4124: error getting process arguments for pid=4124: ProcArgs failed for pid=4124: could not get Win32_Process WHERE ProcessId = 4124: wmi: cannot load field "CommandLine" into a "string": unsupported type (<nil>)

Does anyone have an idea why this happens? We are only using the module below without the process metricset

- module: system
  metricsets:
   - cpu             # CPU usage
   - memory          # Memory usage
   - filesystem      # File system usage for each mountpoint

Regards
Tonni

Are you sure that you don't have the process metricset enabled somewhere? Like in the modules.d/system.yml?

If you start metricbeat with debug enabled it will log this modules being used.

.\metricbeat.exe -e -d "module"
2018/01/17 16:12:58.041210 wrapper.go:141: DBG [module] system/filesystem will start after 8.876000328s
2018/01/17 16:12:58.041224 wrapper.go:141: DBG [module] system/cpu will start after 2.781402077s
2018/01/17 16:12:58.041236 wrapper.go:141: DBG [module] system/uptime will start after 2.153397671s
2018/01/17 16:12:58.041250 wrapper.go:141: DBG [module] system/fsstat will start after 9.278813114s
2018/01/17 16:12:58.041253 wrapper.go:141: DBG [module] system/network will start after 2.694938553s
2018/01/17 16:12:58.041263 wrapper.go:141: DBG [module] system/load will start after 4.811422101s
2018/01/17 16:12:58.041276 wrapper.go:141: DBG [module] system/process will start after 4.521400583s
2018/01/17 16:12:58.041291 wrapper.go:141: DBG [module] system/process_summary will start after 2.935363829s
2018/01/17 16:12:58.041258 wrapper.go:141: DBG [module] system/memory will start after 7.50219842s

Hi

That is interesting. I did not know that metricbeat.yml wasn't the only place it loaded configuration from. And you are right because system.yml was found to be active in the folder.

2018-01-18T08:51:29+01:00 INFO metricbeat start running.
2018-01-18T08:51:29+01:00 DBG  [module] Starting Wrapper[name=system, len(metricSetWrappers)=2]
2018-01-18T08:51:29+01:00 DBG  [service] Windows is interactive: false
2018-01-18T08:51:29+01:00 DBG  [module] system/cpu will start after 1.240549008s
2018-01-18T08:51:29+01:00 DBG  [module] system/memory will start after 4.08918815s
2018-01-18T08:51:29+01:00 DBG  [module] Starting Wrapper[name=system, len(metricSetWrappers)=1]
2018-01-18T08:51:29+01:00 DBG  [module] system/filesystem will start after 9.355313485s
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Checking module configs from: C:\Monitoring\metricbeat-6.1.1-windows-x86_64/modules.d/*.yml
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Load config from file: C:\Monitoring\metricbeat-6.1.1-windows-x86_64\modules.d\system.yml
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Number of module configs found: 3
2018-01-18T08:51:29+01:00 DBG  [processors] Processors: 
2018-01-18T08:51:29+01:00 DBG  [processors] New condition regexp: map[system.filesystem.mount_point:\A/(?:sys|cgroup|proc|dev|etc|host|lib)(?:(?-m:$)|/)]
2018-01-18T08:51:29+01:00 DBG  [processors] Processors: drop_event, condition=regexp: map[system.filesystem.mount_point:\A/(?:sys|cgroup|proc|dev|etc|host|lib)(?:(?-m:$)|/)]
2018-01-18T08:51:29+01:00 DBG  [processors] Processors: 
2018-01-18T08:51:29+01:00 INFO Config reloader started
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Scan for new config files
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Load config from file: C:\Monitoring\metricbeat-6.1.1-windows-x86_64\modules.d\system.yml
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Number of module configs found: 3
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Remove module from stoplist: 16874904698020136409
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Add module to startlist: 16874904698020136409
2018-01-18T08:51:29+01:00 DBG  [processors] Processors: 
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Remove module from stoplist: 6259003571077527891
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Add module to startlist: 6259003571077527891
2018-01-18T08:51:29+01:00 DBG  [processors] New condition regexp: map[system.filesystem.mount_point:\A/(?:sys|cgroup|proc|dev|etc|host|lib)(?:(?-m:$)|/)]
2018-01-18T08:51:29+01:00 DBG  [processors] Processors: drop_event, condition=regexp: map[system.filesystem.mount_point:\A/(?:sys|cgroup|proc|dev|etc|host|lib)(?:(?-m:$)|/)]
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Remove module from stoplist: 8560891566631850026
2018-01-18T08:51:29+01:00 DBG  [cfgfile] Add module to startlist: 8560891566631850026
2018-01-18T08:51:29+01:00 DBG  [processors] Processors: 
2018-01-18T08:51:29+01:00 INFO Starting 3 runners ...
2018-01-18T08:51:29+01:00 DBG  [module] Starting Wrapper[name=system, len(metricSetWrappers)=5]
2018-01-18T08:51:29+01:00 DBG  [cfgfile] New runner started: 16874904698020136409
2018-01-18T08:51:29+01:00 DBG  [module] Starting Wrapper[name=system, len(metricSetWrappers)=2]
2018-01-18T08:51:29+01:00 DBG  [module] system/cpu will start after 8.083805826s
2018-01-18T08:51:29+01:00 DBG  [module] system/network will start after 6.158962305s
2018-01-18T08:51:29+01:00 DBG  [cfgfile] New runner started: 6259003571077527891
2018-01-18T08:51:29+01:00 DBG  [module] system/memory will start after 2.197573019s
2018-01-18T08:51:29+01:00 DBG  [module] system/process_summary will start after 3.625392083s
2018-01-18T08:51:29+01:00 DBG  [module] system/process will start after 7.509132001s
2018-01-18T08:51:29+01:00 DBG  [module] system/filesystem will start after 4.207375251s
2018-01-18T08:51:29+01:00 DBG  [module] system/fsstat will start after 4.55518703s
2018-01-18T08:51:29+01:00 DBG  [module] Starting Wrapper[name=system, len(metricSetWrappers)=1]
2018-01-18T08:51:29+01:00 DBG  [cfgfile] New runner started: 8560891566631850026
2018-01-18T08:51:29+01:00 DBG  [module] system/uptime will start after 5.74342186s
2018-01-18T08:51:29+01:00 INFO Loading of config files completed.
2018-01-18T08:51:30+01:00 DBG  [module] Starting metricSetWrapper[module=system, name=cpu, host=]

//Tonni

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.