× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I have more information now on the issue, but I am no closer to a
resolution.



I set up the following environment variables:

QIBM_MULTI_THREADED = 'Y'

PASE_STDIO_ISATTY = 'N'



Then I ran these two commands:

QSH CMD('node -v')

Command ended normally with exit status 0.

QSH CMD('npm -v')

Command ended normally with exit status 133.



Here were the results:

v12.18.4

Press ENTER to end terminal session.

qsh: 001-0078 Process ended by signal 5.

Press ENTER to end terminal session.



When I run the same two "-v" checks inside of QP2TERM, they return the same
success/failure, respectively.



I researched the signal number shown above on this page:
https://www.ibm.com/support/pages/how-determine-meaning-qshell-exit-status-o
r-signal

When the exit status is greater than 128, the command ended by a signal. To
determine the signal number, you would take the exit status received and
subtract 128. For instance, a typical exit status received is 133. If 128 is
subtracted, a signal number of 5 is received. In order to determine the
meaning of the signal, you can refer to the sys/signal.h header file on the
IBM i server. To display the header file, you can execute the WRKMBRPDM
FILE(QSYSINC/SYS) MBR(SIGNAL) command and enter Option 5 to display the
file. Scrolling down through the file, you will find several #define
statements which define a token with a value. In this case, the value is the
numerical signal and the token is the symbolic signal name. A more
descriptive definition of the signal is included to the right between the /*
and */ comment indicators. If you refer back to the exit status of 133, it
was determined that the signal for this exit status is 5. Using the
sys/signal.h header file, it can be determined that signal 5 translates to a
SIGSEGV signal which equates to an invalid memory reference. This
information can then be used in searches to find a matching issue or
supplied to Development to assist in problem determination.



Okay, so now I know that when I try to do anything with NPM it is creating
an invalid memory reference error.



Anyone ever had this happen or seen this? It is becoming an obstacle to
doing things on our Dev LPAR.



Thanks,



Steve





From: Jesse Gorzinski <jgorzins@xxxxxxxxxx>
Sent: Thursday, October 15, 2020 10:22
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxxxxxxxx>
Cc: 'Calvin Buckley' <calvin@xxxxxxxxxx>; 'OpenSource'
<opensource-bounces@xxxxxxxxxxxxxxxxxx>; Steve M <txpenguin1@xxxxxxxxxxx>
Subject: RE: [IBMiOSS] NPM Issue



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


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

From: Steve M via OpenSource <opensource@xxxxxxxxxxxxxxxxxx
<mailto:opensource@xxxxxxxxxxxxxxxxxx> >
To: "'Calvin Buckley'" <calvin@xxxxxxxxxx <mailto:calvin@xxxxxxxxxx> >,
"'IBMi Open Source
Roundtable'" <opensource@xxxxxxxxxxxxxxxxxx
<mailto:opensource@xxxxxxxxxxxxxxxxxx> >
Cc: Steve M <txpenguin1@xxxxxxxxxxx <mailto:txpenguin1@xxxxxxxxxxx> >,
'OpenSource' <opensource-
bounces@xxxxxxxxxxxxxxxxxx <mailto:bounces@xxxxxxxxxxxxxxxxxx> >
Date: 10/15/2020 10:17 AM
Subject: [EXTERNAL] Re: [IBMiOSS] NPM Issue
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxxxxxxxx
<mailto: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 <mailto:calvin@xxxxxxxxxx> >
Sent: Thursday, October 15, 2020 09:31
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxxxxxxxx
<mailto:opensource@xxxxxxxxxxxxxxxxxx> >;
Steve M <txpenguin1@xxxxxxxxxxx <mailto:txpenguin1@xxxxxxxxxxx> >
Cc: 'OpenSource' <opensource-bounces@xxxxxxxxxxxxxxxxxx
<mailto: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 <mailto:txpenguin1@xxxxxxxxxxx>
wrote on 10/15/2020 08:22:09 AM:

From: "Steve M" <
txpenguin1@xxxxxxxxxxx <mailto:txpenguin1@xxxxxxxxxxx>

To: "'Jesse Gorzinski'" <
jgorzins@xxxxxxxxxx <mailto:jgorzins@xxxxxxxxxx>
, "'IBMi Open Source
Roundtable'" <
opensource@xxxxxxxxxxxxxxxxxx <mailto:opensource@xxxxxxxxxxxxxxxxxx>

Cc: "'OpenSource'" <
opensource-bounces@xxxxxxxxxxxxxxxxxx
<mailto: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 <mailto:jgorzins@xxxxxxxxxx>

Sent: Wednesday, October 14, 2020 19:48
To: IBMi Open Source Roundtable <
opensource@xxxxxxxxxxxxxxxxxx <mailto:opensource@xxxxxxxxxxxxxxxxxx>

Cc: OpenSource <
opensource-bounces@xxxxxxxxxxxxxxxxxx
<mailto:opensource-bounces@xxxxxxxxxxxxxxxxxx>
; Steve M
<
txpenguin1@xxxxxxxxxxx <mailto: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
<mailto:opensource-bounces@xxxxxxxxxxxxxxxxxx>
wrote on 10/14/
2020 05:12:03 PM:

From: Steve M via OpenSource <
opensource@xxxxxxxxxxxxxxxxxx <mailto:opensource@xxxxxxxxxxxxxxxxxx>


To: "'IBMi Open Source Roundtable'" <
opensource@xxxxxxxxxxxxxxxxxx <mailto:opensource@xxxxxxxxxxxxxxxxxx>


Cc: Steve M <
txpenguin1@xxxxxxxxxxx <mailto:txpenguin1@xxxxxxxxxxx>

Date: 10/14/2020 05:12 PM
Subject: [EXTERNAL] [IBMiOSS] NPM Issue
Sent by: "OpenSource" <
opensource-bounces@xxxxxxxxxxxxxxxxxx
<mailto: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
<mailto:OpenSource@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: <https://urldefense.proofpoint.com/v2/url?>
https://urldefense.proofpoint.com/v2/url?

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

w6wAginVZ42dfeYbM5huvio_77jTCJXaiFgrE&m=kZl4Z4ESLE54_04O9zCoCUSX0VcoZeI1hVi3
vITW-
qE&s=9GH5bMUAtDdZ66HitlXZgaZHhDczciE6zfNn8vW4XGU&e=
or email: OpenSource-request@xxxxxxxxxxxxxxxxxx
<mailto:OpenSource-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at <https://urldefense.proofpoint.com/v2/url?>
https://urldefense.proofpoint.com/v2/url?
u=https-3A__archive.midrange.com_opensource&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=ZCVxF-

w6wAginVZ42dfeYbM5huvio_77jTCJXaiFgrE&m=kZl4Z4ESLE54_04O9zCoCUSX0VcoZeI1hVi3
vITW-
qE&s=TohxRqLaeOyh3STnpAiOIVE8c3twk09rRaZl5vSh7c8&e= .

Help support midrange.com by shopping at amazon.com with our affiliate
link: <https://urldefense.proofpoint.com/v2/url?>
https://urldefense.proofpoint.com/v2/url?
u=https-3A__amazon.midrange.com&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=ZCVxF-

w6wAginVZ42dfeYbM5huvio_77jTCJXaiFgrE&m=kZl4Z4ESLE54_04O9zCoCUSX0VcoZeI1hVi3
vITW-
qE&s=P0E_kNQ6A7tAgKyCTqBUxNFE3uQfw2HbXp6l1cC_Jhw&e=



As an Amazon Associate we earn from qualifying purchases.

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-2023 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.