#celery

as this may cause problems for things that widly imports stuff

wildly

like kombu.tests.setup: https://github.com/celery/kombu/blob/master/kom...

let me see

guarding the monkey patches is an ok idea, but what would call it exactly once and early?

asksol: ^

kombu.transport.qpid.Transport?

is anything special needed to use celery tasks from within a django-admin.py command ?

make sure proj/__init__.py imports the proj.celery module

and the settings import proj (which it will when settings is set to 'proj.settings')

dpn`, This was the error: Should have used "python manage.py celery worker --loglevel=INFO --beat --settings=settings.staging" instead of "python manage.py celery worker --loglevel=INFO --settings=settings.staging --beat" :)

It was not a problem with supervisord at least.

asksol: thanks, i realise that i'm still using djcelery too so i'll look into the proper way to do things

Paul___: I got flower to start with qpid

Paul___ were you able to file that bug upstream against celery/kombu

bmbouter: not yet :)

I am still stuck at connection refused

connection timed out sorry

do you specify an app when you start flower ?

-A=pulp.server.async.app or something like that ?

I installed flower on the same server as Pulp & qpid

now I have this warning : /usr/lib/python2.6/site-packages/kombu/transport/qpid.py:274: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 if self.allowed_exception_string not in error.message:

that warning is OK

Paul___: I start mine like this

and I have qpidd with auth=no for testing purposes

flower -A=pulp.server.async.app --port=8090 --broker=qpid://localhost/

it's running I forgot to allow 9000 in my security group

that unicode error was because I was using guest@localhost and qpid.messaging fails if the username is unicode

so you should use the default username of 'guest'

and file the bug upstream against kombu so I can fix it before the 3.0.24 release

it is running, but I don't see any workers or tasks in the ui

that's as far as I got, I hope to get furhter, but first ... lunch

I see this output

and now I understand why I had the connection timed out => security group issue !

awesome

the one line I find interesting is this one

[E 141029 12:45:22 state:52] Dashboard and worker management commands are not available for 'qpid' transport

ok brb in 30

celery/celery#2284 (3.1 - daf70d4 : Ask Solem): The build passed.

Change view : https://github.com/celery/celery/compare/11ca54...

Build details : http://travis-ci.org/celery/celery/builds/39407926

Paul___ I think we're both at the same point

flower starts, but doesn't show workers

it does show me the workers on the graphs on /monitor, but not the workers under /workers