Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue starting 3.0.9 on Heroku

See original GitHub issue

Anyone had any luck getting 3.0.9 to start on Heroku? I’m having it crash with this in the log:

billiard==2.7.3.12 celery==3.0.9 Django==1.4.1 django-celery==3.0.9

2012-09-12T14:03:04+00:00 app[celeryd.1]: *** glibc detected *** /app/.heroku/venv/bin/python: munmap_chunk(): invalid pointer: 0x00007fa4e8bc4dac ***
2012-09-12T14:03:04+00:00 app[celeryd.1]: ======= Backtrace: =========
2012-09-12T14:03:04+00:00 app[celeryd.1]: /lib/libc.so.6(+0x775b6)[0x7fa4ebd735b6]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/lib/python2.7/site-packages/_billiard.so(+0x449b)[0x7fa4e924c49b]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x44f553]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x46dc37]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x44f553]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x46dc37]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x43e712]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x5110f3]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x44f553]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x427134]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x50cb83]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x4d58e3]
2012-09-12T14:03:04+00:00 app[celeryd.1]: /app/.heroku/venv/bin/python[0x4d58f3]
2012-09-12T14:03:04+00:00 app[celeryd.1]: ======= Memory map: ========

Issue Analytics

State:
Created 11 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

askcommented, Nov 11, 2013

Note that using the Django/SQLAlchemy transports in production is a bad idea. I have no idea why billiard does not work well on this platform as I have had not had any reports of this happening outside of Heroku.

0reactions

dstegelmancommented, Dec 27, 2012

I am also having this issue. Passing a custom settings structure --settings=settings.whatever breaks the worker, but adding --no-execv seems to resolve the issue.