[ZBX-21135] The agent won't start on Windows with broken perf counters Created: 2022 May 31  Updated: 2024 Apr 10  Resolved: 2022 Aug 06

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 6.0.4
Fix Version/s: 6.0.8rc1, 6.2.2rc1, 6.4.0alpha1, 6.4 (plan)

Type: Problem report Priority: Trivial
Reporter: Victor Sklyarov Assignee: Aleksejs Sestakovs
Resolution: Fixed Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows all versions

Issue Links:
Duplicate
Team: Team B
Sprint: Sprint 89 (Jun 2022), Sprint 90 (Jul 2022), Sprint 91 (Aug 2022)
Story Points: 1

 Description   

The agent does not start if the system for collecting performance counters is not working. In addition, when this system stops, the agent inevitably falls. Is there a way to block this behavior? There are thousands of hosts from XP to win10 and agent crashes happen regularly. The agent should not fall when some Windows features stop working, that's why it is an agent. Well, I don't care about performance counters. Excites only the state of the disk space and the temperature of the processor. Even if I need performance counters, I should either get an error when reading them, or no data.

77972:20220530:140909.826 Starting Zabbix Agent [172.20.63.196]. Zabbix 6.0.4 (revision 3d787ff402e).
77972:20220530:140909.830 **** Enabled features ****
77972:20220530:140909.835 IPv6 support:          YES
77972:20220530:140909.840 TLS support:            NO
77972:20220530:140909.844 **************************
77972:20220530:140909.848 using configuration file: c:\zabbix\conf\zabbix_agentd.conf
77972:20220530:140909.933 Failed to initialize builtin counter: System
77972:20220530:140909.937 Failed to initialize builtin counter: Processor
77972:20220530:140909.941 Failed to initialize builtin counter: Processor Information
77972:20220530:140909.944 Failed to initialize builtin counter: Terminal Services
77972:20220530:140909.948 Failed to initialize builtin counter: Processor Queue Length
77972:20220530:140909.952 Failed to initialize builtin counter: System Up Time
77972:20220530:140909.955 Failed to initialize builtin counter: % Processor Time
77972:20220530:140909.959 Failed to initialize builtin counter: % Processor Time
77972:20220530:140909.962 Failed to initialize builtin counter: Total Sessions
77972:20220530:140913.400 agent #0 started [main process]
73172:20220530:140913.404 agent #1 started [collector]
79628:20220530:140913.408 agent #2 started [listener #1]
60184:20220530:140913.412 agent #3 started [listener #2]
78176:20220530:140913.416 agent #4 started [listener #3]
79844:20220530:140913.419 agent #5 started [active checks #1]
73172:20220530:140913.429 init_cpu_collector(): cannot make counterpath for "\\": [0xC0000BBD] A required argument is missing or not correct.


 Comments   
Comment by Vladimir Stepanov (Inactive) [ 2022 Jun 01 ]

Hi!
Please use debug on the agent side and attach a log file for this ticket.
1. Edit configuration file  zabbix_agentd.conf:
 DebugLevel=5
2. Restart Zabbix agent service.

Comment by Alexey Pustovalov [ 2022 Jun 02 ]

also could you try 6.0.5 version?

Comment by Victor Sklyarov [ 2022 Jun 07 ]

