As I delve into this tutorial for guidance, my aim is to successfully execute the node example.
After downloading the folder and navigating to the directory, I attempted running npm install.
Here is the stack trace that was generated.
npm WARN package.json <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="6c0b1e1c0f4109140d011c00091f2c5c425d425c">[email protected]</a> No repository field.
npm WARN package.json <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="d0b7a2a0b3fdb5a8b1bda0bcb5a390e0fee1fee0">[email protected]</a> No license field.
\
> <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="375045475477061906051905">[email protected]</a> install /tmp/grpc/examples/node/node_modules/grpc
> node-pre-gyp install --fallback-to-build --library=static_library
node-pre-gyp WARN Tried to download(400): https://storage.googleapis.com/grpc-precompiled-binaries/node/grpc/v1.12.2/node-v46-linux-x64-glibc.tar.gz
node-pre-gyp WARN Pre-built binaries not found for <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="1a7d686a795a2b342b283428">[email protected]</a> and <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="335d5c575673071d061d03">[email protected]</a> (node-v46 ABI, glibc) (falling back to source compile with node-gyp)
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: unable to verify the first certificate
gyp ERR! stack at Error (native)
gyp ERR! stack at TLSSocket.<anonymous> (_tls_wrap.js:1022:38)
gyp ERR! stack at emitNone (events.js:67:13)
gyp ERR! stack at TLSSocket.emit (events.js:166:7)
gyp ERR! stack at TLSSocket._init.ssl.onclienthello.ssl.oncertcb.TLSSocket._finishInit (_tls_wrap.js:586:8)
gyp ERR! stack at TLSWrap.ssl.onclienthello.ssl.oncertcb.ssl.onnewsession.ssl.onhandshakedone (_tls_wrap.js:428:38)
gyp ERR! System Linux 4.8.13-100.fc23.x86_64
gyp ERR! command "/home/nbkiq0w/.nvm/versions/node/v4.5.0/bin/node" "/home/nbkiq0w/.nvm/versions/node/v4.5.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--libr$ry=static_library" "--module=/tmp/grpc/examples/node/node_modules/grpc/src/node/extension_binary/node-v46-linux-x64-glibc/grpc_node.node" "--module_name=grpc_node" "--module_path=/tmp/grpc/examples/node/node_mo$ules/grpc/src/node/extension_binary/node-v46-linux-x64-glibc" "--node_abi_napi=node-v46"
Although there are more details in the stack trace, this summary captures the main points.
Unable to verify the first certificate
This appears crucial to my issue at hand.
After some online search, I came across this, which seemed relevant. I made adjustments to the provided code snippet,
examples/node/dynamic_codegen/greeter_server.js
To include the following lines at the beginning of the file.
var rootCas = require('ssl-root-cas/latest').create();
rootCas
.addFile('/etc/pki/ca-trust/source/anchors/amrs-g2.cer');
require('https').globalAgent.options.ca = rootCas;
Following a pattern from this page. However, the issue persists despite these changes. Any suggestions or insights? It's worth noting that I am using node version 4.5.0 and npm version 2.15.9.
Despite some trial and error with versions, I haven't been able to resolve the situation.
Update 1:
Attempted updating node version to 10.0.0, Npm version 5.6.0
Ran npm install again, encountered an unusual error this time...
npm install
npm ERR! code E418
npm ERR! 418 I'm a teapot: async@^1.5.2
Update 2:
Repeating the command multiple times revealed inconsistent library failures.
npm ERR! code E418
npm ERR! 418 I'm a teapot: grpc@^1.0.0
^C
[nbkiq0w@localhost node]$ npm install
npm ERR! code E418
npm ERR! 418 I'm a teapot: google-protobuf@^3.0.0
^C
[nbkiq0w@localhost node]$ npm install
npm ERR! code E418
npm ERR! 418 I'm a teapot: lodash@^4.6.1
^C
[nbkiq0w@localhost node]$ npm install
npm ERR! code E418
npm ERR! 418 I'm a teapot: grpc@^1.0.0
^C
[nbkiq0w@localhost node]$ npm install
npm ERR! code E418
npm ERR! 418 I'm a teapot: lodash@^4.6.1
The continual failures seem indiscriminate among libraries. I tried adjusting proxy settings as suggested here, but to no avail.
Update 3:
Switched back to node 6.12.0, encountering the original tls error. A friend successfully ran the same code on their machine (using 6.12.0), indicating that the issue may be specific to my setup.