-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
[bug] Django migration fails: possibly misconfigured celerydb #272
Comments
@Doralitze what is the OS of the target machine? |
output from output from
|
Hi @Doralitze, I was not able to replicate this issue on my Ubuntu 18.04 machine. But, here are some pointers to help us find out the possible reason for this error.
In this example, the number of databases is 16 Alternatively, you can check via
|
Hi @pandafy I was following your steps
I indeed I got the same result.
Said command outputs Thanks a lot for your help dough! |
A quick grep of the README revealed that celery uses Database 3 by default and since redis databases are 0 indexed it couldn't have worked. Looks like i missed that when upgrading my controller instance. I'm truly sorry that I wasted your time for something that collapses to RTFM but I'm really glad you put me on the right spot. Again: Thanks a lot for your help. |
No worries @Doralitze! It was a learning experience for me as well. I am glad that you got it working. 👍🏼 |
when running the playbook the step
openwisp.openwisp2 : migrate
fails.This is the stack trace:
According to this issue this is a misconfiguration of the celery database connection hence Iḿ reporting this here.
In case it's useful I've posted my playbook configuration below:
I'm hoping someone can help me with this.
The text was updated successfully, but these errors were encountered: