C:\Celery>celeryd --loglevel=DEBUG
celery@Blahhost v1.0.0 is starting.
Configuration ->
. broker -> amqp://m...@127.0.0.1:5672/mainhost
. queues ->
. celery -> exchange:celery (direct) binding:celery
. concurrency -> 1
. loader -> celery.loaders.default
. logfile -> [stderr]@DEBUG
. events -> OFF
. beat -> OFF
. tasks ->
. celery.delete_expired_task_meta
. celery.execute_remote
. celery.map_async
. celery.ping
. celery.task.http.HttpDispatchTask
. tasks.add
Celery has started.
[2010-03-03 02:51:03,703: DEBUG/MainProcess] Instantiating thread
components...
[2010-03-03 02:51:03,717: DEBUG/MainProcess] Starting thread
TaskPool...
[2010-03-03 02:51:03,858: DEBUG/MainProcess] created semlock with
handle 1632
[2010-03-03 02:51:03,858: DEBUG/MainProcess] created semlock with
handle 1620
[2010-03-03 02:51:03,890: DEBUG/MainProcess] Starting thread
Mediator...
[2010-03-03 02:51:03,890: DEBUG/MainProcess] Starting thread
ScheduleController.
..
[2010-03-03 02:51:03,890: DEBUG/MainProcess] Starting thread
CarrotListener...
[2010-03-03 02:51:03,890: DEBUG/MainProcess] CarrotListener: Re-
establishing con
nection to the broker...
[2010-03-03 02:51:03,967: DEBUG/MainProcess] CarrotListener:
Connection Establis
hed.
[2010-03-03 02:51:03,983: DEBUG/MainProcess] CarrotListener: Starting
message co
nsumer...
[2010-03-03 02:51:03,983: DEBUG/MainProcess] CarrotListener: Ready to
accept tas
ks!
celery@Blahhost v1.0.0 is starting.
Configuration ->
. broker -> amqp://m...@127.0.0.1:5672/mainhost
. queues ->
. celery -> exchange:celery (direct) binding:celery
. concurrency -> 1
. loader -> celery.loaders.default
. logfile -> [stderr]@DEBUG
. events -> OFF
. beat -> OFF
. tasks ->
. celery.delete_expired_task_meta
. celery.execute_remote
. celery.map_async
. celery.ping
. celery.task.http.HttpDispatchTask
. tasks.add
Celery has started.
I'm using a bare celeryconfig.py with just the broker configs,
celery_backend = "amqp"
Any hints would be much appreciated!
On Mar 3, 8:52 am, throwness <thrown...@gmail.com> wrote:
> Hi, I hope I didn't miss anything obvious but when I startup celeryd
> (with no daemon managers of any kind), it keeps spawning new celeryd
> processes. Originally I tried it with Python 2.5 and the
> multiprocessing backport, but then I tried it on a fresh machine with
> 2.6 installed, but same thing. This will just keep repeating unless I
> ctrl-c. I tried a number of options (including concurrency=1 but no
> go) Here's what it looks like:
>
>
Apparently celery 1.0 doesn't work well with windows,
and I haven't had the time to look at it yet :(