[ZBX-13130] Not registered Zabbix proxies may cause high traffic/overload Zabbix server network interface Created: 2017 Dec 02  Updated: 2024 Apr 10  Resolved: 2018 Jan 16

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

Type: Problem report Priority: Major
Reporter: Oleg Ivanivskyi Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 0
Labels: encryption, proxy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix 3.4.4 with active proxies


Attachments: PNG File traffic.png    
Team: Team A
Sprint: Sprint 25
Story Points: 1

 Description   

Steps to reproduce:

  1. Install several Zabbix proxies (use active mode)
  2. Enable PSK based encryption for the proxies
  3. Don't add proxies in the frontend for now
  4. Wait for an hour
  5. Check incoming traffic on Zabbix server

Result:
Each proxy generates ~11 Mbps of traffic. I.e. 10 proxies will push ~110 Mbps. Imagine if you have 1000 of proxies... These not registered proxies may overload Zabbix server network interface easily.

Steps to reproduce:

  1. Add these new proxies in the frontend (Administration --> Proxies)
  2. Wait for a moment and check incoming traffic graph again. You will see that each proxy will use ~10Kbps now (proxy has no monitored hosts).

Expected:
Not registered proxy should generate less traffic or send configuration request not so frequently.

Notes:

  • I didn't test passive proxies
  • I didn't test proxies without encryption


 Comments   
Comment by Oleg Ivanivskyi [ 2017 Dec 02 ]

Missing proxies were added in Zabbix at 9:33-9:37.

Comment by Glebs Ivanovskis (Inactive) [ 2017 Dec 04 ]

https://en.wikipedia.org/wiki/Exponential_backoff

Comment by Vladislavs Sokurenko [ 2018 Jan 08 ]

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

Comment by Vladislavs Sokurenko [ 2018 Jan 08 ]

It's not related to encryption.

Comment by Andris Zeila [ 2018 Jan 09 ]

(1)
I think for described situation 1 second sending interval is still too much. It would be better either to use predefined larger interval in the case of sending error (1minute for example) or as Gleb suggested - increase the interval exponentially until some limit.

wiper After short discussion it was decided to send empty proxy data requests after failing to put data to server until server returns success response.

vso RESOLVED in r76714

wiper tested with a slight variation in r76729, please review

vso CLOSED with small style fixes in 76729:r76731

Comment by Vladislavs Sokurenko [ 2018 Jan 16 ]

Fixed in:

  • pre-3.4.7rc1 r76887
  • pre-4.0.0alpha3 (trunk) r76888
Generated at Fri Apr 26 10:35:33 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.