<html><head></head><body>Oops, I didn't see Ken's reply where he already figure this out (spotty cell service).<br>
<br>
Where I work we were having this issue when bringing up new VMs. While provisioning, it would seem to just hang for 10 or 15 minutes when installing packages. No cpu usage, no disk io, no network io. And every time you'd ssh in to the VM to run top, it'd start going again. Very frustrating. Simply installing haveged first fixed the issue.<br>
<br>
-Dennis<br><br><div class="gmail_quote">On August 8, 2017 5:47:11 PM EDT, Dennis Straffin <dennis@straffin.net> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
VMs lack hardware devices to fill up the pool of random numbers. Installing the haveged daemon will do expansion on the random numbers to keep the pool full.<br />
<br />
-Dennis<br /><br /><div class="gmail_quote">On August 8, 2017 3:30:46 PM EDT, Ken D'Ambrosio <ken@jots.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 2017-08-08 15:18, Joshua Judson Rosen wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> The /dev/random interface is considered a legacy <br /> interface, and<br /> /dev/urandom is preferred and sufficient in all use cases, <br /> with the<br /> exception of applications which require randomness during <br /> early boot<br /> time; for these applications, getrandom(2) must be used <br /> instead,<br /> because it will block until the entropy pool is initialized.<br /> <br /> So, there you go. "until the entropy pool is initialized" is apparently<br /> about 3 minutes in your case ;)<br /></blockquote><br />Yeah... getrandom() apparently pings /dev/urandom by default which, as <br />per the getrandom manpage, blocks until it has entropy. Sounds like <br />we've wound up at much the same place: I took some data off of <br />/dev/random, stored it in a file, and am feeding that to /dev/urandom at <br />boot time (and re-seeding the file after five minutes' uptime). Alas <br />(because, you know, deadline), that doesn't seem to be working. Which <br />is really, really annoying. I'm *still* blocking for three-to-five on <br />getrandom().<br /><br />I guess it's time to cut my losses and start this in a different <br />language. I mean, most of the hard stuff was figuring out *how* to do <br />things, but I admit, my Perl and Python have grown rusty as I've enjoyed <br />my Ruby...<br /><br />-Ken<br /><hr /><br />gnhlug-discuss mailing list<br />gnhlug-discuss@mail.gnhlug.org<br /><a href="http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss">http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss</a>/<br /></pre></blockquote></div><br /></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>