Node-red queue error (ServerError)

I am trying to imitate the project you do in this Youtube tutorial (https://www.youtube.com/live/Zy04eSDy3RI?si=-NsyLVNiAnpU-2e6&t=3305) but I get a ServerError error when Invoke OpenFlow.

ServerError: [dt_gbs_iberia_operations_tools] Unknown queue noderedep or access denied, missing read permission on queue object

In the video you do not create any queue in app.openiap.io, I have tried to create it, but I do not see the option either, the agent is created with the same user (I only have one user and I do everything with him), the permissions of my user are the following, but I have not seen the option to add more permissions.

regards

The error says that the Node-RED user is missing read permission on the message queue object. Inside the mq collection, you will find an object with "_type":"queue" and name noderedep. Edit the ACL on that object to include the Node-RED user as well.

Sorry, I just saw you are using https://app.openiap.io … someone else has already used that name for a workitem queue that is why it’s not working, please use a different queue name.

Just change the name inside nodered, and once you don’t get an error after clicking deploy, you found a name that is not in use. Then use that name inside Invoke Openflow in OpenRPA.

It worked by changing the name, I didn’t know that the DB was compared to the other users.

Is there any documentation on how to install OpenRPA locally? I found a video of yours on Youtube where you explain how to install it on Linux, but then how can I connect the backend to the OpenRPA application on windows? By which port do you connect?

Regards.

This video is a little long, but a lot people say they really liked it.

But basically, you install docker ( on any operating system ) and then follow the guide at GitHub - open-rpa/docker ( install docker, clone the repo, run normal-up, then update wsurl in settings.json for OpenRPA )

I have cloned the repository and run the ./normal-up.sh script on linux. Everything seems to be fine, but the openiap/openflow container constantly restarts every 10 seconds due to connection error with Redis, I suppose I have to have Redis installed?

14:21:12.876 Starting @openiap/core
14:21:12.876 Done loading imports
14:21:13.194 [otel ][setdefaultlabels] ofid=46ce24eba84848dc077c9851ceeecdfc
Tracing initialized
14:21:13.290 [DatabaseConnection ][connect] Connecting to mongodb
14:21:13.325 [DatabaseConnection ][connect] Connected to mongodb
14:21:13.372 [amqpwrapper ][connect] Connecting to rabbitmq
14:21:13.427 [amqpwrapper ][connect] Connected to rabbitmq
14:21:13.478 [index ][init] VERSION: 1.5.10.62
14:21:13.552 [SamlProvider ][configure] SAML signing certificate is not configured, saml not possible
14:21:14.701 [Config ][cleanAndApply] Loaded config version 3
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
MaxRetriesPerRequestError: Reached the max retries per request limit (which is 20). Refer to “maxRetriesPerRequest” option for details.
at Socket. (/app/node_modules/ioredis/built/redis/event_handler.js:182:37)
at Object.onceWrapper (node:events:634:26)
at Socket.emit (node:events:519:28)
at TCP. (node:net:343:12)
14:21:25.548 [index ][anonymous] 404

Yes, Redis should be running.

Normally, when I run this on a fresh install, I need to run “normal-up” two times to let MongoDB set up the replication. I have never had issues with Redis before.

Sorry, I must be tired. No, you are correct, the normal setup should not be using Redis…

Have you by any chance used this server for OpenFlow before? Have you at some point used the ee-up script? (That does use Redis.)

If that is the case, then please run normal-down, then run remove-data, and then run normal-up again. This will delete all data, including the old MongoDB database that has a configuration with Redis configured.

Just to be 100% sure, I have just tested normal-up on a fresh machine, and it seems to be working for me, so I am very interested in knowing why yours has Redis configured inside OpenFlow/the database.

yes, that was the error, first install the ee version, run the remove-data script and then normal-up now the container stays on top

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.