FreeKB - RabbitMQ Resolve "net_tick_timeout"
RabbitMQ - Resolve "net_tick_timeout"

Let's say the main RabbitMQ log file contains the net_tick_timeout.

=ERROR REPORT==== 1-Oct-2020::00:39:53 ===
** Node rabbit@server1 not responding **
** Removing (timedout) connection **

=INFO REPORT==== 1-Oct-2020::00:39:53 ===
rabbit on node rabbit@server1 down

=INFO REPORT==== 1-Oct-2020::00:39:53 ===
node rabbit@server1 down: net_tick_timeout


The main rabbitmq conf file may have the net_ticktime defined. If not defined, the net_ticktime defaults to 60 seconds.

net_ticktime = 60


net_tick_timeout occurs when:

  • One RabbitMQ node in a cluster issues a TCP connection to another RabbitMQ node in the cluster
  • The net_ticktime duration is reached (60 seconds by default) before the TCP request is acknowledged

When net_tick_timeout occurs, the node is removed from the cluster. The rabbitmqctl cluster_status command can be used to view the current nodes in the cluster. In this example, "nodes" shows that there are 3 nodes in the cluster, and "running_nodes" shows that only one of the nodes is "running".

~]# rabbitmqctl cluster_status
Cluster status of node rabbit@server1


The rabbitmqctl node_health_check command can be used.

~]# rabbitmqctl node_health_check
Timeout: 70.0 seconds
Checking health of node rabbit@server1
Health check passed


In this scenario, you can try to restart the node, and then reissue the rabbitmqctl cluster_status command to see if the node is detected as a "running node".


Add a Comment

We will never share your name or email with anyone. Enter your email if you would like to be notified when we respond to your comment.

Please enter 9f16d in the box below so that we can be sure you are a human.


Web design by yours truely - me, myself, and I   |   |