[ZBX-20357] MongoDB monitoring plugin problem with custom port Created: 2021 Dec 15  Updated: 2025 Feb 14  Resolved: 2025 Feb 14

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

Type: Problem report Priority: Major
Reporter: Sergei Grigoriev Assignee: Stanislavs Jurgensons
Resolution: Duplicate Votes: 0
Labels: Agent2, MongoDB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2021-12-15-13-53-27-797.png     Text File zabbix_agent2.log    
Issue Links:
Duplicate
duplicates ZBX-24230 Zabbix MongoDB Agent 2 Plugin - Stops... Closed

 Description   

Checking Mongodb with a custom port.
When Mongo crashes, item changes its value.
But when Mongo goes up, the zabbix agent does not see it: 



 Comments   
Comment by Edgar Akhmetshin [ 2021 Dec 16 ]

Hello Sergei,

Thank you for reporting the issue. Could you please set DebugLevel to 5 in the agent configuration file and restart it, after repeat check with mongodb.

Attach log to the issue.

Regards,
Edgar

Comment by Sergei Grigoriev [ 2021 Dec 16 ]

Hi Edgar,

zabbix_agent2.log

Check port  from net.tcp.service

|2021-12-16 15:03:52|1|
|2021-12-16 15:03:22|0|
|...| |
|2021-12-16 15:01:22|0|
|2021-12-16 15:00:52|1|

Check from mongodb.ping (at 15:18 decreased Discard unchanged with heartbeat to 1 min) 

|2021-12-16 15:19:21|0|
|2021-12-16 15:18:21|0|
|2021-12-16 15:01:21|0|
|2021-12-16 14:38:21|1|
Comment by Edgar Akhmetshin [ 2021 Dec 20 ]

Hi, thank you, but log is not attached to the issue. Could you please try once again?

Comment by Sergei Grigoriev [ 2021 Dec 20 ]

zabbix_agent2.log

Comment by Edgar Akhmetshin [ 2021 Dec 21 ]

Sergei, could you please confirm, this 27018 is part of the instances started with --shardsvr or just separate one with port modified?

Comment by Sergei Grigoriev [ 2021 Dec 21 ]

MongoDB standalone docker container (0.0.0.0:27018->27017/tcp)

 

Comment by Edgar Akhmetshin [ 2021 Dec 21 ]


Thank you, confirmed. Looks like code is trying to get isMaster state to get topology for a CLOSE_WAIT socket.

Generated at Tue Apr 08 01:15:19 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.