[ZBX-19276] Agent2 for "service.info[]" key returns not supported instead of value 255 Created: 2021 Apr 22 Updated: 2024 Apr 10 Resolved: 2023 Jan 12 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Agent2 plugin (G), Frontend (F), Server (S) |
| Affects Version/s: | 5.0.9 |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Major |
| Reporter: | msl0 | Assignee: | dimir |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Team: | |||||||||
| Description |
|
Steps to reproduce:
Result:
Additionally can you advise how to trigger action if on new Windows host there isn't specific service? |
| Comments |
| Comment by Oleksii Zagorskyi [ 2021 Apr 25 ] |
|
Agent2 is listening custom port 10060, classic agent is listening regular port 10050: # zabbix_get -s 10.33.0.28 -p 10060 -k 'service.info[test,state]' ZBX_NOTSUPPORTED: The specified service does not exist as an installed service. # zabbix_get -s 10.33.0.28 -k 'service.info[test,state]' 255 Agent2 should behave the same way as classic agent, so should be fixed. |
| Comment by msl0 [ 2021 Apr 26 ] |
|
Unfortunately I can't confirm. On my Windows machines Zabbix Agent 2 service listens on 0.0.0.0:10050 (checked by 'netstat -nta'). Service has been installed using zabbix_agent2-5.0.9-windows-amd64-openssl.msi from Zabbix website. $ zabbix_get -s A.B.C.D -p 10050 -k 'service.info[test,state]' ZBX_NOTSUPPORTED: The specified service does not exist as an installed service. $ zabbix_get -s A.B.C.D -p 10060 -k 'service.info[test,state]' zabbix_get [1982345]: Get value error: cannot connect to [[A.B.C.D]:10060]: [111] Connection refused $ zabbix_get -s A.B.C.D -k 'service.info[test,state]' ZBX_NOTSUPPORTED: The specified service does not exist as an installed service. Can I get 255 code using Agent2 or should I install classic agent also? |
| Comment by Oleksii Zagorskyi [ 2021 Apr 26 ] |
|
Custom TCP port I used (10060) is not related to bug itself at all. I just installed both agents and had them running simultaneously. If you will use so called classic agent (not Agent2) - it works correctly for the key. |
| Comment by dimir [ 2023 Jan 12 ] |
|
It was fixed in 5.0.20: msl0, Would it be possible to try this version? |
| Comment by dimir [ 2023 Jan 12 ] |
|
Sadly, this one was somehow missed and the real duplicate was created later. But since the issue was fixed there, closing as duplicate of |