[ZBX-15305] Agent ping not working for some clients after upgrading 2.2 to 3.4.15 Created: 2018 Dec 11 Updated: 2018 Dec 27 Resolved: 2018 Dec 27 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Critical |
| Reporter: | Diju S Nair | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
We are using Redhat Enterprise 7.5 with one main server and 5 proxy server. |
||
| Attachments: |
z66-Server.png
z66-proxy.png
z77-proxy.png
zabbix_proxy.log
zabbix_server-main.zip
zabbix_server.zip
|
| Description |
|
Steps to reproduce After upgrading the servers fro zabbix 2.2 to zabbix 3.4.15 around 50-60 servers are reporting agent ping issue and some servers around 20-30, the agent ping comes and goes in regular interval. Result: |
| Comments |
| Comment by Arturs Lontons [ 2018 Dec 11 ] |
|
Hello and thank you for reporting the issue. We will need some additional information to further troubleshoot the issue. Could you provide please provide the server/proxy log files and internal graphs regarding the Zabbix poller utilization? Right now it looks like the issue could be related to Zabbix poller utilization. |
| Comment by Diju S Nair [ 2018 Dec 11 ] |
|
Hello Arturs, Thank you for showing interest in this issue, as i have been having a hard time to resolve the error. I have attached the screen shot for two proxy servers for which the issues have been reporting and also the sever details also. For the error log... i have been using debug level 5 to trace the issue but in vain and it is very long log... Can you please update for which debug level you want report. Also please note that 90% client is using zabbix agent 2.2 which needs to be upgraded. we have optimised mysql... tried different poller values...preprossors etc....I dont know what else to do...where to find the issue... Please also find the logs attached. I hope you can shed a light on the issue.
Regards, Diju |
| Comment by Diju S Nair [ 2018 Dec 11 ] |
|
Also we have disabled agent.ping as it was sending lots of mail...within seconds...agent is unreachable and resolved...it goes on like that... |
| Comment by Glebs Ivanovskis [ 2018 Dec 11 ] |
|
What is the Update interval of agent ping items? What is time interval in nodata() function in the corresponding trigger? In official templates both are 1m, which isn't very reliable, especially if agents are active or these is proxy involved in data gathering. |
| Comment by Diju S Nair [ 2018 Dec 12 ] |
|
Hello Ivan, For agent ping it was 1 min and we changed to 5 min and the trigger for nodata() is 10 m and also we tried with 600s. |
| Comment by Diju S Nair [ 2018 Dec 14 ] |
|
Guys,.. Any help.... Also if you can provide best value possible for main server conf and proxy conf... two proxy have around 600-650 clients each ad rest three proxy servers have 100-250 clients... Reagrds, Dj |
| Comment by Arturs Lontons [ 2018 Dec 14 ] |
|
Hi, Also, try changing the agent ping interval to 1 min and nodata () to 5 min. |
| Comment by Arturs Lontons [ 2018 Dec 27 ] |
|
Hi, Due to lack of activity, we will be closing this ticket. |