OpenSSL Issue about node-opcua-logger HOT 3 OPEN

I have the same issues, both unexperienced and "Can't load /home....../random.rnd into RNG":
My versions are:

user@computer:~/node-opcua-logger$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
user@computer:~/node-opcua-logger$ openssl version
OpenSSL 1.1.1 11 Sep 2018
user@computer:~/node-opcua-logger$ node --version
v8.10.0

I don't know how to tell if openssl is correctly installed...

As far as I can understand I miss these files:
/node-opcua-logger/node_modules/node-opcua-client/certificates/PKI/own/private/random.rnd
and
/node-opcua-logger/node_modules/node-opcua-server/certificates/PKI/own/private/random.rnd
and
/node-opcua-logger/node_modules/node-opcua-server-discovery/certificates/PKI/own/private/random.rnd

Thanks!

Resolved by doing this...
sudo openssl genrsa -out "/home/user/node-opcua-logger/node_modules/node-opcua-server-discovery/certificates/PKI/own/private/private_key.pem" 2048
sudo openssl genrsa -out "/home/user/node-opcua-logger/node_modules/node-opcua-server/certificates/PKI/own/private/private_key.pem" 2048
sudo openssl genrsa -out "/home/user/node-opcua-logger/node_modules/node-opcua-client/certificates/PKI/own/private/private_key.pem" 2048
cd /home/user/node-opcua-logger/node_modules/node-opcua-client
node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_1024.pem
cd ../node-opcua-server
node test_helpers/create_certificates.js certificate -s -o certificates/server_selfsigned_cert_2048.pem
cd ../node-opcua-server-discovery/
node test_helpers/create_certificates.js certificate -s -o certificates/server_selfsigned_cert_2048.pem

not sure if the sudo bit on openssl commands is really necessary...

from node-opcua-logger.

Hi, can you specify some details about your environment?

• OS?
• Node version
• Is openssl installed correctly? Which version?

from node-opcua-logger.

Hi @AWanderingEngineer,

certificate generation is done by the underlying node OPCUA library, and I've had problems with it before. Could you try this with the new version (v2) of the logger, which also contains a much more recent version of the node-OPCUA library? Even better, if you download a binary from the release page, you don't need to generate anything yourself.

from node-opcua-logger.