rabbitmq is up but inaccessible

asked 2018-11-08 06:41:07 -0600

novainfinite gravatar image

updated 2018-11-08 07:04:38 -0600

i see this error a lot of time how can i solve it? the rabbitmq in controller1 is up and work fine rabbitmq is cluster why it do not try to connect to controller2 NotFound: Queue.declare: (404) NOT_FOUND - home node 'rabbit@controller1' of durable queue 'conductor' in vhost '/' is down or inaccessible

edit retag flag offensive close merge delete

Comments

1

It looks to me that it is in fact trying, but failing. If Rabbit is not down, perhaps it's inaccessible? Or perhaps this is a temporary condition when starting controller1 or restarting RabbitMQ on controller1.

Bernd Bausch gravatar imageBernd Bausch ( 2018-11-09 23:55:27 -0600 )edit

i have controller2.but in log it does not seem try to connect it thanks for answering

novainfinite gravatar imagenovainfinite ( 2018-11-10 01:37:35 -0600 )edit

Where is this error message from? NotFound: Queue.declare: (404) NOT_FOUND - home node 'rabbit@controller1' of durable queue 'conductor' in vhost '/' is down or inaccessible

Bernd Bausch gravatar imageBernd Bausch ( 2018-11-10 03:15:06 -0600 )edit

in nova and neutron log

novainfinite gravatar imagenovainfinite ( 2018-11-10 09:38:10 -0600 )edit

When you google for Queue.declare: (404) NOT_FOUND, quite a few results come up, including a two-years old bug in RHEL.

Bernd Bausch gravatar imageBernd Bausch ( 2018-11-10 22:28:33 -0600 )edit