Stack traces are sometimes "missing" #544

obeattie opened this Issue Jul 13, 2012 · 1 comment


None yet
1 participant

As discussed on the IRC channel with @dcramer yesterday, it seems that in some instances, stack traces can be missing from some of the events in my Sentry instance. The trace instead shows a single frame, which is a raise directive (in Django), which should obviously preserve the stack trace.

If this is something that you'd consider to be out of scope of Sentry, and caused at a higher level (either by Django or Python, at a guess), I'd be happy to take it up with those guys, but the responses from there previously has always been "it can't be us, take it up with Sentry" so it would good to have something like this ticket to point to.

More about the environment:

  • Ubuntu 12.04 LTS
  • Python 2.7.3 (from the Ubuntu dpkg)
  • Django 1.4.0
  • Raven 2.0.0
  • Sentry 4.8.0 (on Postgres/RabbitMQ)

The stack traces we're seeing instead of the actual error:

TypeError: must be string, not

Stacktrace (most recent call last):

  File "django/core/handlers/", line 121, in get_response

The raw JSON data for this particular event

As mentioned on IRC, this is not limited to a single error, but seems to happen for approx. half of the exceptions we see in production. It seems to consistently happen for the same error cases, however.

obeattie commented Sep 6, 2012

I'm going to close this, as after some further investigation I don't think this is an issue with Sentry (or Django, or Python). The culprit here seems to be either gevent or psycopg2, and it appears to be a manifestation benoitc/gunicorn#214.

obeattie closed this Sep 6, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment