[ZBX-21766] Mongodb item mongodb.server.status "timeout occurred" Created: 2022 Oct 14  Updated: 2023 Oct 13  Resolved: 2022 Nov 03

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

Type: Problem report Priority: Major
Reporter: Ján Ignjič Assignee: Zabbix Integration Team
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Ubuntu 20.04.3 LTS
zabbix-agent2-plugin-mongodb/focal,now 0:1.1.0-1+ubuntu20.04 amd64 [installed]
zabbix-agent2/focal,now 1:6.0.9-1+ubuntu20.04 amd64 [installed]
zabbix-get/focal,now 1:6.0.9-1+ubuntu20.04 amd64 [installed]
zabbix-sender/focal,now 1:6.0.9-1+ubuntu20.04 amd64 [installed]
MongoDB: 6.0.2


Attachments: PNG File Screenshot 2022-10-18 at 15.01.02.png     File ZBX-21766.mongodb.pcap     PNG File commands.png     Text File zabbix_agent2.log    

 Description   

Hello,
after I execute zabbix_get -s localhost -k 'mongodb.server.status[tcp://localhost:27017,<user>,<password>]' any other mongodb items end with results: "ZBX_NOTSUPPORTED: timeout occurred"

Environment:

  1. OS: Ubuntu 20.04.3 LTS
  2. Zabbix:
zabbix-agent2-plugin-mongodb/focal,now 0:1.1.0-1+ubuntu20.04 amd64 [installed]
zabbix-agent2/focal,now 1:6.0.9-1+ubuntu20.04 amd64 [installed]
zabbix-get/focal,now 1:6.0.9-1+ubuntu20.04 amd64 [installed]
zabbix-sender/focal,now 1:6.0.9-1+ubuntu20.04 amd64 [installed]
  1. MongoDB: 6.0.2

Steps to reproduce:

root@minion1:~# zabbix_get -s localhost -k 'mongodb.ping[tcp://localhost:27017,zabbix,123]'
1.000000
root@minion1:~# zabbix_get -s localhost -k 'mongodb.db.discovery[tcp://localhost:27017,zabbix,123]'
[{"{#DBNAME}":"admin"},{"{#DBNAME}":"config"},{"{#DBNAME}":"local"}]
root@minion1:~# zabbix_get -s localhost -k 'mongodb.server.status[tcp://localhost:27017,zabbix,123]'
ZBX_NOTSUPPORTED: timeout occurred
root@minion1:~# zabbix_get -s localhost -k 'mongodb.ping[tcp://localhost:27017,zabbix,123]'
ZBX_NOTSUPPORTED: timeout occurred
root@minion1:~# zabbix_get -s localhost -k 'mongodb.db.discovery[tcp://localhost:27017,zabbix,123]'
ZBX_NOTSUPPORTED: timeout occurred

Log file zabbix_agent2.log



 Comments   
Comment by Edgar Akhmetshin [ 2022 Oct 18 ]

Hello Ján,

Could you please gather network dump from this host during failing checks?

tcpdump -npi any -s 0 -w /tmp/ZBX-21766.mongodb.pcap port 27017

Start capturing, execute check several times using zabbix_get or execute now from frontend.

Regards,
Edgar

Comment by Ján Ignjič [ 2022 Oct 18 ]

Hello Edgar,

Tcpdump here: ZBX-21766.mongodb.pcap

Command sequence:

root@minion1:/home/vagrant# zabbix_get -s localhost -k 'mongodb.ping[tcp://localhost:27017,zabbix,123]'
1.000000
root@minion1:/home/vagrant# zabbix_get -s localhost -k 'mongodb.server.status[tcp://localhost:27017,zabbix,123]'
ZBX_NOTSUPPORTED: timeout occurred
root@minion1:/home/vagrant# zabbix_get -s localhost -k 'mongodb.ping[tcp://localhost:27017,zabbix,123]'
ZBX_NOTSUPPORTED: timeout occurred 
Comment by Edgar Akhmetshin [ 2022 Oct 18 ]

Thank you,

Please show:

ss -twlrnu
ip a
cat /etc/hosts

Looks like sometimes agent tries to create new connection on top of existing one.

Comment by Ján Ignjič [ 2022 Oct 18 ]

 

Hello here is output

root@minion1:/# ss -twlrnu
Netid   State    Recv-Q   Send-Q              Local Address:Port        Peer Address:Port   Process
icmp6   UNCONN   0        0                          *%eth1:58                     *:*
icmp6   UNCONN   0        0                          *%eth0:58                     *:*
udp     UNCONN   0        0                    localhost%lo:53               0.0.0.0:*
udp     UNCONN   0        0                    minion1%eth0:68               0.0.0.0:*
tcp     LISTEN   0        4096                      0.0.0.0:27017            0.0.0.0:*
tcp     LISTEN   0        511        ubuntu2004.localdomain:6001             0.0.0.0:*
tcp     LISTEN   0        511        ubuntu2004.localdomain:6002             0.0.0.0:*
tcp     LISTEN   0        511        ubuntu2004.localdomain:6003             0.0.0.0:*
tcp     LISTEN   0        511        ubuntu2004.localdomain:6004             0.0.0.0:*
tcp     LISTEN   0        4096                 localhost%lo:53               0.0.0.0:*
tcp     LISTEN   0        128                       0.0.0.0:22               0.0.0.0:*
tcp     LISTEN   0        4096                            *:10050                  *:*
tcp     LISTEN   0        511                             *:80                     *:*
tcp     LISTEN   0        128                          [::]:22                  [::]:*

root@minion1:/# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:25:0e:c1 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic eth0
       valid_lft 84046sec preferred_lft 84046sec
    inet6 fe80::a00:27ff:fe25:ec1/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:f9:4b:62 brd ff:ff:ff:ff:ff:ff
    inet 192.168.50.11/24 brd 192.168.50.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fef9:4b62/64 scope link
       valid_lft forever preferred_lft forever

root@minion1:/# cat /etc/hosts
127.0.0.1       localhost
127.0.1.1       ubuntu2004.localdomain# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

127.0.0.1 ubuntu2004.localdomain127.0.2.1 minion1 minion1

192.168.50.11           mongo1
192.168.50.12           mongo2
192.168.50.13           mongo3 

 

Comment by Ján Ignjič [ 2022 Nov 03 ]

Fix from task ZBX-21388 worked.

Thank you very much!

Comment by Aloisio Bilck [ 2023 Oct 13 ]

Hi, 
I have a similar error, but I use TLS.

logs from zabbix-agent2

 

2023/10/13 15:08:23.646013 [MongoDB] server selection error: server selection timeout, current topology: { Type: Single, Servers: [
{ Addr: mongodb.mycompany.internal:27017, Type: Unknown, Last error: connection() error occured during connection handshake: connection(mongodb.mycompany.internal:27017[-188093]) socket was unexpectedly closed: EOF }
, ] } 

 

When doing zabbix_get sometimes it responds

 

$ zabbix_get -s mongodb.mycompany.internal -k 'mongodb.ping["tcp://mongodb.mycompany.internal:27017","zabbix_mon","qwe123456"]' 
ZBX_NOTSUPPORTED: timeout occurred
$ zabbix_get -s mongodb.mycompany.internal -k 'mongodb.ping["tcp://mongodb.mycompany.internal:27017","zabbix_mon","qwe123456"]'
0.000000
$ zabbix_get -s mongodb.mycompany.internal -k 'mongodb.ping["tcp://mongodb.mycompany.internal:27017","zabbix_mon","qwe123456"]'
0.000000
$ zabbix_get -s mongodb.mycompany.internal -k 'mongodb.ping["tcp://mongodb.mycompany.internal:27017","zabbix_mon","qwe123456"]'
0.000000
$ zabbix_get -s mongodb.mycompany.internal -k 'mongodb.ping["tcp://mongodb.mycompany.internal:27017","zabbix_mon","qwe123456"]'
ZBX_NOTSUPPORTED: timeout occurred
$ zabbix_get -s mongodb.mycompany.internal -k 'mongodb.ping["tcp://mongodb.mycompany.internal:27017","zabbix_mon","qwe123456"]'
ZBX_NOTSUPPORTED: timeout occurred
$ zabbix_get -s mongodb.mycompany.internal -k 'mongodb.ping["tcp://mongodb.mycompany.internal:27017","zabbix_mon","qwe123456"]'
ZBX_NOTSUPPORTED: timeout occurred
$ zabbix_get -s mongodb.mycompany.internal -k 'mongodb.ping["tcp://mongodb.mycompany.internal:27017","zabbix_mon","qwe123456"]'
ZBX_NOTSUPPORTED: timeout occurred 

 

Generated at Fri Apr 18 23:03:18 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.