-
Problem report
-
Resolution: Fixed
-
Major
-
5.0.35, 6.0.16, 6.0.18, 6.4.3
-
None
-
Windows Server 2019/2022
-
Sprint 103 (Aug 2023)
-
0.125
Steps to reproduce:
- Install the Zabbix Agent 2 version 6.0.13 using the MSI on Windows Servers that are running as Domain Controllers
- Start the Zabbix Agent 2 service using the Windows Services Manager (services.msc)
- Start the Zabbix Agent 2 using the command line
This issue is specific to servers that are running Windows Server and have the Domain Controller role. Other servers are able to run Zabbix Agent 2 version 6.0.13 succesfully.
Result:
Agent installation using the MSI completes successfully in all cases.
Starting the Zabbix Agent 2 service using the Windows Services Manager (services.msc) gives the following result:
Starting the Zabbix Agent 2 service using the command line (in this case Powershell), gives the following result:
I use the following commands to start the agent and check to see if the agent is running:
& 'C:\Program Files\Zabbix Agent 2\zabbix_agent2.exe' --start --config 'C:\Program Files\Zabbix Agent 2\zabbix_agent2.conf' ; Get-Service 'Zabbix Agent 2' ; Start-Sleep -Seconds 2 ; Get-Service 'Zabbix Agent 2'
As seen in the screenshot above, the cmdlet "Get-Service" shows the agent service is "Starting" right after the zabbix_agent2.exe command ran, however after 2 seconds it switches to the "Stopped" state.
The Zabbix Agent 2 log file found in C:\Program Files\Zabbix Agent 2\zabbix_agent2.log shows the following:
2023/05/02 17:29:42.335474 Starting Zabbix Agent 2 (6.0.13) 2023/05/02 17:29:42.335474 OpenSSL library (OpenSSL 3.0.8 7 Feb 2023) initialized 2023/05/02 17:29:42.335474 using configuration file: C:\Program Files\Zabbix Agent 2\zabbix_agent2.conf 2023/05/02 17:29:42.335474 using plugin 'Agent' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'Ceph' (built-in) providing following interfaces: exporter, runner, configurator 2023/05/02 17:29:42.335474 using plugin 'Cpu' (built-in) providing following interfaces: exporter, collector, runner 2023/05/02 17:29:42.335474 using plugin 'DNS' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'File' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'Log' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'MQTT' (built-in) providing following interfaces: watcher, configurator 2023/05/02 17:29:42.335474 using plugin 'Memcached' (built-in) providing following interfaces: exporter, runner, configurator 2023/05/02 17:29:42.335474 using plugin 'Memory' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'Modbus' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'Mysql' (built-in) providing following interfaces: exporter, runner, configurator 2023/05/02 17:29:42.335474 using plugin 'NetIf' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'Oracle' (built-in) providing following interfaces: exporter, runner, configurator 2023/05/02 17:29:42.335474 using plugin 'Proc' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'Redis' (built-in) providing following interfaces: exporter, runner, configurator 2023/05/02 17:29:42.335474 using plugin 'Smart' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'Swap' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'SystemRun' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'TCP' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'UDP' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'Uname' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'Uptime' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'Users' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'VFSDir' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'VMemory' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'VfsFs' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'WebCertificate' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'WebPage' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 using plugin 'WindowsEventlog' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 lowering the plugin WindowsPerfInstance capacity to 1 as the configured capacity 100 exceeds limits 2023/05/02 17:29:42.335474 using plugin 'WindowsPerfInstance' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'WindowsPerfMon' (built-in) providing following interfaces: exporter, collector, runner 2023/05/02 17:29:42.335474 using plugin 'WindowsServices' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'Wmi' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'ZabbixAsync' (built-in) providing following interfaces: exporter 2023/05/02 17:29:42.335474 using plugin 'ZabbixStats' (built-in) providing following interfaces: exporter, configurator 2023/05/02 17:29:42.335474 lowering the plugin ZabbixSync capacity to 1 as the configured capacity 100 exceeds limits 2023/05/02 17:29:42.335474 using plugin 'ZabbixSync' (built-in) providing following interfaces: exporter 2023/05/02 17:29:43.165157 Plugin communication protocol version is 6.0.13 2023/05/02 17:29:43.165157 Zabbix Agent2 hostname: [REDACTED] 2023/05/02 17:29:43.167786 cannot start agent: open \\.\pipe\agent.sock: The system cannot find the path specified. 2023/05/02 17:29:44.013516 Zabbix Agent 2 stopped. (6.0.13)
It seems that the agent cannot find (or start) the \\.\pipe\agent.sock. It is unclear to me what this component does and what could possibly prevent the agent from finding/starting this component.
The zabbix_agent2.conf file contains the following settings:
LogFile=C:\Program Files\Zabbix Agent 2\zabbix_agent2.log Server=REDACTED ServerActive=REDACTED Hostname=REDACTED Include=C:\Program Files\Zabbix Agent 2\zabbix_agent2.d\ ControlSocket=\\.\pipe\agent.sock Include=.\zabbix_agent2.d\plugins.d\*.conf
These settings are the same for all our servers (except for the Hostname, which of course differs from server to server).
Expected:
We would expect the Agent service to run. This is also the behavior we see on other (non-Domain Controller) Windows Servers running Windows Server 2019 as well as servers running Windows Server 2016:
