Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Transaction ended but current_node is not Sentinel

errors

#1

We received the following error:

Transaction ended but current_node is not Sentinel. Current node is <FunctionTrace {'terminal': 
 False, 'group': 'Function', 'name': 'django.core.handlers.wsgi:WSGIHandler._get_response', 
    'params': None, 'rollup': None, 'label': None}>. Report this issue to New Relic support.
  File "/venv/app/lib/python2.7/site-packages/gevent/baseserver.py", line 26, in _handle_and_close_when_done
    return handle(*args_tuple)
  File "/venv/app/lib/python2.7/site-packages/gunicorn/workers/ggevent.py", line 155, in handle
    super(GeventWorker, self).handle(listener, client, addr)
  File "/venv/appl/lib/python2.7/site-packages/gunicorn/workers/async.py", line 56, in handle
    self.handle_request(listener_name, req, client, addr)
  File "/venv/app/lib/python2.7/site-packages/gunicorn/workers/ggevent.py", line 160, in handle_request
    addr)
  File "/venv/appl/lib/python2.7/site-packages/gunicorn/workers/async.py", line 107, in handle_request
    respiter = self.wsgi(environ, resp.start_response)
  File "/venv/app/lib/python2.7/site-packages/newrelic/api/web_transaction.py", line 1285, in _nr_wsgi_application_wrapper_
    transaction.__exit__(*sys.exc_info())

Python: 2.7.5
gevent: 1.3.5
gunicorn: 19.8.1
newrelic: 3.2.0.91

We don’t necessarily need assistance, per se. I’m just reporting the issue, as the traceback requested – please let me know if there is a more appropriate interface for making this report.


#2

@jleadbetter Thanks for your post and for brining this issue to our attention. I’ve confirmed with our engineers that this is the result of a bug in the agent. We believe we have enough to reproduce this issue. Thanks again for your help.


#3

Any news about this?
Is it fixed?
I’m getting this error using Tornado (with Python 2.7).


#4

Hi rodolfo, which agent version are you using? This has been fixed since Python Agent 4.6.0.106. :slight_smile: