[ZBX-12971] Agent icon does not become green due to monitoring via proxy. Created: 2017 Nov 01  Updated: 2024 Apr 10  Resolved: 2017 Nov 17

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P)
Affects Version/s: 3.0.13, 3.4.4, 4.0.0alpha1
Fix Version/s: 3.0.14rc1, 3.4.5rc1, 4.0.0alpha1, 4.0 (plan)

Type: Problem report Priority: Major
Reporter: Kazuo Ito Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 1
Labels: availability, interfaces, proxy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix3.0.10

Attachments: PNG File Host.png     PNG File Host2.png     PNG File Item.png     PNG File Latest_data.png    
Issue Links:
Duplicate
Team: Team A
Sprint: Sprint 20, Sprint 21
Story Points: 0.25

 Description   

In the following cases the icon will not change green.
1)Register host via proxy(Status is disable).

2)Register item of "Zabbix agent" type

3)Change host as enable.


Monitoring is done but the icon does not change green.

Host is not available but data has been acquired.

mysql> select hostid, host, status, available, lastaccess from hosts where host = 'test';
+--------+------+--------+-----------+------------+
| hostid | host | status | available | lastaccess |
+--------+------+--------+-----------+------------+
|  10114 | test |      0 |         0 |          0 |
+--------+------+--------+-----------+------------+
1 row in set (0.00 sec)

mysql> select itemid, name , key_ from items where key_ = 'agent.ping' and hostid =10114;
+--------+------+------------+
| itemid | name | key_       |
+--------+------+------------+
|  23677 | test | agent.ping |
+--------+------+------------+
1 row in set (0.00 sec)

mysql> select itemid, from_unixtime(clock), value from history_uint where itemid=23677 limit 0,1;
+--------+----------------------+-------+
| itemid | from_unixtime(clock) | value |
+--------+----------------------+-------+
|  23677 | 2017-11-01 16:23:53  |     1 |
+--------+----------------------+-------+
1 row in set (0.00 sec)


When you restart Zabbix proxy, the icon changes to green.

 Comments   
Comment by Andrea Biscuola (Inactive) [ 2017 Nov 01 ]

Hi kazuo.ito

I'm not actually able to reproduce it with the latest version released for the 3.0 branch.
Could you be so kind to try and reproduce the issue with 3.0.12?
Also, can you provide informations on how the proxy is setup? Active or Passive?

Thanks!

Comment by Kazuo Ito [ 2017 Nov 02 ]

Hi Andrea Biscuola

proxy is Active.

I confirmed this problem at 3.0.10.
I will check it in 3.0.12 from now.

Thanks.

Comment by Kazuo Ito [ 2017 Nov 02 ]

Hi Andrea Biscuola

I checked with Zabbix 3.0.12.
This problem no longer occurred.

I confirmed the occurrence of this problem at 3.0.10.
I think that it was solved by the correction of 3.0.11 or 3.0.12.

Thanks!

Comment by Andrea Biscuola (Inactive) [ 2017 Nov 02 ]

Close the problem as FIXED. Being solved between 3.0.11 and 3.0.12

Comment by Andrea Biscuola (Inactive) [ 2017 Nov 02 ]

I can confirm that the issue was fixed in 3.0.11, was able to reproduce on 3.0.10 as
the user reported. I'm finalizing the search of the commit that fixed this.

Comment by Andrea Biscuola (Inactive) [ 2017 Nov 03 ]

I'm not able to pin-point exactly where it was fixed, the issue seems to be
not consistently reproducible across 3.0.11 commits. It seems related to
some race condition in a database update, but I was not able to find still
the exact commit where this condition was "fixed". As I need to switch to
finish ZBXNEXT-4002, I'll go back investigating this later.

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

I could reproduce a very similar scenario with Zabbix 3.0.13 r74314:

  • Initially agent is running, proxy and server are not.
  • Create and disable some host to be accessed via passive proxy, add (passive) item agent.ping
  • Manually reset host to gray: UPDATE `zabbix30`.`hosts` SET `available`='0' WHERE `hostid`=10122
  • Start proxy
  • Start server
  • Enable the host in Frontend
  • agent.ping data starts coming, but status remains gray (available==0).
  • kill proxy, start proxy
  • status turns green (available==1).

In this sequence, proxy and server can be started in any order – status update does not happen.
Server can afterwards be killed and restarted many times – status does not change (stays gray).
As you restart proxy, status soon becomes green (available).

Comment by Andrea Biscuola (Inactive) [ 2017 Nov 07 ]

valdis

If something similar can happen with the latest version, it seems
that we definitely have a race or concurrency problem somewhere
that cause this kind of behaviour.
It's absolutely possible that some and I think, completely unrelated
commit fixed the particular case the user reported but the root
cause is still there.
Can you confirm, eventually, that reproducing the issue as the user
reported (through the procedure the user suggest to do), is not
possible with 3.0.13?

Comment by Alexander Vladishev [ 2017 Nov 07 ]

Steps to reproduce:

0. Start Zabbix server, active proxy and agent
1. Register disabled host with ZA item with 5s update interval, monitored by proxy
2. Update configuration cache on server
3. Update configuration cache on proxy
4. Enable host
5. Update configuration cache on proxy
6. Wait >10 seconds
7. Update configuration cache on server

Reproducible on 3.0.10 and latest 3.0.13.

I confirm this issue.

Comment by Andris Zeila [ 2017 Nov 16 ]

Successfully tested (3.0, 3.4)

Comment by Vladislavs Sokurenko [ 2017 Nov 16 ]

Fixed in:

  • pre-3.0.14rc1 r74664
  • pre-3.4.5rc1 r74665
  • pre-4.0.0alpha1 (trunk) r74666
Comment by Oleksii Zagorskyi [ 2018 Apr 23 ]

There might be a regression or another use case - ZBX-13788

Comment by Marc [ 2018 Jul 30 ]

Since ZBX-14447 was reverted due to compatibility issues, what is the current status on this? Will it be implemented differently in one of the next updates or in the next major release only?

Comment by richlv [ 2018 Aug 12 ]

As per Marc's question above, can this please be reopened?

Comment by Vladislavs Sokurenko [ 2018 Aug 12 ]

Could you please be so kind and describe issue that you are having ? Is it same issue as in ZBX-13788 ?

Comment by richlv [ 2018 Aug 13 ]

The fix for this issue was supposedly reverted. When upgrading, should users be aware of the problem, reported in this issue, returning after the revert?

Comment by Vladislavs Sokurenko [ 2018 Aug 13 ]

ZBX-13788 fix was rolled back

Comment by richlv [ 2018 Aug 13 ]

Thank you, but that issue has no comment indicating it and is closed as fixed - is that correct?

Generated at Thu Apr 02 17:16:59 EEST 2026 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.