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

Queues detected but jobs not listed #4

Open
MeStrak opened this issue Apr 11, 2021 · 5 comments
Open

Queues detected but jobs not listed #4

MeStrak opened this issue Apr 11, 2021 · 5 comments

Comments

@MeStrak
Copy link

MeStrak commented Apr 11, 2021

Hi, I'm trying to run bull-board from the docker image but have a problem that no jobs are shown, even though the queues are detected.

I originally created this issue in the bull-board repo (felixmosh/bull-board#249) but they analysed it and don't think it is related directly to bull-board.

I have started up the container, and my bull queues are detected:

image

However, no jobs ever show in the UI. Running .backgroundDataQueue.getJobCounts() gives the following:

{
  waiting: 1,
  active: 0,
  completed: 25,
  failed: 0,
  delayed: 5,
  paused: 0
}

But all job categories in the UI are empty. For example:
image

image

Is there some additional config that I need to do to detect the jobs? Or should it work automatically if the queues are detected?

Thanks!

@Deadly0
Copy link
Owner

Deadly0 commented Apr 15, 2021

@MeStrak hi, did you try to run bull-board directly (without this docker image)?
Do you use bull or bullmq?
Can you share settings (env vars) witch you use to run container?

@SloCompTech
Copy link

I have the same issues, here is my part of docker-compose:

bull-ui:
    image: deadly0/bull-board:3.2.6
    container_name: queue-qui
    depends_on:
      - redis
    restart: unless-stopped
    ports:
      - 8082:3000
    environment:
      REDIS_HOST: 'q-redis'
      REDIS_PORT: 6379
      REDIS_USE_TLS: 'false'
      BULL_PREFIX: 'queue'
      BULL_VERSION: 'bull'

@SaschaVanEssen
Copy link

I am having the same issue. Did someone find a solution?
For me this problem only occurs when using a prefix.
docker-compose:

  sf-bullboard:
    container_name: sf-bullboard
    image: deadly0/bull-board
    restart: always
    environment:
      REDIS_HOST: sf-redis
      REDIS_PORT: 6379
      BULL_VERSION: bull
      BULL_PREFIX: sf-bull
    networks:
      - gcp_redis
    ports:
      - 8011:3000

And I am using the same BULL_PREFIX in Bull's Queue Options

@benzavision
Copy link

same issue with env vars :

BULL_PREFIX: 'queue'
BULL_VERSION: 'bull'

@tiagoboeing
Copy link

Same issue here. Does anyone found a workaround?

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

6 participants