PID check failed. RNG must be re-initialized after fork()
Bug #649158 reported by
Hugo Bernier
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
paramiko |
Confirmed
|
Undecided
|
Unassigned | ||
paramiko (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This bug has already been reported at the website below.
http://
This issue occurs with paramiko 1.7.6 and pycrypto 2.1.0 on Arch Linux.
The website above links to a git diff:
http://
I applied it and it resolved the issue.
Changed in paramiko (Ubuntu): | |
status: | New → Confirmed |
tags: | added: patch |
To post a comment you must log in.
Here is some more background on how to reproduce the problem. Theoretically, you would have to have access to multiple ssh servers to reproduce it, though I'm not sure how many.
I use paramiko on top of the multiprocessing library, using queues to feed tasks to threads. Each thread or worker imports the paramiko module, and using a library we developed for internal use, does RPC on hundreds of linux machines simultaneously. I run 64-128 threads at a time so I'm not sure at what point the issue occurs.