[ZBX-23944] CentOS 6 Zabbix Agent 2: Default socket path issue in Package Created: 2024 Jan 16  Updated: 2024 Nov 28

Status: Confirmed
Project: ZABBIX BUGS AND ISSUES
Component/s: Packages (C)
Affects Version/s: 6.0.25, 7.0.2
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Kim Jongkwon Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I encountered an issue with starting the Zabbix Agent 2 on CentOS 6 after its installation.

Zabbix agent2 service failed to start. Running the service did not generate any log.
Therefore, I confirmed the error below by executing the binary directly and the following error was encountered:

# zabbix_agent2 -c /etc/zabbix/zabbix_agent2.conf
2024/01/16 10:34:51.475218 cannot register plugins: failed to create plugin listener with socket path, /run/zabbix/agent.plugin.sock, listen unix /run/zabbix/agent.plugin.sock: bind: no such file or directory
zabbix_agent2 [2061]: ERROR: cannot register plugins: failed to create plugin listener with socket path, /run/zabbix/agent.plugin.sock, listen unix /run/zabbix/agent.plugin.sock: bind: no such file or directory

Resolved this issue by changing the settings in the zabbix_agent2.conf file from "/run/zabbix/..." to "/var/run/zabbix/..."

PluginSocket=/var/run/zabbix/agent.plugin.sock
ControlSocket=/var/run/zabbix/agent.sock

I believe this issue might be related to the default configuration paths in the CentOS 6 RPM package.



 Comments   
Comment by JorUge Ferrari [ 2024 Mar 07 ]

Same scenario here, and changing the zabbix_agent2.conf as recommended by this post, solved the problem.

Anyone that has permission,  please close this issue, this solution works perfectly, thanks

Comment by Francesco Cirelli [ 2024 Jul 30 ]

tbross, I also confirm the presence of this problem and the solution is the following: correct the configuration file as indicated by  JKKim by replacing 

PluginSocket=/run/zabbix/agent.plugin.sock with PluginSocket=/var/run/zabbix/agent.plugin.sock

and ControlSocket=/run/zabbix/agent.sock with ControlSocket=/var/run/zabbix/agent.sock

also the 7.0.x version is affected 

 

Comment by Priit Saar [ 2024 Oct 22 ]

Can confirm the workaround works. 7.0.4 agent on Centos 6.

Generated at Sat May 10 07:09:55 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.