[ZBX-20554] MongoDB Plugin hangs on Agent2 on Windows Created: 2022 Feb 08  Updated: 2024 Apr 10  Resolved: 2022 Nov 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent2 plugin (G)
Affects Version/s: 5.4.9, 6.0.0beta3
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Radek Pavlík Assignee: Eriks Sneiders
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux Centos 8.5

Issue Links:
Duplicate
duplicates ZBX-20404 Zabbix Agent 2 can't obtain metrics f... Closed
Team: Team INT
Sprint: Sprint 85 (Feb 2022), Sprint 86 (Mar 2022), Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022), Sprint 90 (Jul 2022), Sprint 91 (Aug 2022), Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Sprint 94 (Nov 2022)
Story Points: 1

 Description   

Steps to reproduce:

  1. System worsk initially as expected and monitors MongoDB
  2. MongoDB hangs and stop responding
  3. Zabbix Agent2 zabbix_get calls to MongoDB plugin related Item keys hangs too
  4. Other zabbix_get calls like agent.ping works well

Example (IP address and password obfuscated)

  1. time zabbix_get -s 0.0.0.0 -k mongodb.ping["tcp://localhost:00000","zab","xyz"]

zabbix_get [4087707]: Timeout while executing operation

 

real    1m0.003s

user    0m0.000s

sys     0m0.002s

 

Result:
Zabbix_get call timeouts after1 minute - network timeout.

The consequence is, that Zabbix marks whole interface on the monitored Host as unsupported because of the network timeout and after while Zabbix marks the Interface working again because other Items  like agent.ping works. 

This flapping causes huge load by "unsupported pollers".

Expected:
Expected result is that Zabbix agent returns Item value or returns ZBX_NOTSUPPORTED after agent timeout (3 secs) is reached.

 Comments   
Comment by Edgars Melveris [ 2022 Feb 08 ]

Confirm
I test connection to unavailable host - 10.1.1.155 doesn't exist

time zabbix_get -s 127.0.0.1 -p 10060  -k mongodb.ping["tcp://10.1.1.155:0000","zab","xyz"]
0

real    0m9.711s
user    0m0.001s
sys     0m0.001s

According to my config:

grep -P "^Timeout|^ListenPort" /etc/zabbix/zabbix_agent2.conf
ListenPort=10060
Timeout=3

it should timeout after 3 seconds, not 9 seconds. Not sure why it's taking 60 seconds for reporter, but it should be 3 seconds in both situations.

Comment by Alexander Vladishev [ 2022 Nov 07 ]

Closed as duplicate of ZBX-20404

Generated at Wed Apr 30 06:52:26 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.