what's the error and traceback? (paste at pastie.org or similar)

Preface this by saying that I've been successfully and happily using celery since 0.8, which was over 2 years ago. Since 2.0, it's been rock solid. But then I switched from RabbitMQ to redis and when I added redis slaves, it broke.

Here goes: http://pastie.org/4216467

It's probably due to redis' INFO command giving different values. Now would be a great time to get it sorted out, too.

About your error, seems strange that a simple info command gives that error, maybe you're running an outdated version of redis-py/redis-server?

Latest redis (2.4.15) and using redis-py 2.4.10. Just checked the CHANGELOG for redis-py, which is now at 2.4.13, and voila:

    * 2.4.11
        * Made the INFO command more tolerant of Redis changes formatting. Fix for #217.

Doh! Off by a single patch release. Thanks for the help.

See, folks? Celery is amazing in multiple ways.

no i am not, sorry