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

No jobs displayed #14

Open
dazza-codes opened this issue Jun 9, 2021 · 1 comment
Open

No jobs displayed #14

dazza-codes opened this issue Jun 9, 2021 · 1 comment

Comments

@dazza-codes
Copy link

With a single worker paused and many jobs queued up, the "Jobs" table has no entries. The redis memory display grows in size as more jobs are submitted, but nothing shows in the rqmonitor display. The queues are called "high", "medium" and "low". There appears to be no way to "select" a queue for the "Selected Queues" and that list is empty. The jobs are submitted to the "high" queue and the "Queues" display shows that it has 60 jobs in the queue. Why does the "Jobs" display show no details of the jobs in the queue?

versions

$ poetry show rq
name         : rq
version      : 1.8.1
description  : RQ is a simple, lightweight, library for creating background jobs, and processing them.

dependencies
 - click >=5.0.0
 - redis >=3.5.0

$ poetry show rqmonitor
name         : rqmonitor
version      : 1.0.1
description  : Flask based dynamic and actionable dashboard for monitoring RQs

dependencies
 - Click >=7.0
 - fabric >=2.5.0
 - Flask >=1.1.1
 - humanize >=2.4.0
 - invoke >=1.4.1
 - redis >=3.3.11
 - rq >=1.2.0
 - six >=1.13.0
 - Werkzeug >=0.16.0

docker compose

version: '3.7'
services:
  rq-server:
    image: redis:alpine
    ports:
      - 6379:6379

  rq-worker:
    image: my-rq-worker
    depends_on:
      - "rq-server"
    command: rq worker -u redis://rq-server:6379 high medium low

  rq-monitor:
    image: pranavgupta1234/rqmonitor
    depends_on:
      - "rq-server"
    environment:
      - RQ_MONITOR_REDIS_URL=redis://rq-server:6379
    ports:
      - 8899:8899
@dazza-codes
Copy link
Author

dazza-codes commented Jun 9, 2021

The -v option was enabled and then only after a docker-compose down and a restart did rqmonitor discover the "high" queue and started to show jobs from that queue. It did not pick up the "medium" or the "low" queues. Something about the addition of a -v option might have changed how the jobs/selected-queues behave (although it doesn't really make sense that it should do so).

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

1 participant