#celery

xkillac4: wrt your rate limiting question, celery doesn't provide anything for that ... you'll have to build something yourself

here's an example of somebody doing something with lua/redis: https://callhub.io/blog/2014/02/03/distributed-...

(not an endorsement)

frege: re: celery web interface, are you looking for something like this? http://celery.readthedocs.org/en/latest/usergui...

dgouldin: thanks for the link, when I have some more time on my hands I'd like to put something like that together. For now I'm just going to separate that task into a separate queue and have a single worker

xkillac4: that's a common stopgap

xkillac4: I can't figure out how to link to a specific slide, but look at slide 42 in my presentation here: https://speakerdeck.com/dgouldin/using-celery-w...

video: http://www.youtube.com/watch?v=z751qhAzMb4

time at which I start talking about that slide: http://www.youtube.com/watch?v=z751qhAzMb4#t=1249

nice, thanks

I'm trying to run celery with a rabbitmq broker but when I start the workers they core dump after ~ 1 second with this message: "Segmentation fault (core dumped)" any idea why this may be happening?

pachi, any logs/outputs would be appreciated

pachi: you can also get a stacktrace from coredump

it usually reveals some library call (and you find an incompatible library version)

This is the output I get: http://pastebin.com/PZzp9pdD

the problem is I don't get too much information so I'm a bit lost here

would some other logs be useful to you?

these systems are all installed using ubuntu14.04 packages, no pip or other not ubuntu-curated packages

pachi: you need to open the core dump in a gdb

some more information (/var/log/celery/worker1.log) in http://pastebin.com/VJTieK5m

moo-_-: ok, would you mind helping me to do it? what do I need to do?

gdb before the celery worker call?

pachi: I am no expert myself

pachi: but this should do it http://stackoverflow.com/a/22711917/315168

pachi: if the core dump happens everyt ime

yes, I can reproduce it always

then you can start application with gdb directly

will try that and report here, thanks

and gdb will hit debugger when the dump happens

ok

moo-_-: interesting, it indeed fails in the librabbitmq1 lib and I've just found this related debian bug report on librabbitmq1 being too old https://bugs.debian.org/cgi-bin/bugreport.cgi?b...