ZBX-11851-Capture.PNG
ZBX-11851-Capture2.PNG
[ZBX-11851] Zabbix Agent availability not reset after re-IP Created: 2017 Feb 27 Updated: 2018 May 08 Resolved: 2018 May 08 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 3.2.3 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Minor |
| Reporter: | Zoe O'Connell | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
ZBX-11851-Capture.PNG
ZBX-11851-Capture2.PNG
|
| Description |
|
If an agent goes down and generates an error on the server, (such as "Get value from agent failed: cannot connect to [[10.X.X.X]:10050]: [4] Interrupted system call") that error is not reset and still appears in the dashboard and is reported via the API if the agent is re-IPed before coming back up again. This happens relatively frequently in our environment, as we have immutable servers monitored via Zabbix where the hostname is recycled, but the IP address is not. We're monitoring via a Zabbix proxy, it's not clear if the problem is as a result of the proxy or the server. |
| Comments |
| Comment by Glebs Ivanovskis (Inactive) [ 2017 Feb 27 ] |
|
The error message will get updated or disappear when server receives a new error or a value for the item. This may take some time, especially if proxy is involved (server configuration update, then proxy configuration update, then item check, then sending results from proxy back to server). I see no indication of a bug so far. |
| Comment by Zoe O'Connell [ 2017 Feb 27 ] |
|
The Zabbix server is receiving data from the agent after the reIP - the error still does not clear. |
| Comment by Glebs Ivanovskis (Inactive) [ 2017 Feb 27 ] |
|
Does the item receive new values? |
| Comment by Zoe O'Connell [ 2017 Feb 27 ] |
|
Yes. |
| Comment by Glebs Ivanovskis (Inactive) [ 2017 Feb 27 ] |
|
Could you provide screenshots of Monitoring -> Latest Data and Configuration -> Hosts -> Items? |
| Comment by Zoe O'Connell [ 2017 Feb 27 ] |
|
Attached. |
| Comment by Glebs Ivanovskis (Inactive) [ 2017 Feb 27 ] |
|
Thank you! Probably host availability updates are failing... Are both server and proxy 3.2.3? |
| Comment by Zoe O'Connell [ 2017 Feb 27 ] |
|
Yes, both 3.2.3. The agents are a variety of older versions, the one from the screenshots is 2.4.4. |
| Comment by Alexander Vladishev [ 2018 May 08 ] |
|
Since version 3.4, the processing of availability data has been completely rewritten. Probably this bug will disappear. I close this issue as "Cannot reproduce". Feel free to reopen if this bug still reproducible in latest 3.4. |