[ZBX-22712] Zabbix's RabbitMQ Template using deprecated node_health_check function Created: 2023 Apr 21  Updated: 2024 Sep 19  Resolved: 2024 Sep 18

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

Type: Problem report Priority: Trivial
Reporter: Dario Andres Susman Assignee: Evgenii Gordymov
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Production, Debian Bullseye, RabbitMQ 3.11.13


Attachments: PNG File image-2024-09-18-22-03-19-035.png     JPEG File shot-2023-04-20_22-32-45.jpg    
Team: Team INT

 Description   

Steps to reproduce:

  1. Install zabbix-agent on the RabbitMQ Server
  2. On Zabbix UI, add on the corresponding server the "Template App RabbitMQ node by Zabbix agent", modify the template with the appropriate credentials.

Result:
See log file...(removed server's FQDN for security reasons)

 

2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>   crasher:
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     initial call: cowboy_stream_h:request_process/3
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     pid: <0.989.0>
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     registered_name: []
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     exception error: no function clause matching
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>                      rabbit_mgmt_wm_node:find_type('rabbit@<SERVER FQDN>',
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>                                                    []) (rabbit_mgmt_wm_node.erl, line 74)
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>       in function  rabbit_mgmt_wm_node:node_data/2 (rabbit_mgmt_wm_node.erl, line 65)
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>       in call from rabbit_mgmt_wm_node:node0/1 (rabbit_mgmt_wm_node.erl, line 44)
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>       in call from rabbit_mgmt_wm_node:resource_exists/2 (rabbit_mgmt_wm_node.erl, line 29)
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>       in call from cowboy_rest:call/3 (src/cowboy_rest.erl, line 1575)
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>       in call from cowboy_rest:expect/6 (src/cowboy_rest.erl, line 1558)
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>       in call from cowboy_rest:upgrade/4 (src/cowboy_rest.erl, line 284)
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>       in call from cowboy_stream_h:execute/3 (src/cowboy_stream_h.erl, line 300)
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     ancestors: [<0.988.0>,<0.597.0>,<0.588.0>,<0.587.0>,<0.585.0>,
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>                   rabbit_web_dispatch_sup,<0.574.0>]
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     message_queue_len: 0
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     messages: []
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     links: [<0.988.0>]
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     dictionary: []
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     trap_exit: false
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     status: running
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     heap_size: 4185
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     stack_size: 28
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>     reductions: 3007
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0>   neighbours:
2023-04-21 01:15:51.889906+00:00 [error] <0.989.0> 
2023-04-21 01:15:51.890815+00:00 [error] <0.988.0> Ranch listener {acceptor,{0,0,0,0,0,0,0,0},15672}, connection process <0.988.0>, stream 1 had its request process <0.989.0> exit with reason function_clause and stacktrace [{rabbit_mgmt_wm_node,find_type,['rabbit@<SERVER FQDN>',[]],[{file,"rabbit_mgmt_wm_node.erl"},{line,74}]},{rabbit_mgmt_wm_node,node_data,2,[{file,"rabbit_mgmt_wm_node.erl"},{line,65}]},{rabbit_mgmt_wm_node,node0,1,[{file,"rabbit_mgmt_wm_node.erl"},{line,44}]},{rabbit_mgmt_wm_node,resource_exists,2,[{file,"rabbit_mgmt_wm_node.erl"},{line,29}]},{cowboy_rest,call,3,[{file,"src/cowboy_rest.erl"},{line,1575}]},{cowboy_rest,expect,6,[{file,"src/cowboy_rest.erl"},{line,1558}]},{cowboy_rest,upgrade,4,[{file,"src/cowboy_rest.erl"},{line,284}]},{cowboy_stream_h,execute,3,[{file,"src/cowboy_stream_h.erl"},{line,300}]}]
2023-04-21 01:15:51.890815+00:00 [error] <0.988.0> 
2023-04-21 01:15:59.736256+00:00 [warning] <0.1000.0> rabbitmqctl node_health_check and its HTTP API counterpart are DEPRECATED. See https://www.rabbitmq.com/monitoring.html#health-checks for replacement options.

Expected:

Access from zabbix without erros.



 Comments   
Comment by Dario Andres Susman [ 2023 Apr 21 ]

That's from the RabbitMQ log file. Not Zabbix's. As a matter of fact, Zabbix does appear to work normally, though missing some data.

Best regards,

 

-- 
Dario Susman
Systems Engineer 
Systems Engineering - Infrastructure
[email protected]

Foregenix | www.foregenix.com 

 

Comment by Arkadiusz Rzadkowolski [ 2023 Oct 03 ]

Seeing same behavior.

 

RabbitMQ version: 3.11.16 on Oracle Linux Server

Comment by Dario Andres Susman [ 2024 Mar 13 ]

This seems to have been fixed upgrading RabbitMQ to 3.13.0, running Zabbix 6.4.12.

 

Best regards,
 

Dario Susman
Systems Engineer
Infrastructure

t: +44 845 309 6232

foregenix.com | twitter | LinkedIn

Comment by Evgenii Gordymov [ 2024 Sep 18 ]

Tested on RabbitMQ 3.13.1, Zabbix 6.0.33.

Metrics collected.

Comment by Dario Andres Susman [ 2024 Sep 19 ]

I take it that if it's fixed on 6.0 it must be fixed on 6.4?

Because I reported the issue on 6.4, not on 6.0.

 

Best regards,

 

-- 
Dario Susman
Systems Engineer 
Systems Engineering - Infrastructure
[email protected]

Foregenix | www.foregenix.com 

Comment by Evgenii Gordymov [ 2024 Sep 19 ]

Hello!
dsusman 

In Details – Affects Version/s 6.0.16.

In what Zabbix version right now u have `missing some data`?

Comment by Dario Andres Susman [ 2024 Sep 19 ]

No, sorry. I was mistaken with the one of the comments stating that on 6.4.12.

 

Let me give it a test and get back to you.

 

Best regards,

 

-- 
Dario Susman
Systems Engineer 
Systems Engineering - Infrastructure
[email protected]

Foregenix | www.foregenix.com 

Comment by Dario Andres Susman [ 2024 Sep 19 ]

It's been so long, I've upgraded this Zabbix to 6.4 and I've forgotten about it. I don't have a 6.0.x that has a RabbitMQ running.

I'm sorry for the inconvenience.  You may close the ticket.

Best regards,

 

-- 
Dario Susman
Systems Engineer 
Systems Engineering - Infrastructure
[email protected]

Foregenix | www.foregenix.com

Generated at Fri Jul 25 06:10:03 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.