-
Notifications
You must be signed in to change notification settings - Fork 37
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
Unknown command celeryd for biocloudcentral/manage.py #43
Comments
This could have something to do with RHEL as I've only installed this on Ubuntu but nothing jumps at me. With the virtualenv activated, what do you see when you issue
While you're at it, I'd sugges updating bioblend to what's in git as some of the recent changes to Cloud Launch require the still unreleased bioblend changes. Just use this command: |
I installed the updated bioblend changes as requested with no luck. I'm happy to supply whatever else. RHEL is frustrating indeed. I'm not sure why the output of manage.py --help is such... do you see something else in your build? /srv/cloudlaunch >pip freeze |
@afgane is does your manage.py script have the "celeryd" command? |
Yes it does. I'm working on an Ansible role to automate the installation process and hopefully help that way. In a basic format, it should be ready today but at least in this iteration it'll still be Ubuntu-only. Can you get a Ubuntu-VM instead of the RHEL? |
Here's the Ansible playbook I mentioned: https://github.com/afgane/ansible-cloudlaunch If you can get access to a Ubuntu machine, feel free to try it out and let me know if you run into any problems. If you'd like to add support for installing the app on a CentOS machine via a PR, we'd appreciate it (or you can send me required system package names and I'll eventually add it). |
I also notice that you have some extra python libs and also that some are different versions than what's provided in |
It turns out something went wrong with my virtualenv that was triggering the issue. I recreated the virtualenv, got supervisor working, and nginx launched. I encountered another issue with the celery.d process terminating with no error to the supervisor log. Thanks for helping me fix this issue @afgane |
Hello again,
I took advice from #42, setting up a fresh instance on a linux workstation, RHEL6 with pyenv-virtualenv. I took your suggestion @afgane and decided to install according to the repository's instructions. I manage fine until I receive the following error while starting supervisor. I notice that the celeryd command line tool is available(see below), although this subcommand is not available to manage.py
From the supervisor log (/srv/cloudlaunch/cloudlaunch/supervisor.log):
The text was updated successfully, but these errors were encountered: