[ZBX-10045] First proc.cpu.util[] request results in network error Created: 2015 Nov 03  Updated: 2017 May 30  Resolved: 2015 Nov 12

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: None
Fix Version/s: 3.0.0alpha5

Type: Incident report Priority: Minor
Reporter: Andris Zeila Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: collector
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

When agent receives new proc.cpu.util[] request it adds new query to collector and returns OK with no value. While this 'hack' works with simple items, it is interpreted as network failure by server when processing agent checks.

One solution would be to wait for collector to gather at least 2 samples (or timeout) before returning a real value.

proc.cpu.util[] was implemented in ZBXNEXT-494. This issue was noticed in sub-issue (9).

 Comments   
Comment by Andris Zeila [ 2015 Nov 03 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-10045

Comment by Andris Zeila [ 2015 Nov 10 ]

Released in:

  • pre-3.0.0alpha5 r56631
Comment by Oleksii Zagorskyi [ 2015 Dec 02 ]

A similar case I may recall it performance counters added on windows agent.
It was ~4 years ago, so I don't remember all details but recall that something was strange with first received value after item has been added.
It probably was actual only when perf_counter[counter,<interval>] was with <interval> specified, but I'm not sure and cannot find any written down details.

Comment by Aleksandrs Saveljevs [ 2015 Dec 02 ]

Oleksiy, you might have meant this comment.

Comment by Oleksii Zagorskyi [ 2015 Dec 02 ]

oh, recalled more details - as I remember it was related to active checks like "system.cpu.util" or mentioned performance counters which received when agent just has started (when collector is also just has started).
And as I recall sometimes the first received value can be not very goo or not_supported or something like that.
I probably didn't report it as issue as I could not reproduce it for sure, but don't remember, I'm sorry.

Comment by Oleksii Zagorskyi [ 2015 Dec 02 ]

Thanks asaveljevs! Note - I posted comment above before noticed your reply.

Generated at Thu Apr 25 23:42:40 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.