6.0.4 and 6.05

  1312:20220607:195648.787 Starting Zabbix Agent [10.54.74.140]. Zabbix 6.0.4 (revision 3d787ff402e).
  1312:20220607:195648.797 **** Enabled features ****
  1312:20220607:195648.807 IPv6 support:          YES
  1312:20220607:195648.817 TLS support:            NO
  1312:20220607:195648.827 **************************
  1312:20220607:195648.837 using configuration file: c:\zabbix\conf\zabbix_agentd.conf
  1312:20220607:195648.847 In init_collector_data()
  1312:20220607:195648.857 GetActiveProcessorCount() not supported, fall back to GetNativeSystemInfo()
  1312:20220607:195648.857 logical CPU count 1
  1312:20220607:195648.867 End of init_collector_data()
  1312:20220607:195648.877 In init_perf_collector()
  1312:20220607:195648.887 In init_builtin_counter_indexes()
  1312:20220607:195648.897 In get_all_counter_names()
  1312:20220607:195648.907 End of get_all_counter_names()
  1312:20220607:195648.948 End of init_builtin_counter_indexes():SUCCEED
  1312:20220607:195648.958 In set_object_names()
  1312:20220607:195650.720 In get_all_counter_names()
  1312:20220607:195650.720 End of get_all_counter_names()
  1312:20220607:195650.730 In get_all_counter_names()
  1312:20220607:195650.740 RegQueryValueEx() failed at getting buffer size, 0xc0000034
  1312:20220607:195650.750 End of get_all_counter_names()
  1312:20220607:195650.760 End of set_object_names():FAIL
  1312:20220607:195650.770 End of init_perf_collector():FAIL
  1312:20220607:195650.780 cannot initialize performance counter collector: cannot initialize object names
  1312:20220607:195650.790 Zabbix Agent stopped. Zabbix 6.0.4 (revision 3d787ff402e).

   528:20220607:201423.183 Starting Zabbix Agent [10.54.74.140]. Zabbix 6.0.5 (revision 8da3e1f8419).
   528:20220607:201423.193 **** Enabled features ****
   528:20220607:201423.244 IPv6 support:          YES
   528:20220607:201423.274 TLS support:            NO
   528:20220607:201423.324 **************************
   528:20220607:201423.374 using configuration file: c:\zabbix\conf\zabbix_agentd.conf
   528:20220607:201423.434 In init_collector_data()
   528:20220607:201423.464 GetActiveProcessorCount() not supported, fall back to GetNativeSystemInfo()
   528:20220607:201423.504 logical CPU count 1
   528:20220607:201423.544 End of init_collector_data()
   528:20220607:201423.584 In init_perf_collector()
   528:20220607:201423.614 In init_builtin_counter_indexes()
   528:20220607:201423.644 In get_all_counter_names()
   528:20220607:201423.664 End of get_all_counter_names()
   528:20220607:201424.065 End of init_builtin_counter_indexes():SUCCEED
   528:20220607:201424.095 In set_object_names()
   528:20220607:201426.198 In get_all_counter_names()
   528:20220607:201426.208 End of get_all_counter_names()
   528:20220607:201426.218 In get_all_counter_names()
   528:20220607:201426.218 RegQueryValueEx() failed at getting buffer size, 0xc0000034
   528:20220607:201426.248 End of get_all_counter_names()
   528:20220607:201426.258 End of set_object_names():FAIL
   528:20220607:201426.268 End of init_perf_collector():FAIL
   528:20220607:201426.278 cannot initialize performance counter collector: cannot initialize object names
   528:20220607:201426.278 Zabbix Agent stopped. Zabbix 6.0.5 (revision 8da3e1f8419).
Comment by Alexey Pustovalov [ 2022 Jun 07 ]

did you try rebuild performance counters?

Comment by Victor Sklyarov [ 2022 Jun 12 ]

It is not always possible to fix the counters on Win XP. The problem is not only in the start of the agent. The agent also stops when the work of the subsystem for collecting performance counters is disrupted. On 10,000 nodes this happens regularly. In my opinion, the agent should not stop when the counters fail. In normal desktop systems, no one needs these counters at all.

Comment by Victor Sklyarov [ 2022 Jun 15 ]

This cardinal solution is to fix Win. I have about 10 thousand nodes and the performance counter collection system drops regularly, about 0.5% per week. A system for collecting performance counters is needed on some highly loaded servers in order to understand the problem of resource exhaustion. And on workstations, there is no benefit other than spending resources. The dependence of the agent on some internal mechanisms of Win is a mistake. The counters don't work, WMI doesn't work, but the office spins and the internet works, so what does the user care about these systems? If the agent receives a request to display the parameters of an idle Win system, it should return an error, and not crash or be unable to start.
The dependency on counters was not present in earlier versions of the agent. There were no problems, the trigger for the lack of data is triggered - you fix it. The result of the innovations is catastrophic, the agent crashes and no data is collected. Perhaps the agent needs a setting to enable the system for collecting counters or not. Please move this issue to critical.

Comment by Aleksejs Sestakovs [ 2022 Aug 01 ]

Available in versions:

Generated at Fri May 02 08:34:54 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.