Doesn't seem to like Redis about flower HOT 5 CLOSED

This doesn't look like a flower issue. Can you try 'celery inspect registered' command?

from flower.

Output of command requested:

celery inspect registered --broker=redis://lochost:6379/2
-> portal.mydomain.ca: OK
* celery.backend_cleanup
* celery.chain
* celery.chord
* celery.chord_unlock
* celery.chunks
* celery.group
* celery.map
* celery.starmap
* support.tasks.check_mail_task
* utils.tasks.send_mail_task

A bit more info:

Workers now shows my portal worker process (not the www which is what I would expect). However the errors in the www site flow as they did yesterday.

from flower.

For the workers not showing up, do you have the yajl json library install by chance?

from flower.

@volksman could you create a minimal project which demonstrates the problem? All our tests didn't reveal anything suspicious. Also it would be useful to have the output of 'celery report' and 'flower --logging=debug'.

from flower.

Hi, I got the same problem. Its not related to flower. On my server I have 3 Django projects running celery with redis. Each project uses a separate redis DB. Project1 and Project2 use the same pluggable app, so many workers got the same name (i.e. Project1.MyPluggableApp.MyTask and Project2.MyPluggableApp.MyTask). When I start Project2's worker while Project1's worker is already running the above error occurs. But it doesnt occur when I start Project3, which has other tasks-names (i.e. Project3.OtherApp.OtherTask). So I guess its somehow related to naming conventions of worker-names or ids within the redis db.

This is my traceback: http://nopaste.info/c54cc5f020.html

from flower.