Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bull arena inside docker just loading #387

Open
YasienDwieb opened this issue May 19, 2021 · 7 comments
Open

Bull arena inside docker just loading #387

YasienDwieb opened this issue May 19, 2021 · 7 comments

Comments

@YasienDwieb
Copy link

I have been using bull arena for a while as being reached via express server that is served on its own via pm2 or whatever. I have no problem with that.

The problem is when I use it from within a docker container, I get the main page but whenever I head to any queue. It never loads.

BTW, the queue is working fine and is jobs are processed but I can' view it form arena.

Thanks in advance

@rauny-henrique
Copy link

rauny-henrique commented Jun 1, 2021

I fix this by changing the "type" of each queue and configuring the redis connection for each queue.

example:

{ type: 'bull', name: queue.name, hostId: "q", redis: { port: 6379, host: process.env.REDIS_HOST || '127.0.0.1', password: null, } }

@YasienDwieb
Copy link
Author

Does, this works inside of docker? can you access each job? @rauny-henrique

@igordreher
Copy link

I'm currently facing the same issue.
It works locally, but when running inside a docker container, arena fails to load queues pages.
Error logs:

MaxRetriesPerRequestError: 
Reached the max retries per request limit (which is 20). Refer to "maxRetriesPerRequest" option for details.

I imagine that it has something to do with arena's connection to redis

@igordreher
Copy link

I solved my problem.
In my case, arena would fail to connect to redis if I provided the redis url:

queues: [{
  type: 'bull',
  name: 'example',
  hostId: 'q',
  url: 'redis://127.0.0.1:6379',
}]

The fix was simply providing the redis config connection instead, like so:

queues: [{
  type: 'bull',
  name: 'example',
  hostId: 'q',
  redis: {
    host: '127.0.0.1',
    port: 6379,
  },
}]

@YasienDwieb
Copy link
Author

YasienDwieb commented Jul 24, 2021

There's no problem with redis connection, as data is being stored and processed properly.
The issue is mainly with the dashboard, as you just get the main page and can't proceed to check whatever other pages like active, processing,... etc
Just hang up on the main page

@rauny-henrique
Copy link

Does, this works inside of docker? can you access each job? @rauny-henrique

yes, works. The problem is the redis configuration on arena, you need explicitly declare redis connection, like @igordreher say:

queues: [{ type: 'bull', name: 'example', hostId: 'q', redis: { host: '127.0.0.1', port: 6379, }, }]

@rd67
Copy link

rd67 commented Sep 24, 2021

Facing same problem with above solution as well:

Docker Compose File: https://pastebin.com/aydfsZWT

Bull Arena Config.json file: https://pastebin.com/Th4qRccT

Getting following errors on bull-arena
`/opt/arena/node_modules/bull-arena/src/server/queue/index.js:28

  throw new Error('unsupported configuration: no queues configured');

  ^

Error: unsupported configuration: no queues configured

at Queues.setConfig (/opt/arena/node_modules/bull-arena/src/server/queue/index.js:28:13)

at new Queues (/opt/arena/node_modules/bull-arena/src/server/queue/index.js:17:10)

at module.exports (/opt/arena/node_modules/bull-arena/src/server/app.js:23:18)

at run (/opt/arena/node_modules/bull-arena/index.js:7:27)

at Object.<anonymous> (/opt/arena/index.js:14:1)

at Module._compile (internal/modules/cjs/loader.js:1063:30)

at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)

at Module.load (internal/modules/cjs/loader.js:928:32)

at Function.Module._load (internal/modules/cjs/loader.js:769:14)

at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants