[ZBX-8049] zabbix[java,,ping] becomes unsupported if java gateway is down Created: 2014 Apr 08  Updated: 2024 Apr 10  Resolved: 2017 Nov 28

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Java gateway (J), Proxy (P), Server (S)
Affects Version/s: 2.2.3
Fix Version/s: 3.0.14rc1, 3.4.5rc1, 4.0.0alpha1, 4.0 (plan)

Type: Problem report Priority: Major
Reporter: Gabriele Armao Assignee: Valdis Kauķis (Inactive)
Resolution: Fixed Votes: 2
Labels: javagateway, notsupported
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

zabbix server and java gateway 2.2.3 (but also 2.2.1)

Team: Team A
Sprint: Sprint 18, Sprint 19, Sprint 20, Sprint 21, Sprint 22
Story Points: 1

 Description   

I added a new internal item to check java_gateway availability, the item is the documented: zabbix[java,,ping], I then added a trigger using the nodata(60) function in order to get an alarm if java gateway crashes, unfortunately, when zabbix java gateway goes down for any reason (be it crash, or be it just stopping the service), the item turns into NOT SUPPORTED, making the nodata() trigger unusable.

Here's the message appearing in the zabbix_server.log:

24045:20140408:112627.634 item [Zabbix Server:zabbix[java,,ping]] became not supported: cannot connect to [[127.0.0.1]:10052]: [111] Connection refused

 Comments   
Comment by Oleksii Zagorskyi [ 2014 May 16 ]

Confirmed.
Something should be fixed - server side or documentation.
https://www.zabbix.com/documentation/2.2/manual/config/items/itemtypes/internal

According to logic how work "agent.ping" key, we need to fix server side.
I.e. this item should not become unsupported.
If should return nothing if gateway is unavailable.

Comment by Gabriele Armao [ 2015 Sep 07 ]

any progress on this?

Comment by Valdis Kauķis (Inactive) [ 2017 Oct 20 ]

We handle four different input conditions: java gateway not configured, configured but not responding, responding improperly, responding properly.
The reaction is respectively: unsupport item, return no value, unsupport item, return value.
Behavior is the same for all <param>, i.e. zabbix[java,,ping] and zabbix[java,,version]. Documentation does not specify how ",version" behaves, so we keep code changes to a minimum.

Comment by Valdis Kauķis (Inactive) [ 2017 Nov 02 ]

Fixed in svn://svn.zabbix.com/branches/dev/ZBX-8049 r74228

Comment by Valdis Kauķis (Inactive) [ 2017 Nov 10 ]

Available in

  • 3.0.14rc1 r74434
  • 3.4.5rc1 r74435
  • 4.0.0alpha1 (trunk) r74436
Comment by Valdis Kauķis (Inactive) [ 2017 Nov 10 ]

Documentation for item type "Zabbix internal" could mention that zabbix[java,,ping] never becomes unsupported (even if Java gateway is not configured, not responding or responding improperly). zabbix[java,,version] becomes unsupported in these three cases, with appropriate error message in frontend (it did so also before this fix).

Comment by Valdis Kauķis (Inactive) [ 2017 Nov 16 ]

Fixed in:

  • 3.0.14rc1 r74698
  • 3.4.5rc1 r74699
  • 4.0.0alpha1 (trunk) r74701
Comment by Natalja Cernohajeva (Inactive) [ 2017 Nov 24 ]

natalja.cernohajeva: necessary Documentation update has been made for all corresponding versions. Please review:
3.0.14 Upgrade notes
3.0.14 Whatsnew
3.4.5 Upgrade notes
3.4.5 Whatsnew
RESOLVED

vjaceslavs CLOSED

Generated at Thu Apr 25 19:00:22 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.