Description

Database:RabbitMQ connection down causing the contrail-control and contrail-collector in "initializing" state

Symptoms

contrail services is not in healthy state causing contrail services to be interrupted.

Solution

RabbitMQ connections were stuck in "TIME_WAIT" state and not responding to contrail-control and contrail-collector incoming TCP connections.


Check the "netstat -ant | grep 5672" network port status on node accepting the RabbitMQ connection.


Check the Contrail-rabbitmq logs in case of any error with RabbitMQ, And check the Health Status of RabbitMQ "rabbitmqctl cluster_status"


Restart the RabbitMQ container on the problematic nodes, this will release the TIME_WAIT state and create "ESTABLISHED" state connections.


Check the contrail-status on all nodes.

Modification History

2025-02-19 : Article Created