RabbitMQ - missed heartbeats from client

[derevyan]

Describe the problem/error/question

Lots of missed heartbeats from client, timeout: 60s errors in RabbitMQ logs.
In n8n logs all looks just fine but in RabbitMQ not really, will be helpful for any ideas how to fix it.
Service works in different dockers containers with same network.

What is the error message (if any)?

2024-06-23 03:50:04.997792+00:00 [warning] <0.77871.0> closing AMQP connection <0.77871.0> (172.25.0.22:50482 -> 172.25.0.11:5672, vhost: '/', user: 'homarabbit'):
2024-06-23 03:50:04.997792+00:00 [warning] <0.77871.0> client unexpectedly closed TCP connection
2024-06-23 03:53:02.685175+00:00 [error] <0.77886.0> closing AMQP connection <0.77886.0> (172.25.0.22:40214 -> 172.25.0.11:5672):
2024-06-23 03:53:02.685175+00:00 [error] <0.77886.0> missed heartbeats from client, timeout: 60s

Information on your n8n setup

• n8n version: Version: 1.44.2
• Database (default: SQLite): SQLite
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system: Linux e6fa43a4e493 5.15.0-101-generic #111-Ubuntu SMP Tue Mar 5 20:16:58 UTC 2024 x86_64 Linux

[Ludwig]

Hi @derevyan, thanks for reaching out and joining our community! Do you mind me asking - how are you using RabbitMQ?

RabbitMQ has a handy Heartbeat guide which explains how you might be able to configure the service for different scenarios.

Looking at similar posts on other forums, there is a suggestion that by increasing your timeout value you could avoid the situation that you’re experiencing.

[derevyan]

Thanks a lot for reply. Im try all ways you mention here but still have:

* 2024-07-13 15:16:19.893524+00:00 [error] <0.6554.0> closing AMQP connection <0.6554.0> (172.25.0.29:53112 -> 172.25.0.24:5672):

* 2024-07-13 15:16:19.893524+00:00 [error] <0.6554.0> missed heartbeats from client, timeout: 3600s

I using last version of RabbitMQ and default n8n rabbit connection type, will be happy if some one gives more ideas how to solve it.

UPDATE:
Im already try to add:

    sysctls:
      - net.ipv4.tcp_keepalive_time=600
      - net.ipv4.tcp_keepalive_intvl=60
      - net.ipv4.tcp_keepalive_probes=5

to both docker services, play around with different settings, still have errors.