osrandom engine already registered #2287
Comments
|
Hey @komakino, this usually happens when using threading. Can you confirm that the "kodi addon" is using threading? Also can you link to that project since I have no clue what project it is. |
|
Also, can you include the version of "kodi" that you're using, the version of requests that's installed, and the version of cryptography in use? |
|
I remain baffled as to how this condition can occur under the threading lock we have. 😢 |
|
Kodi: 15.1 Git:d496682 |
|
thats my addon, that I'm developing. I do not use threading. I also tested in a "clean" addon, just importing requests and got the same results. |
|
Oh, and cryptography is 1.0 |
|
@komakino does that plugin get imported by something using threading? What is kodi a plugin for? |
|
I'm seeing the same thing in a Django app running under mod_wsgi which is triggered as soon as something imports requests (I noticed it with raven-python but even a simple import requests fails in the threaded WSGIDaemon environment): |
|
Let me see how simple I can make it – my app isn't simple but I could reproduce simply by tossing |
|
Yeah, even this will trigger it with the import requests line uncommented: #!/usr/bin/env python
# encoding: utf-8
# import requests
def application(environ, start_response):
status = '200 OK'
output = 'Hello World!'
response_headers = [('Content-type', 'text/plain'),
('Content-Length', str(len(output)))]
start_response(status, response_headers)
return [output]Relevant Apache config: WSGIDaemonProcess example user=example-site group=www-data processes=8 threads=8 maximum-requests=20000 shutdown-timeout=120 deadlock-timeout=60 display-name=example home=/opt/example python-path=/opt/example/.virtualenv/lib/python2.7/site-packages
WSGIImportScript /opt/example/example_wsgi.py application-group=example process-group=example
WSGILazyInitialization On
WSGIRestrictEmbedded On |
|
This is related to the subinterpreters used by mod_wsgi. We're tracking this in #2299. |
|
One of our Emby users is experiencing this issue (log is attached in the post): http://emby.media/community/index.php?/topic/25735-emby-for-kodi-broken-no-sync/ Is there anything we can do on our side to prevent this error from happening? So far, it seems to affect only one user. Emby add-on for Kodi: https://github.com/MediaBrowser/Emby.Kodi |
|
The issue might come from Kodi and not Emby, I experienced similar errors (osrandom engine already registered) in Kodi with addons requesting connection to websites (trakt.tv). Note that I'm a noob user, not a developper. All the info are in the same emby.media thread : |
|
For the record: #2293 fixed this problem for me (see also #2299 (comment) ) |
|
This is merged! |
|
Hi, Is there actually a fix for this in Kodi? On Ubuntu 15.10 the python libs are sufficiently different that the fix on 2293 doesn't apply cleanly (plus I'd be updating system .py files). |
|
@micahg try installing cryptography 1.1 from pip, which contains this change. To do this you may need to uninstall python-cryptography from apt though. |
|
@reaperhulk that worked, tyvm. |
|
This nonsense happened to me today in Kodi running on Linux. It killed the YouTube plugin dead so it wouldn't even start up. I had to resort to deleting python cryptography and python openssl on the underlying Linux system that hosts my Kodi box using the package manager. You'd think after the number of years this issue has existed someone would have fixed it. |
|
@TheRealTachyon You might think that someone would have fixed it...and in this case you would be right. This was an extremely complex issue to fix due to the interplay between cryptography, applications that embed a Python interpreter, and the way dynamically loaded C libraries work. However, due to the hard work of several people a major (and completely transparent!) change was landed in version 1.7 to entirely resolve this problem (#3229). Of course, the nature of linux distributions is that they don't pick up the latest versions of things instantaneously. Instead, users who choose to utilize packages in this fashion will typically be locked into whatever version their distribution ships until they upgrade to the next major release. In some cases backports may occur, but person power in open source projects is limited and priority is not given to such endeavors. We're glad you've resolved the issue to your satisfaction, and it is unfortunate that it occurred in the first place, but in general you might want to consider a few things in the future before commenting on GitHub issues:
|
|
To address your points.
I did quite a bit of research into this issue before deciding to post here and frankly a lot of what I saw involved a lot of passing the buck as to where the source of the issue lay. Congrats to the team here for taking it on and resolving it, but.... The fact that this was so easily re-triggered clearly indicates that this issue's solution has either not been fully fixed, or has not permeated downstream to everyone using it. And BTW, I do not run auto-updates on my systems, so there was not an OS update between yesterday when it worked and this morning when it didn't. This means that the error happened due to a client side change since only Kodi and it's add-ons auto-update on this system. That implies to me that the issue is not fully fixed. If it were fixed properly, you would not be able to break it again in normal usage. |
|
You do not have a recent enough version of cryptography. cryptography 1.7 (released in December 2016) contains the fix. Without the latest version you can potentially see this problem. Your "quite a bit" of research apparently did not extend to actually trying to see if newer versions than the one conveniently provided by your linux distribution (1.0 for the record. A version released in August of 2015) might resolve the issue. This is not a productive avenue of discussion so I'll go ahead and lock this conversation. If you see this problem with the latest version please file a new issue. |
Getting "osrandom engine already registered" from cryptography module when including requests in kodi addon.
http://xbmclogs.com/pq07deaup
I'm on Ubuntu 14.04 LTS based system with python 2.7.6.
The text was updated successfully, but these errors were encountered: