Skip to content
This repository has been archived by the owner on Oct 16, 2021. It is now read-only.

trouble with node-report with node 12.14.1 on z/OS #164

Open
rpenny125 opened this issue Oct 2, 2020 · 0 comments
Open

trouble with node-report with node 12.14.1 on z/OS #164

rpenny125 opened this issue Oct 2, 2020 · 0 comments

Comments

@rpenny125
Copy link

rpenny125 commented Oct 2, 2020

  • Version: v12.14.1
  • Platform: OS/390 RS28 27.00 04 8561
  • Subsystem:

Problem:

  1. I'm trying to find tools that helps diagnose "apparent loops" in node on z/OS. Specifically, I'd like to be able to see the javascript stack, either from a running node process on z/OS, or from a system dump of the address space (the latter would be a "node" equivalent of the java tool jdmpview)
  2. I think that the npm package node-report sounds like a useful tool, as it means I could issue "kill -USR2 " to force node to write out javascript information.
  3. An old blog about IBM's node SDK suggests that node-report is "pre-installed" (https://developer.ibm.com/node/2017/03/10/node-report-now-available-ibm-sdk-node-js/)
  4. when I try to use "-r node-report" on my node command line, this is the result:
    Error: Cannot find module 'node-report'
  5. if I try to install node-report using "npm install node-report", the "make" fails (see below):
    RS25:ctds/tep~/repos/omegcc/web-tep-cap/ctds/tep> npm i node-report

node-report@2.2.11 install /proj/kbm/pdpenn/repos/omegcc/web-tep-cap/ctds/tep/node_modules/node-report
node-gyp rebuild

make: Entering directory '/proj/kbm/pdpenn/repos/omegcc/web-tep-cap/ctds/tep/node_modules/node-report/build'
CXX(target) Release/obj.target/api/src/node_report.o
make: njsc++: Command not found
make: *** [api.target.mk:114: Release/obj.target/api/src/node_report.o] Error 127
make: Leaving directory '/proj/kbm/pdpenn/repos/omegcc/web-tep-cap/ctds/tep/node_modules/node-report/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/proj/mvd/node/installs/node-v12.14.1-os390-s390x/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:223:5)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System OS/390 27.00
gyp ERR! command "/proj/mvd/node/installs/node-v12.14.1-os390-s390x/bin/node" "/proj/mvd/node/installs/node-v12.14.1-os390-s390x/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /proj/kbm/pdpenn/repos/omegcc/web-tep-cap/ctds/tep/node_modules/node-report
gyp ERR! node -v v12.14.1
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"os390","arch":"s390x"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-report@2.2.11 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-report@2.2.11 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /proj/kbm/pdpenn/.npm/_logs/2020-10-02T17_33_04_737Z-debug.log

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant