Zabbix agent service running but nothing send to server

[yujizmq]

Environment
Zabbix server: zabbix_server (Zabbix) 4.0.5 Revision 90164 25 February 2019, compilation time: Feb 27 2019 03:00:44
Zabbix agent: zabbix_agentd Win64 (service) (Zabbix) 4.0.5 Revision 90164 25 February 2019, compilation time: Feb 25 2019 16:38:05

I have a zabbix anget installed on windows server 2016 and i always receive agent unreachable alerts these days.
I login to the server and confirm the zabbix agent service is in "running" state, and tcp port 10050 is accessable from same lan network.
But server didn't receive any item data from agent.
Agent works well after restart service, but after several minutes/hours the issue will appear again. Same config file on other agent has no issues.

Has anyone encountered same issue or know the solution of this issue?

After increase agent log level, i found some logs:

 16140:20200304:175336.299 End of collect_perfstat()
 15740:20200304:175336.680 Requested [system.swap.size[,total]]
 15740:20200304:175336.680 Sending back [109318565888]
 15740:20200304:175336.838 Requested [net.if.out[Microsoft ISATAP Adapter]]
 15740:20200304:175336.849 Sending back [0]
 15740:20200304:175336.954 Requested [vfs.fs.size[D:,pfree]]
 15740:20200304:175336.954 In zbx_execute_threaded_metric() key:'vfs.fs.size'
 17428:20200304:175336.955 executing in data thread for key:'vfs.fs.size'
 15740:20200304:175336.955 End of zbx_execute_threaded_metric():SYSINFO_SUCCEED ''
 15740:20200304:175336.955 Sending back [45.223841]
 15740:20200304:175337.102 Requested [vfs.fs.size[E:,pfree]]
 15740:20200304:175337.102 In zbx_execute_threaded_metric() key:'vfs.fs.size'
 16588:20200304:175337.103 executing in data thread for key:'vfs.fs.size'
 15740:20200304:175337.103 End of zbx_execute_threaded_metric():SYSINFO_SUCCEED ''
 15740:20200304:175337.103 Sending back [43.798821]
 15740:20200304:175337.235 Requested [system.uname]
 16140:20200304:175337.300 In collect_perfstat()
 16140:20200304:175337.304 End of collect_perfstat()
 16140:20200304:175338.305 In collect_perfstat()
 16140:20200304:175338.309 End of collect_perfstat()
 16140:20200304:175339.309 In collect_perfstat()
 16140:20200304:175339.313 End of collect_perfstat()
 16140:20200304:175340.314 In collect_perfstat()
 16140:20200304:175340.318 End of collect_perfstat()
 16140:20200304:175341.318 In collect_perfstat()
 16140:20200304:175341.322 End of collect_perfstat()
 16140:20200304:175342.323 In collect_perfstat()
 16140:20200304:175342.327 End of collect_perfstat()
 16140:20200304:175343.327 In collect_perfstat()
 16140:20200304:175343.332 End of collect_perfstat()
 16140:20200304:175344.332 In collect_perfstat()
 16140:20200304:175344.337 End of collect_perfstat()
 16140:20200304:175345.337 In collect_perfstat()
 16140:20200304:175345.341 End of collect_perfstat()
 16140:20200304:175346.342 In collect_perfstat()
 16140:20200304:175346.346 End of collect_perfstat()
 16140:20200304:175347.346 In collect_perfstat()
 16140:20200304:175347.350 End of collect_perfstat()
 16140:20200304:175348.351 In collect_perfstat()
 16140:20200304:175348.355 End of collect_perfstat()
 16140:20200304:175349.356 In collect_perfstat()
 16140:20200304:175349.359 End of collect_perfstat()
 16140:20200304:175350.360 In collect_perfstat()
 16140:20200304:175350.365 End of collect_perfstat()
 16140:20200304:175351.366 In collect_perfstat()
 16140:20200304:175351.370 End of collect_perfstat()
 16140:20200304:175352.371 In collect_perfstat()
 16140:20200304:175352.375 End of collect_perfstat()
 16140:20200304:175353.376 In collect_perfstat()
 16140:20200304:175353.380 End of collect_perfstat()
 16140:20200304:175354.381 In collect_perfstat()
 16140:20200304:175354.385 End of collect_perfstat()
 16140:20200304:175355.386 In collect_perfstat()
 16140:20200304:175355.389 End of collect_perfstat()
 16140:20200304:175356.390 In collect_perfstat()
 16140:20200304:175356.394 End of collect_perfstat()
 16140:20200304:175357.395 In collect_perfstat()
 16140:20200304:175357.398 End of collect_perfstat()
 16140:20200304:175358.399 In collect_perfstat()
 16140:20200304:175358.402 End of collect_perfstat()

[sirovstrukelj]

did you check configuration? restarted zabbix agent after applying configuration? correct host name in frontend and zabbix conf??

[yujizmq]

Thanks for you reply.

Yes, I have already checked my configuration and restart zabbix agent service, hostname in frontend and agent conf was the same one.

I'll post agent config file later.

[yujizmq]

did you check configuration? restarted zabbix agent after applying configuration? correct host name in frontend and zabbix conf??

Here is my agent configuration:

LogFile=C:\Program Files\Zabbix Agent\zabbix_agentd.log
LogFileSize=100
DebugLevel=4
Server=<zabbix_server_ip>
Hostname=XXX-AGENT  #already confirmed same as frontend.

Zabbix server configuration:

LogFile=/var/log/zabbix/zabbix_server.log
LogFileSize=1024
DebugLevel=3
DBName=zabbix
DBUser=zabbix
DBPassword=<db_password>
DBSocket=/var/run/postgresql/.s.PGSQL.5432
StartPollers=55
StartIPMIPollers=3
StartPollersUnreachable=20
StartPingers=10
StartDiscoverers=10
SNMPTrapperFile=/tmp/zabbix_traps.tmp
StartSNMPTrapper=1
CacheSize=1G
StartDBSyncers=8
HistoryCacheSize=512M
TrendCacheSize=512M
ValueCacheSize=512M
Timeout=30
UnavailableDelay=5
UnreachableDelay=5
FpingLocation=/usr/sbin/fping
LogSlowQueries=3000

Agent works well after restart service, but after several minutes/hours the issue appear again. Same config file on other agent has no issues.

[sirovstrukelj]

maybe you can check the event viewer in windows, where the agent is installed and compare the timestamps from the logs, to the timestamps when you loose connection to the agent. I dont know which logs to look at in windows but you can dig around a bit.

[limcz]

I have same problem, mostly with Zabbix Agent 2 on Windows 2022 server (Windows 2019). But in one case is problem with Zabbix Agent on Windows 2022. Other agents work corectly.