RabbitMQ - Resolve "NOT_FOUND - no exchange in vhost"

by
Jeremy Canfield |
Updated: May 21 2021
| RabbitMQ articles
Let's say the main RabbitMQ log has the following.
NOT_FOUND – no exchange 'exchange001' in vhost 'vhost001'
This event may appear if there is a shovel in a "terminated" state. The rabbitmqctl shovel_status command can be used to determine if there are any shovels in a terminated state.
rabbitmqctl shovel_status
If there is a shovel in a terminated state, something like this should be returned.
<<"NOT_FOUND - no exchange 'exchange001' in vhost 'vhost001'">>}},
{gen_server,call,
[<11597.12815.21>,
{call,{'queue.bind',0,<<>>,
<<"exchange001">>,
<<"#">>,false,[]},
none,<11597.12806.21>},
60000]}} dynamic foo
In this scenario, the rabbitmqctl delete_shovel command can be used to delete the shovel in a terminated state.
rabbitmqctl delete_shovel -p vhost001 shovel001
Did you find this article helpful?
If so, consider buying me a coffee over at