RabbitMQ now seems to be working correctly. However, when I try
python -m celery.bin.celeryd --loglevel=INFO`
(regular celeryd doesn’t work), I get the error
No handlers could be found for logger “multiprocessing”`).
Here’s the full output (redacted slightly):
[2011-06-06 02:08:08,105: WARNING/MainProcess] -------------- celery@blahblah v2.2.6
---- **** -----
--- * *** * -- [Configuration]
-- * - **** --- . broker: amqplib://blah@localhost:5672/vhost
- ** ---------- . loader: celery.loaders.default.Loader
- ** ---------- . logfile: [stderr]@INFO
- ** ---------- . concurrency: 2
- ** ---------- . events: OFF
- *** --- * --- . beat: OFF
-- ******* ----
--- ***** ----- [Queues]
-------------- . celery: exchange:celery (direct) binding:celery
[Tasks]
. tasks.add
[2011-06-06 02:08:08,812: WARNING/MainProcess] celery@blahblah has started
.
No handlers could be found for logger "multiprocessing"
No handlers could be found for logger "multiprocessing"
I’d really like to get this set up properly, so I can move on to using it with Django!
(It is not my first no handlers found error, but I’m having trouble finding anything on the web regarding this…)
There seems to be something strange in the way celery initializes logging. If I put the switch
--logfile=yourfile.logon the command-line, it works reliably, but reading the logging from the config gives unreliable results including the stuff you’re seeing.