Skip to content
This repository has been archived by the owner on Jun 15, 2021. It is now read-only.

ValueError: There's already an active RQ scheduler #98

Closed
dcloud opened this issue Oct 11, 2016 · 3 comments
Closed

ValueError: There's already an active RQ scheduler #98

dcloud opened this issue Oct 11, 2016 · 3 comments

Comments

@dcloud
Copy link
Contributor

dcloud commented Oct 11, 2016

https://sentry.io/csis/recon-asia/issues/167866733/

ValueError: There's already an active RQ scheduler
(4 additional frame(s) were not displayed)
...
  File "django_rq/management/commands/rqscheduler.py", line 22, in handle
    scheduler.run()

ValueError: There's already an active RQ scheduler

Looks like a side effect of heroku starting new dyno instances before stopping the other ones. Doesn't look like it's having negative side effects, but something to look into.

@dcloud dcloud self-assigned this Oct 11, 2016
@dcloud
Copy link
Contributor Author

dcloud commented Oct 24, 2016

See also rq/rq-scheduler#70. There is an open pull request that could quiet this.

@realnot
Copy link

realnot commented Sep 20, 2019

Each time I deploy an application Sentry return this error. How did you solved?

@shvng
Copy link

shvng commented May 12, 2020

having same issue that @realnot is facing . Using docker container

@dcloud dcloud removed their assignment May 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants