-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Same problem with NewRelic #1
Comments
We have the same problem too, trying to upgrade to Python 3.5. It seems to be a problem inside wrapt as opposed to new relic itself. Still investigating... |
I've created this repo to demonstrate the issue to New Relic support team. My initial ticket was created on March 2nd, and here is the answer I got on May the 23rd:
We eventually switched to gunicorn because downgrading Python or Django was not an option for us. For further info, here is the last answer I got on May 31st:
|
Thanks very much. They didn't clarify that it's |
N.B. we did go with |
Thanks guys for your reply, I also go with |
Hello all, I would like to follow up and let everyone know that our Python agent engineers have engaged with the uWSGI team and have received verification that this is an bug with uWSGI and not New Relic. However, the "fix" will be to ensure that the Here is the GitHub Issue filed with uWSGI - unbit/uwsgi#1408 Our official workaround recommendation, until uWSGI releases version 2.1 (which will set Thank you all again for your reports and help with the investigation. |
@andrewgoetz thanks for following up and posting here. In the future you could create a github repo for issue reporting on the python agents so you can message us developers where we are 😉 |
Mobeye/NewRelic#1 Since Lax does not freeze its dependencies, I think we need to do this every time we install with pip
because otherwise a binary (a wheel?) is downloaded that contains the C extensions.
finds no result after installing on a new virtualenv. |
@giorgiosironi read @andrewgoetz message there, there's an official fix/workaround now |
I tried changing the uWSGI options to no avail before, so I'm documenting here the path to correctly avoid installing C extension for the poor souls which will find themselves in the same situation. |
I confirm that avoiding the C extensions seems to solve the problem. |
@giorgiosironi I believe uWSGI v2.0.15 contains a fix which prevents the SystemError issue with wsgi-env-behavior set to cheat. If you upgrade to v2.0.15 and set wsgi-env-behavior=cheat (or avoid setting wsgi-env-behavior) does that eliminate the SystemError? |
As we were on 2.0.14, we set on disabling the C extensions during installation ( |
Hi guys,
did you solve your issue with New Relic? I have the same problem and I can't find any solution. Your repository is the only result when I ask Google.
Best!
The text was updated successfully, but these errors were encountered: