|
From: "Steve M" <txpenguin1@xxxxxxxxxxx>afterwards.
To: "'Jesse Gorzinski'" <jgorzins@xxxxxxxxxx>, "'IBMi Open Source
Roundtable'" <opensource@xxxxxxxxxxxxxxxxxx>
Cc: "'OpenSource'" <opensource-bounces@xxxxxxxxxxxxxxxxxx>
Date: 10/15/2020 08:22 AM
Subject: [EXTERNAL] RE: [IBMiOSS] NPM Issue
Jesse, ? I try to follow the advice of others and not use QSH.? My
failures were using...
This Message Is From an External Sender
This message came from outside your organization.
Jesse,
I try to follow the advice of others and not use QSH. My failures
were using both BitVise SSH Client and using PuTTy.
I did try QSH just now, and received this:
$
node -v
v12.18.4
$
npm -v
[6286]: ../src/node_platform.cc:62:std::unique_ptr<unsigned int>
node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start():
Assertion `(0) == (uv_thread_create(t.get(), start_thread, this))'
failed.
qsh: 001-0078 Process ended by signal 5.
$
Steve
From: Jesse Gorzinski <jgorzins@xxxxxxxxxx>
Sent: Wednesday, October 14, 2020 19:48
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxxxxxxxx>
Cc: OpenSource <opensource-bounces@xxxxxxxxxxxxxxxxxx>; Steve M
<txpenguin1@xxxxxxxxxxx>
Subject: Re: [IBMiOSS] NPM Issue
I assume you're not running from QSH.
Does "node -v" (and other node commands) work?
What does "which npm" and "which node" give you? Both should give
you a /QOpenSys/pkgs/bin path
Also, you may need to run:
/QOpenSys/pkgs/bin/nodever 12
in order to explicitly use version 12 if you have older versions
also installed.
"OpenSource" <opensource-bounces@xxxxxxxxxxxxxxxxxx> wrote on 10/14/
2020 05:12:03 PM:
From: Steve M via OpenSource <opensource@xxxxxxxxxxxxxxxxxx>
To: "'IBMi Open Source Roundtable'" <opensource@xxxxxxxxxxxxxxxxxx>
Cc: Steve M <txpenguin1@xxxxxxxxxxx>
Date: 10/14/2020 05:12 PM
Subject: [EXTERNAL] [IBMiOSS] NPM Issue
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxxxxxxxx>
Strange new issue. O/S is 7.2 with current updates applied
quarterly. Just used ACS to upgrade Node to v12.18.4.
Every NPM command returns "Abort - core dumped". I mean every
single one, even something as simple as "npm -v".
Was happening before doing the upgrade and still continuing
Any thoughts?
Thanks,
Steve M.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.