Federation link connection disappears and can't be reestablished

[kotyara85]

Hello everyone,
We have a fairly simple setup with main (upstream) server and downstream servers connecting to it
v: 3.11.10 on k8s
[us] - [eu]
|
[cn]

so lately eu servers thwrow this error trying to connect to us

TLS server: In state hello at tls_record.erl:564 generated SERVER ALERT

Configured upstream -

So one interesting observation, if I go to US console -> exchanges, the binding to eu server is still valid, which makes it even worse, since us server thinks eu is still online and all messages go nowhere

I'd appreciate any help,
the only fix for this is to completely redeploy rmq

US logs:

2023-06-11 03:26:51.346586+00:00 [info] <0.3377.1055> connection <0.3377.1055> (192.168.194.192:61070 -> 192.168.74.157:5671 - Disposable exchange federation link connection): user 'federation' authenticated and granted access to vhost '/'
2023-06-11 03:26:51.395403+00:00 [debug] <0.1228.1055> accepting AMQP connection <0.1228.1055> (192.168.58.23:55616 -> 192.168.74.157:5672)
2023-06-11 03:26:51.395495+00:00 [debug] <0.1228.1055> closing AMQP connection <0.1228.1055> (192.168.58.23:55616 -> 192.168.74.157:5672):
2023-06-11 03:26:51.395495+00:00 [debug] <0.1228.1055> connection_closed_with_no_data_received
2023-06-11 03:26:51.395685+00:00 [debug] <0.2014.1055> Closing all channels from connection '192.168.58.23:55616 -> 192.168.74.157:5672' because it has been closed
2023-06-11 03:26:52.013629+00:00 [info] <0.3377.1055> closing AMQP connection <0.3377.1055> (192.168.194.192:61070 -> 192.168.74.157:5671 - Disposable exchange federation link connection, vhost: '/', user: 'federation')
2023-06-11 03:26:52.014060+00:00 [debug] <0.591.1055> Closing all channels from connection '192.168.194.192:61070 -> 192.168.74.157:5671' because it has been closed
2023-06-11 03:26:31.760216+00:00 [debug] <0.11941.811> connection_closed_with_no_data_received
2023-06-11 03:26:31.760363+00:00 [debug] <0.12361.811> Closing all channels from connection '192.168.58.82:35054 -> 192.168.204.94:5672' because it has been closed
2023-06-11 03:26:41.760022+00:00 [debug] <0.11344.811> accepting AMQP connection <0.11344.811> (192.168.58.82:33208 -> 192.168.204.94:5672)
2023-06-11 03:26:41.760109+00:00 [debug] <0.11344.811> closing AMQP connection <0.11344.811> (192.168.58.82:33208 -> 192.168.204.94:5672):
2023-06-11 03:26:41.760109+00:00 [debug] <0.11344.811> connection_closed_with_no_data_received
2023-06-11 03:26:41.760305+00:00 [debug] <0.11619.811> Closing all channels from connection '192.168.58.82:33208 -> 192.168.204.94:5672' because it has been closed
2023-06-11 03:26:51.760625+00:00 [debug] <0.11507.811> accepting AMQP connection <0.11507.811> (192.168.58.82:60220 -> 192.168.204.94:5672)
2023-06-11 03:26:51.760719+00:00 [debug] <0.11507.811> closing AMQP connection <0.11507.811> (192.168.58.82:60220 -> 192.168.204.94:5672):
2023-06-11 03:26:51.760719+00:00 [debug] <0.11507.811> connection_closed_with_no_data_received
2023-06-11 03:26:51.760856+00:00 [debug] <0.10932.811> Closing all channels from connection '192.168.58.82:60220 -> 192.168.204.94:5672' because it has been closed
2023-06-11 03:26:38.464974+00:00 [notice] <0.18056.834> TLS server: In state hello at tls_record.erl:564 generated SERVER ALERT: Fatal - Unexpected Message
2023-06-11 03:27:59.672308+00:00 [debug] <0.32193.1054> Exchange federation will check on exchange 'federation: fuze.direct -> rmq-us-west-2-prd-fuze A' in upstream 'eu-ams15-prd-general'
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054> Disposable connection parameters: {amqp_params_network,
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054> Disposable connection parameters: {amqp_params_network,<<"federation">>,
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054>                                    <<"4VvKKnwDqPfV9Rm">>,<<"/">>,
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054>                                    "eu-region.example.com",
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054>                                    443,2047,0,10,60000,
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054>                                    [{server_name_indication,
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054>                                      "eu-region.example.com"}],
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054>                                    [#Fun<amqp_uri.9.1630366>,
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054>                                     #Fun<amqp_uri.9.1630366>],
2023-06-11 03:27:59.672377+00:00 [debug] <0.32193.1054>                                    [],[]}

EU logs:

2023-06-11 03:29:22.979025+00:00 [debug] <0.6962.2> connection_closed_with_no_data_received
2023-06-11 03:29:22.979367+00:00 [debug] <0.6964.2> Closing all channels from connection '192.168.68.79:46670 -> 192.168.112.91:5672' because it has been closed
2023-06-11 03:29:27.892628+00:00 [notice] <0.7005.2> TLS server: In state hello at tls_record.erl:564 generated SERVER ALERT: Fatal - Unexpected Message
2023-06-11 03:29:27.892628+00:00 [notice] <0.7005.2>  - {unsupported_record_type,71}
2023-06-11 03:29:31.987604+00:00 [info] <0.6945.2> accepting AMQP connection <0.6945.2> (192.168.115.0:5177 -> 192.168.110.235:5671)
2023-06-11 03:29:32.164773+00:00 [info] <0.6945.2> connection <0.6945.2> (192.168.115.0:5177 -> 192.168.110.235:5671) has a client-provided name: Disposable exchange federation link connection
2023-06-11 03:29:32.164854+00:00 [debug] <0.6945.2> Raw client connection hostname during authN phase: {0,0,0,0,0,65535,49320,
2023-06-11 03:29:32.164854+00:00 [debug] <0.6945.2>                                                     28395}
2023-06-11 03:29:32.164919+00:00 [debug] <0.6945.2> Resolved client hostname during authN phase: ::ffff:192.168.110.235
2023-06-11 03:29:32.164967+00:00 [debug] <0.6945.2> User 'federation' authenticated successfully by backend rabbit_auth_backend_internal
2023-06-11 03:29:32.221658+00:00 [notice] <0.6825.2> TLS server: In state hello at tls_record.erl:564 generated SERVER ALERT: Fatal - Unexpected Message
2023-06-11 03:29:32.221658+00:00 [notice] <0.6825.2>  - {unsupported_record_type,71}
2023-06-11 03:29:32.342742+00:00 [info] <0.6945.2> connection <0.6945.2> (192.168.115.0:5177 -> 192.168.110.235:5671 - Disposable exchange federation link connection): user 'federation' authenticated and granted access to vhost '/'
2023-06-11 03:29:32.979184+00:00 [debug] <0.7042.2> accepting AMQP connection <0.7042.2> (192.168.68.79:60588 -> 192.168.112.91:5672)
2023-06-11 03:29:32.979282+00:00 [debug] <0.7042.2> closing AMQP connection <0.7042.2> (192.168.68.79:60588 -> 192.168.112.91:5672):
2023-06-11 03:29:32.979282+00:00 [debug] <0.7042.2> connection_closed_with_no_data_received
2023-06-11 03:29:32.979525+00:00 [debug] <0.7044.2> Closing all channels from connection '192.168.68.79:60588 -> 192.168.112.91:5672' because it has been closed
2023-06-11 03:29:33.050516+00:00 [info] <0.6945.2> closing AMQP connection <0.6945.2> (192.168.115.0:5177 -> 192.168.110.235:5671 - Disposable exchange federation link connection, vhost: '/', user: 'federation')
2023-06-11 03:29:33.051136+00:00 [debug] <0.6967.2> Closing all channels from connection '192.168.115.0:5177 -> 192.168.110.235:5671' because it has been closed
2023-06-11 03:29:34.152125+00:00 [debug] <0.6976.2> accepting AMQP connection <0.6976.2> (192.168.76.103:51866 -> 192.168.110.235:5672)
2023-06-11 03:29:34.152249+00:00 [debug] <0.6976.2> closing AMQP connection <0.6976.2> (192.168.76.103:51866 -> 192.168.110.235:5672):
2023-06-11 03:29:34.152249+00:00 [debug] <0.6976.2> connection_closed_with_no_data_received
2023-06-11 03:29:34.152500+00:00 [debug] <0.6978.2> Closing all channels from connection '192.168.76.103:51866 -> 192.168.110.235:5672' because it has been closed
2023-06-11 03:29:36.075433+00:00 [notice] <0.7078.2> TLS server: In state hello at tls_record.erl:564 generated SERVER ALERT: Fatal - Unexpected Message
2023-06-11 03:29:36.075433+00:00 [notice] <0.7078.2>  - {unsupported_record_type,71}
2023-06-11 03:29:36.284493+00:00 [debug] <0.6859.2> accepting AMQP connection <0.6859.2> (192.168.76.103:58712 -> 192.168.110.170:5672)
2023-06-11 03:29:36.284620+00:00 [debug] <0.6859.2> closing AMQP connection <0.6859.2> (192.168.76.103:58712 -> 192.168.110.170:5672):

[lukebakken]

Hello! Please help us help you by making this issue as easy as possible to reproduce. Right now you're asking us to guess about how you have your environment set up, which takes time and we'd probably not get our environment set up the same way.

The best way would be for you to provide a docker compose project that, when started, sets up federation in exactly the same way you have it set up. There shouldn't be a need to create clusters - single nodes should suffice. The tls-gen project can be used to create self-signed certificates. The basic profile also allows you to create multiple client/server certs all signed by the same CA.

The next best way would be to export your definitions so that we can check them and use them.

Finally, about this log message:

2023-06-11 03:29:36.075433+00:00 [notice] <0.7078.2> TLS server: In state hello at tls_record.erl:564 generated SERVER ALERT: Fatal - Unexpected Message
2023-06-11 03:29:36.075433+00:00 [notice] <0.7078.2>  - {unsupported_record_type,71}

This seems like a non-TLS or non-AMQP client is trying to connect.

[lianzhang132]

Hi guys, I'm having the same problem here. I'm kolla deploying openstack-xena on three controller nodes and I noticed that rabbitmq uses 3.9.29

(rabbitmq)[rabbitmq@test03 /]$ rabbitmqctl status
Status of node rabbit@test03 ...
Runtime

OS PID: 25
OS: Linux
Uptime (seconds): 3204
Is under maintenance?: false
RabbitMQ version: 3.9.29
RabbitMQ release series support status: out of support
Node name: rabbit@test03
Erlang configuration: Erlang/OTP 25 [erts-13.2.2.3] [source] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:1] [jit:ns]
Crypto library: OpenSSL 1.1.1k FIPS 25 Mar 2021
Erlang processes: 2051 used, 1048576 limit
Scheduler run queue: 1
Cluster heartbeat timeout (net_ticktime): 60

Plugins

Enabled plugin file: /etc/rabbitmq/enabled_plugins
Enabled plugins:

• rabbitmq_management
• amqp_client
• rabbitmq_web_dispatch
• cowboy
• cowlib
• rabbitmq_management_agent

Data directory

Node data directory: /var/lib/rabbitmq/mnesia/rabbit@test03
Raft data directory: /var/lib/rabbitmq/mnesia/rabbit@test03/quorum/rabbit@test03

Config files

• /etc/rabbitmq/advanced.config
• /etc/rabbitmq/rabbitmq.conf

Log file(s)

• /var/log/kolla/rabbitmq/rabbit@test03.log
• /var/log/kolla/rabbitmq/rabbit@test03_upgrade.log

Alarms

(none)

Memory

Total memory used: 0.1836 gb
Calculation strategy: rss
Memory high watermark setting: 0.4 of available memory, computed to: 53.7267 gb

binary: 0.0627 gb (34.15 %)
code: 0.0351 gb (19.13 %)
other_proc: 0.0207 gb (11.26 %)
reserved_unallocated: 0.0177 gb (9.66 %)
other_system: 0.017 gb (9.23 %)
connection_other: 0.0063 gb (3.43 %)
queue_slave_procs: 0.0038 gb (2.05 %)
other_ets: 0.0033 gb (1.82 %)
queue_procs: 0.0033 gb (1.79 %)
plugins: 0.0032 gb (1.77 %)
connection_readers: 0.0023 gb (1.25 %)
mgmt_db: 0.0021 gb (1.14 %)
allocated_unused: 0.0014 gb (0.79 %)
atom: 0.0014 gb (0.78 %)
metrics: 0.0012 gb (0.67 %)
mnesia: 0.0012 gb (0.64 %)
connection_channels: 0.0006 gb (0.34 %)
connection_writers: 0.0001 gb (0.07 %)
msg_index: 0.0 gb (0.02 %)
quorum_ets: 0.0 gb (0.01 %)
stream_queue_procs: 0.0 gb (0.0 %)
stream_queue_replica_reader_procs: 0.0 gb (0.0 %)
quorum_queue_procs: 0.0 gb (0.0 %)
stream_queue_coordinator_procs: 0.0 gb (0.0 %)

File Descriptors

Total: 64, limit: 1048479
Sockets: 62, limit: 943629

Free Disk Space

Low free disk space watermark: 0.05 gb
Free disk space: 58.3321 gb

Totals

Connection count: 62
Queue count: 327
Virtual host count: 1

Listeners

Interface: 192.168.83.30, port: 25672, protocol: clustering, purpose: inter-node and CLI tool communication
Interface: [::], port: 15672, protocol: http, purpose: HTTP API
Interface: 192.168.83.30, port: 5672, protocol: amqp, purpose: AMQP 0-9-1 and AMQP 1.0
(rabbitmq)[rabbitmq@test03 /]$

The following is my log information

2024-03-07 11:38:45.933102+08:00 [debug] <0.24261.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-03-07 11:38:45.933198+08:00 [debug] <0.24261.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-03-07 11:38:48.108621+08:00 [debug] <0.24283.0> accepting AMQP connection <0.24283.0> (192.168.83.30:52358 -> 192.168.83.30:5672)
2024-03-07 11:38:48.108759+08:00 [debug] <0.24283.0> closing AMQP connection <0.24283.0> (192.168.83.30:52358 -> 192.168.83.30:5672):
2024-03-07 11:38:48.108759+08:00 [debug] <0.24283.0> connection_closed_with_no_data_received
2024-03-07 11:38:48.110231+08:00 [debug] <0.24285.0> Closing all channels from connection '192.168.83.30:52358 -> 192.168.83.30:5672' because it has been closed
2024-03-07 11:39:00.269370+08:00 [error] <0.22997.0> closing AMQP connection <0.22997.0> (192.168.83.28:49994 -> 192.168.83.30:5672 - mod_wsgi:24:251c235e-138a-4e0f-be29-b596f25ba088):
2024-03-07 11:39:00.269370+08:00 [error] <0.22997.0> missed heartbeats from client, timeout: 60s
2024-03-07 11:39:00.270983+08:00 [debug] <0.24294.0> Closing all channels from connection '192.168.83.28:49994 -> 192.168.83.30:5672' because it has been closed
2024-03-07 11:39:00.629379+08:00 [error] <0.23016.0> closing AMQP connection <0.23016.0> (192.168.83.30:57524 -> 192.168.83.30:5672 - mod_wsgi:22:35cc56f0-dc37-4385-a821-965ea3db76ad):
2024-03-07 11:39:00.629379+08:00 [error] <0.23016.0> missed heartbeats from client, timeout: 60s
2024-03-07 11:39:00.630851+08:00 [debug] <0.24298.0> Closing all channels from connection '192.168.83.30:57524 -> 192.168.83.30:5672' because it has been closed
2024-03-07 11:39:20.384356+08:00 [debug] <0.24310.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-03-07 11:39:20.384525+08:00 [debug] <0.24310.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-03-07 11:39:22.610147+08:00 [debug] <0.24332.0> accepting AMQP connection <0.24332.0> (192.168.83.30:38340 -> 192.168.83.30:5672)
2024-03-07 11:39:22.610277+08:00 [debug] <0.24332.0> closing AMQP connection <0.24332.0> (192.168.83.30:38340 -> 192.168.83.30:5672):
2024-03-07 11:39:22.610277+08:00 [debug] <0.24332.0> connection_closed_with_no_data_received
2024-03-07 11:39:22.611555+08:00 [debug] <0.24334.0> Closing all channels from connection '192.168.83.30:38340 -> 192.168.83.30:5672' because it has been closed
2024-03-07 11:39:55.163327+08:00 [debug] <0.24495.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-03-07 11:39:55.163452+08:00 [debug] <0.24495.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-03-07 11:39:57.373040+08:00 [debug] <0.24517.0> accepting AMQP connection <0.24517.0> (192.168.83.30:58266 -> 192.168.83.30:5672)
2024-03-07 11:39:57.373182+08:00 [debug] <0.24517.0> closing AMQP connection <0.24517.0> (192.168.83.30:58266 -> 192.168.83.30:5672):
2024-03-07 11:39:57.373182+08:00 [debug] <0.24517.0> connection_closed_with_no_data_received
2024-03-07 11:39:57.374522+08:00 [debug] <0.24519.0> Closing all channels from connection '192.168.83.30:58266 -> 192.168.83.30:5672' because it has been closed
2024-03-07 11:40:27.587064+08:00 [debug] <0.24550.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-03-07 11:40:27.587247+08:00 [debug] <0.24550.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-03-07 11:40:29.687674+08:00 [debug] <0.24559.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-03-07 11:40:29.687802+08:00 [debug] <0.24559.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-03-07 11:40:31.874203+08:00 [debug] <0.24581.0> accepting AMQP connection <0.24581.0> (192.168.83.30:36960 -> 192.168.83.30:5672)
2024-03-07 11:40:31.874347+08:00 [debug] <0.24581.0> closing AMQP connection <0.24581.0> (192.168.83.30:36960 -> 192.168.83.30:5672):
2024-03-07 11:40:31.874347+08:00 [debug] <0.24581.0> connection_closed_with_no_data_received
2024-03-07 11:40:31.875655+08:00 [debug] <0.24583.0> Closing all channels from connection '192.168.83.30:36960 -> 192.168.83.30:5672' because it has been closed
2024-03-07 11:41:00.019574+08:00 [info] <0.25028.0> accepting AMQP connection <0.25028.0> (192.168.83.30:49228 -> 192.168.83.30:5672)
2024-03-07 11:41:00.024248+08:00 [info] <0.25028.0> Connection <0.25028.0> (192.168.83.30:49228 -> 192.168.83.30:5672) has a client-provided name: mod_wsgi:25:c688e5d9-e4b6-495e-8384-a6b61458b77f
2024-03-07 11:41:00.024368+08:00 [debug] <0.25028.0> Raw client connection hostname during authN phase: {192,168,83,30}
2024-03-07 11:41:00.024508+08:00 [debug] <0.25028.0> Resolved client hostname during authN phase: 192.168.83.30
2024-03-07 11:41:00.024691+08:00 [debug] <0.25028.0> User 'openstack' authenticated successfully by backend rabbit_auth_backend_internal
2024-03-07 11:41:00.025533+08:00 [info] <0.25028.0> connection <0.25028.0> (192.168.83.30:49228 -> 192.168.83.30:5672 - mod_wsgi:25:c688e5d9-e4b6-495e-8384-a6b61458b77f): user 'openstack' authenticated and granted access to vhost '/'
2024-03-07 11:41:00.157441+08:00 [info] <0.25041.0> accepting AMQP connection <0.25041.0> (192.168.83.29:38242 -> 192.168.83.30:5672)
2024-03-07 11:41:00.163507+08:00 [info] <0.25041.0> Connection <0.25041.0> (192.168.83.29:38242 -> 192.168.83.30:5672) has a client-provided name: mod_wsgi:25:bc3a7257-639f-42c7-9a40-4d777d114a60
2024-03-07 11:41:00.163596+08:00 [debug] <0.25041.0> Raw client connection hostname during authN phase: {192,168,83,30}
2024-03-07 11:41:00.163699+08:00 [debug] <0.25041.0> Resolved client hostname during authN phase: 192.168.83.30
2024-03-07 11:41:00.163841+08:00 [debug] <0.25041.0> User 'openstack' authenticated successfully by backend rabbit_auth_backend_internal
2024-03-07 11:41:00.164592+08:00 [info] <0.25041.0> connection <0.25041.0> (192.168.83.29:38242 -> 192.168.83.30:5672 - mod_wsgi:25:bc3a7257-639f-42c7-9a40-4d777d114a60): user 'openstack' authenticated and granted access to vhost '/'
2024-03-07 11:41:00.442391+08:00 [error] <0.23743.0> closing AMQP connection <0.23743.0> (192.168.83.28:56654 -> 192.168.83.30:5672 - mod_wsgi:23:472f27de-a590-44e9-85c6-cb4e856bd20f):
2024-03-07 11:41:00.442391+08:00 [error] <0.23743.0> missed heartbeats from client, timeout: 60s
2024-03-07 11:41:00.443938+08:00 [debug] <0.25053.0> Closing all channels from connection '192.168.83.28:56654 -> 192.168.83.30:5672' because it has been closed
2024-03-07 11:41:04.127410+08:00 [debug] <0.25067.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-03-07 11:41:04.127518+08:00 [debug] <0.25067.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-03-07 11:41:06.297736+08:00 [debug] <0.25089.0> accepting AMQP connection <0.25089.0> (192.168.83.30:49230 -> 192.168.83.30:5672)
2024-03-07 11:41:06.297870+08:00 [debug] <0.25089.0> closing AMQP connection <0.25089.0> (192.168.83.30:49230 -> 192.168.83.30:5672):
2024-03-07 11:41:06.297870+08:00 [debug] <0.25089.0> connection_closed_with_no_data_received
2024-03-07 11:41:06.299422+08:00 [debug] <0.25091.0> Closing all channels from connection '192.168.83.30:49230 -> 192.168.83.30:5672' because it has been closed
2024-03-07 11:41:38.566335+08:00 [debug] <0.25255.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-03-07 11:41:38.566474+08:00 [debug] <0.25255.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-03-07 11:41:40.700446+08:00 [debug] <0.25277.0> accepting AMQP connection <0.25277.0> (192.168.83.30:37152 -> 192.168.83.30:5672)
2024-03-07 11:41:40.700573+08:00 [debug] <0.25277.0> closing AMQP connection <0.25277.0> (192.168.83.30:37152 -> 192.168.83.30:5672):
2024-03-07 11:41:40.700573+08:00 [debug] <0.25277.0> connection_closed_with_no_data_received
2024-03-07 11:41:40.701884+08:00 [debug] <0.25279.0> Closing all channels from connection '192.168.83.30:37152 -> 192.168.83.30:5672' because it has been closed
2024-03-07 11:42:13.000895+08:00 [debug] <0.25303.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-03-07 11:42:13.001038+08:00 [debug] <0.25303.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-03-07 11:42:15.132946+08:00 [debug] <0.25325.0> accepting AMQP connection <0.25325.0> (192.168.83.30:55382 -> 192.168.83.30:5672)
2024-03-07 11:42:15.133081+08:00 [debug] <0.25325.0> closing AMQP connection <0.25325.0> (192.168.83.30:55382 -> 192.168.83.30:5672):
2024-03-07 11:42:15.133081+08:00 [debug] <0.25325.0> connection_closed_with_no_data_received
2024-03-07 11:42:15.134452+08:00 [debug] <0.25327.0> Closing all channels from connection '192.168.83.30:55382 -> 192.168.83.30:5672' because it has been closed

I want to know how to eliminate this frequent connection after closing action

[michaelklishin]

RabbitMQ 3.9 has reached end of life. Even 3.11 is out of community support.

RabbitMQ does not close connections, a client does, and that's not how messaging protocols are supposed to be used. See High Connection Churn.