And also:
ls -l /QOpenSys/usr/bin/node /QOpenSys/usr/bin/npm


"OpenSource" <opensource-bounces@xxxxxxxxxxxxxxxxxx> wrote on 10/15/2020
09:58:47 AM:

From: Steve M via OpenSource <opensource@xxxxxxxxxxxxxxxxxx>
To: "'Calvin Buckley'" <calvin@xxxxxxxxxx>, "'IBMi Open Source
Roundtable'" <opensource@xxxxxxxxxxxxxxxxxx>
Cc: Steve M <txpenguin1@xxxxxxxxxxx>, 'OpenSource' <opensource-
bounces@xxxxxxxxxxxxxxxxxx>
Date: 10/15/2020 10:17 AM
Subject: [EXTERNAL] Re: [IBMiOSS] NPM Issue
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxxxxxxxx>

Within QSH, here is what I get:

$
which node
/QOpenSys/usr/bin/node
$
which npm
/QOpenSys/usr/bin/npm
$

I did the same inside of PuTTy and received the same results.

Steve


-----Original Message-----
From: Calvin Buckley <calvin@xxxxxxxxxx>
Sent: Thursday, October 15, 2020 09:31
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxxxxxxxx>;
Steve M <txpenguin1@xxxxxxxxxxx>
Cc: 'OpenSource' <opensource-bounces@xxxxxxxxxxxxxxxxxx>
Subject: Re: [IBMiOSS] NPM Issue

I wonder if the OPS node is on the path - it was pretty crashy. I'd
do what Jesse suggests and give us the output of "which node".

On Thu, 2020-10-15 at 09:29 -0500, Jesse Gorzinski wrote:
Looks like you're running into QSH's default behavior of not allowing
multithreaded applications. You will need to set environment variable
QIBM_MULTI_THREADED to 'Y' before starting your QSH session.
It should work from SSH. Does SSH give you a dfferent error?

"Steve M" <
txpenguin1@xxxxxxxxxxx
wrote on 10/15/2020 08:22:09 AM:

From: "Steve M" <
txpenguin1@xxxxxxxxxxx

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

afterwards.
Any thoughts?

Thanks,

Steve M.



--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: INVALID URI REMOVED

u=https-3A__lists.midrange.com_mailman_listinfo_opensource&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=ZCVxF-

w6wAginVZ42dfeYbM5huvio_77jTCJXaiFgrE&m=kZl4Z4ESLE54_04O9zCoCUSX0VcoZeI1hVi3vITW-
qE&s=9GH5bMUAtDdZ66HitlXZgaZHhDczciE6zfNn8vW4XGU&e=
or email: OpenSource-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at INVALID URI REMOVED
u=https-3A__archive.midrange.com_opensource&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=ZCVxF-

w6wAginVZ42dfeYbM5huvio_77jTCJXaiFgrE&m=kZl4Z4ESLE54_04O9zCoCUSX0VcoZeI1hVi3vITW-
qE&s=TohxRqLaeOyh3STnpAiOIVE8c3twk09rRaZl5vSh7c8&e= .

Help support midrange.com by shopping at amazon.com with our affiliate
link: INVALID URI REMOVED
u=https-3A__amazon.midrange.com&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=ZCVxF-

w6wAginVZ42dfeYbM5huvio_77jTCJXaiFgrE&m=kZl4Z4ESLE54_04O9zCoCUSX0VcoZeI1hVi3vITW-
qE&s=P0E_kNQ6A7tAgKyCTqBUxNFE3uQfw2HbXp6l1cC_Jhw&e=




This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].