<!-- Thank you for reporting a possible bug in Node.js. Please fill in as much of the template below as you can. Version: output of `node -v` Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows) Subsystem: if known, please specify the affected core module name If possible, please provide code that demonstrates the problem, keeping it as simple and free of external dependencies as you can. --> * **Version**: 10.17.0 (however all Node.js versions with OpenSSL 1.1.1d seem to be affected) * **Platform**: "SUSE Linux Enterprise Server 12 SP4" Linux frdgosdpdbs1 4.12.14-95.19-default #1 SMP Tue Jun 11 11:04:48 UTC 2019 (a904a7f) ppc64le ppc64le ppc64le GNU/Linux * **Subsystem**: crypto <!-- Please provide more details below this comment. --> I have observed an issue with Node.js versions using OpenSSL 1.1.1d on a ppc64le machine where the entropy cannot be initialized when calling randomBytes: ``` internal/crypto/random.js:118 if (ex) throw ex; ^ Error: error:2406C06E:random number generator:RAND_DRBG_instantiate:error retrieving entropy at handleError (internal/crypto/random.js:117:14) at Object.randomBytes (internal/crypto/random.js:52:19) ``` This behavior is observed directly after the Node.js application was started and after randomBytes was called. It seems to be the same issue as reported here: [http://lists.openembedded.org/pipermail/openembedded-core/2019-September/287081.html](http://lists.openembedded.org/pipermail/openembedded-core/2019-September/287081.html)