Error: No consumer listening
When trying to run an RPA Workflow from locally hosted OpenFlow or NodeRed I get the following error:
"Error: No consumer listening at <id>"
I'm pretty sure both OpenFlow and NodeRed have been installed correctly.
I can access both interfaces and can see both ports are listening.
Also, my OpenRPA software is configured correctly and says "Connected to ws://localhost.openrpa.dk as <user> NM: online" in the bottom left.
Any idea of where to start troubleshooting this?
I'm not even sure of where to find the log files.
Any help would be much appreciated!
Allan Zimmermann last edited by
Try restarting the web/api. Sometimes the rabbitmq takes to long to start
I've tried restarting all the services but I'm still getting the same error.
I've had a look into the RabbitMQ logs and can see when the OpenFlow service starts it successfully accepts a connection:
2021-03-29 02:36:32.285 [info] <0.686.0> accepting AMQP connection <0.686.0> (127.0.0.1:53366 -> 127.0.0.1:5672)
2021-03-29 02:36:32.294 [info] <0.686.0> connection <0.686.0> (127.0.0.1:53366 -> 127.0.0.1:5672): user 'guest' authenticated and granted access to vhost '/'
When listing consumers on RabbitMQ I can see a active consumer with a matching queue name to the one being returned in the error on OpenFlow, so I'm not sure why it can't find it
I tried completely disabling my firewall during testing to ensure that wasn't a problem but its still not working.
Do you have any more ideas?
Allan Zimmermann last edited by Allan Zimmermann
Not sure if you are using docker or have installed as npm packages.
But if you are not running in docker, you need to manually enable API of rabbitmq ( on the github page it states "You need to enable management console in RabbitMQ" ) and links here
That would be my best guess if everyting else works.
The reason API needs to be enabled, is AMQP does not support querying how many listeners are on a queue. To avoid a message just "disappear" with out any error, openflow always check if the queue exists and have consumers before sending the message. Without the api it cannot, and will give the error
Enabling the management console plugin fixed all my issues!
Thanks you so much!