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
Slow execution due to low entropy in /dev/random #10604
Comments
Note: in rare cases the response is immediate |
Replying to [10604 jkvbe]: It takes about 38 minutes.
I confirm behaviour since version 6.9.1.29776. On version 6.8.3.29107 duck CLI was running fine. It is independent from OS version (16.04 or 18.04). No java installed since this is no dependency.
|
Hey, we ran into this today and it appears as though the issues is with the use of /dev/random in certain calls that are being made.
|
Because of this we actually run with |
Suggestion for End-Users: If you need duck to work now, and cannot wait for the devs (sometimes this happens). You can increase the entropy of your systems' /dev/random by using something like haveged. This acts as a quite decent source of randomness to feed /dev/random in a very efficient (non-CPU-intensive) way. And works excellently for VM/containers that have no access to more traditional sources of randomness. There are some other projects and methods but something like haveged should be fairly available and infrastructure independent, so no need to worry about virtio / kvm / qemu ... Also, a big thank you to the cyberduck team for their support. -Edit:* |
Replying to [comment:10 frwessling]: Thanks for sharing this! |
Replying to [comment:11 dkocher]:
My pleasure, glad to help. |
Now documented. |
duck -h
takes more than 5 minutes to execute. I have the impression it runs against a timeout, but I don't see what resources duck needs to print the help information.This happens for each duck command.
The text was updated successfully, but these errors were encountered: