search

IBM / nodejs-idb-connector

A JavaScript (Node.js) library for communicating with Db2 for IBM i, with support for queries, procedures, and much more. Uses traditional callback-style syntax
MIT License
37 stars 23 forks source link

Profound JS idb-connector installation error #40

Closed abmusse closed 5 years ago

abmusse commented 5 years ago

Original report by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

We have install Node JS 8 on IBM i offline system and now we are trying to install profound js but facing the below mention error please help to resolve the issue. Thanks in advance.

[37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mTried to download(undefined): https://bitbucket.org/litmis/nodejs-idb-conn ector/downloads/db2ia-v1.0.13-node-v57-ibmi-ppc64.tar.gz [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mPre-built binaries not found for idb-connector@1.0.13 and node@8.11.4 (node-v57 ABI, unknown) (falling back to source compile with node-gyp) [0m

Thanks Iftikhar Ahmed

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

Hello @sheikhifti , I am not very familiar with web solutions using Node.js. Maybe you need the Express framework?

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu Meng,

I couldn't find any example of Node JS working as web service I want to develop a web service in node js which will take two inputs from url and response back in json format.

Thanks

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

You do not have to set any path. But you should call yum at the same folder of the rpm file (just like previous tar rpm install)

To uninstall it, call yum erase nodejs8-idb-connector (in any folder)

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

What path I have to set for installation.

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

@sheikhifti Any folder is OK. Then you can install it using yum install ***.rpm

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu Meng,

Which folder I have to copy these rpm files.

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

@sheikhifti That is a good news! I also have built two rpms of idb-connector for a better offline install experience. They are only for internal use.

https://bitbucket.org/litmis/nodejs-idb-connector/downloads/nodejs8-idb-connector-1.1.4-0.ibmi7.2.ppc64.rpm

https://bitbucket.org/litmis/nodejs-idb-connector/downloads/nodejs10-idb-connector-1.1.4-0.ibmi7.2.ppc64.rpm

I will close this issue now.

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu Meng,

Thanks a lot for your constant help and support it is working like a dream it is resolved both idb-connector and profoundjs problem once again thanks.

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

Hello @sheikhifti You may find the examples at the npm page of idb-connector -- https://www.npmjs.com/package/idb-connector

You can save the example code as a js file (for example, example1.js) and then run 

#!shell

node example1.js

If Node.js can not find idb-connector, you need to run this --

#!shell

export NODE_PATH=/QOpenSys/pkgs/lib/nodejs8/lib/node_modules
abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu,

I think it is working fine now please see attached screen shot.

Please refer me an example code to check and run the idb-connector. PUTY02.jpg

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

$ cd /QOpenSys/pkgs/lib/nodejs8/lib/node_modules $ rm -r /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/idb-connector $ /QOpenSys/pkgs/bin/tar -xf /home/iftikhar/idb-connector-node8.tar /QOpenSys/pkgs/bin/tar: /home/iftikhar/idb-connector-node8.tar\033[C\033[D: Cannot open: No such file or directory /QOpenSys/pkgs/bin/tar: Error is not recoverable: exiting now

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu,

On puty also same error.

require('idb-connector') SyntaxError: Error parsing /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/idb-connector/package.json: Unexpected token � in JSON t position 0

PUTY01.jpg

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

export NODE_PATH=/QOpenSys/pkgs/lib/nodejs8/lib/node_modules
$
node require('idb-connector')
qsh: 001-0050 Syntax error on line 2: token "(" not expected.
$
node require("idb-connector")
qsh: 001-0050 Syntax error on line 2: token "(" not expected.
$
require("idb-connector")
qsh: 001-0049 Syntax error on line 2: token word not expected, expecting token ")".
$
require('idb-connector')
qsh: 001-0049 Syntax error on line 2: token word not expected, expecting token ")".
$

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

I have to check below is it correct syntax.

node require('idb-connector')

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

It still has the same "Unexpected identifier Syntax Error"?

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

It is already in the correct folder.

/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/idb-connector

                         Work with Object Links

Directory . . . . : /QOpenSys/pkgs/lib/nodejs8/lib/node_modules

Type options, press Enter.
2=Edit 3=Copy 4=Remove 5=Display 7=Rename 8=Display attributes 11=Change current directory ...

Opt Object link Type Attribute Text
. DIR
.. DIR
idb-connector DIR
npm DIR

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

If I understand correctly, now you have the extracted idb-connector folder in /QOpenSys/pkgs/bin? Then you can move the idb-connector folder to the correct place --

#!shell

mv /QOpenSys/pkgs/bin/idb-connector /QOpenSys/pkgs/lib/nodejs8/lib/node_modules
abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu,

My yum is working fine I have installed tar in the below folder. Now I have to perform below steps again.

cd /QOpenSys/pkgs/lib/nodejs8/lib/node_modules rm -r /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/idb-connector /QOpenSys/pkgs/bin/tar -xf /home/yourname/idb-connector-node8.tar

tar folder stmf file created in below folder.
/QOpenSys/pkgs/bin/tar

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

If your yum work, you can simply call 

#!shell

yum install tar-gnu-1.29-1.ibmi7.1.ppc64.rpm

at the directory of the rpm file. Otherwise, you may need to reinstall the rpm environment to ensure yum work

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu,

Yes I have did offline Installation I have download the rpm file of tar please advise how to install rpm file of tar or directly put it in tar folder.

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

@sheikhifti Seems you do not have the correct tar (/QOpenSys/pkgs/bin/tar) installed.

It is weird because it should be a built-in part of the rpm environment. I do not know how you set up the rpm environment. Maybe you should refer to the "Offline Install Instruction" here.

Alternatively, you may install the specific rpm file of tar from here

By the way, it is not recommended to use Qshell in "green screen" because of the garbage output like "[1G [0J> [3G". You may have 5733SC1 installed and start a ssh environment by "*STRTCPSVR SSHD**" and then connect to your IBM i system using a ssh terminal (the system built-in one for Linux/MacOS, or putty for Windows).

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu,

Thanks a lot for your patients and support please see below and advise it is unzip successfully below folder is created.

/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/idb-connector

cd /QOpenSys/pkgs/lib/nodejs8/lib/node_modules
$
/QOpenSys/pkgs/bin/tar -xf /home/iftikhar/idb-connector-node8.tar
qsh: 001-0014 Command /QOpenSys/pkgs/bin/tar not found.
$
tar -xf /home/iftikhar/idb-connector-node8.tar
$
node
[1G [0J> [3G
node require('idb-connector')
node require('idb-connector')
node require('idb-connector')
^^^^^^^

SyntaxError: Unexpected identifier

[1G [0J> [3G [1G [0J> [3G

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

@sheikhifti Maybe you could try to use the fully qualified path tar to unzip it -->

#!shell
cd /QOpenSys/pkgs/lib/nodejs8/lib/node_modules
rm -r /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/idb-connector
/QOpenSys/pkgs/bin/tar -xf /home/yourname/idb-connector-node8.tar

As for the profoundjs issue, it is beyond the scope of my knowledge.

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Please also advice profound js install successfully subsystem running but instance is not started.

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu Meng,

Thanks a lot it is unzip successfully but when I trying to verify it is giving me below error may be syntax is wrong.

export NODE_PATH=/QOpenSys/pkgs/lib/nodejs8/lib/node_modules
$
node require('idb-connector')
qsh: 001-0050 Syntax error on line 2: token "(" not expected.
$
node
[1G [0J> [3G
require('idb-connector')
require('idb-connector')
SyntaxError: Error parsing /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/idb-connector/package.json: Unexpected token � in JSON t position 0

[1G [0J> [3G

node require 'idb-connector'
node require 'idb-connector'
node require 'idb-connector'
****Beginning of data**
{
"_from": "idb-connector",
"_id": "idb-connector@1.1.4",
"_inBundle": false,
"_integrity": "sha512-dRpScRhjR+HpUM87KxHTX/iKZ7e7doVeqsjIo6xrlOw1ll+MDu6VnQ19juJPfNuDh3BLIFcRIl4RpdtQTXQfRA==",
"_location": "/idb-connector",
"_phantomChildren": {},
"_requested": {
"type": "tag",
"registry": true,
"raw": "idb-connector",
"name": "idb-connector",
"escapedName": "idb-connector",
"rawSpec": "",
"saveSpec": null,
"fetchSpec": "latest"
},
"_requiredBy": [
"#USER"
],
"_resolved": "https://registry.npmjs.org/idb-connector/-/idb-connector-1.1.4.tgz",
"_shasum": "ff8a819921a55da5a85d770124de628cd144c4a8",
"_spec": "idb-connector",
"_where": "/QOpenSys/pkgs/lib",
"author": {
"name": "IBM"
},
"binary": {
"module_name": "db2ia",
"module_path": "./lib/binding/{configuration}/{node_abi}-ibmi-{arch}/",
"remote_path": ".",
"package_name": "{module_name}-v{version}-{node_abi}-ibmi-{arch}.tar.gz",
"host": "https://bitbucket.org/litmis/nodejs-idb-connector/downloads"
},
"bundleDependencies": [
"node-pre-gyp"
"node-pre-gyp"
],
"contributors": [
{
"name": "Xu Meng",
"email": "dmabupt@gmail.com"
},
{
"name": "Abdirahim Musse",
"email": "abdirahim.musse@ibm.com"
},
{
"name": "Aaron Bartell",
"email": "aaronbartell@gmail.com"
}
],
"dependencies": {
"node-addon-api": "^1.2.0",
"node-pre-gyp": "^0.11.0"
},
"deprecated": false,
"description": "A Node.js DB2 driver for IBM i",
"devDependencies": {
"bindings": "^1.3.0",
"chai": "^4.1.2",
"mocha": "^5.2.0"
},
"directories": {
"lib": "lib",
"test": "test"
},
"gypfile": true,
"homepage": "https://bitbucket.org/litmis/nodejs-idb-connector#readme",
"keywords": [
"DB2",
"IBMi",
"IB "iSeries"
],
"license": "MIT",
"main": "lib/db2a.js",
"name": "idb-connector",
"repository": {
"type": "git",
"url": "git+ssh://git@bitbucket.org/litmis/nodejs-idb-connector.git"
},
"scripts": {
"install": "node-pre-gyp install --fallback-to-build",
"test": "./node_modules/mocha/bin/mocha"
},
"version": "1.1.4"
}
****End of Data****

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

Hello @sheikhifti , I have uploaded the tar file of idb-connector for nodejs 8 here -> idb-connector-node8.tar

You can download it to your i system (for example, /home/yourname/idb-connector-node8.tar ) and change directory to /QOpenSys/pkgs/lib/nodejs8/lib/node_modules and unzip the file -->

#!shell

cd /QOpenSys/pkgs/lib/nodejs8/lib/node_modules
tar -xf /home/yourname/idb-connector-node8.tar

Then you can verify the installation by running ->

#!shell

export NODE_PATH=/QOpenSys/pkgs/lib/nodejs8/lib/node_modules
node
> require('idb-connector')
abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

How to avoid below also shown in log.

20 silly fetchPackageMetaData error for node-addon-api@^1.2.0 request to https://10.6.227.35:4873/node-addon-api failed, reason: socket hang up

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

I have tried with Local registry got the below error I don't know we will going to use it.

npm set registry https://10.6.227.35:4873
$
npm -g install idb-connector-1.1.4.tgz
[K [?25h [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mcode [0m ECONNRESETeanup [0m remove extracted modu [0m [Km [K[0m [K
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35merrno [0m ECONNRESET
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m request to https://10.6.227.35:4873/node-addon-api failed, reason: socket hang up
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m This is a problem related to network connectivity.
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m In most cases you are behind a proxy or have bad network settings. [0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m If you are behind a proxy, please make sure that the
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m 'proxy' config is set properly. See: 'npm help config'
[0m
[37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m A complete log of this run can be found in:
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m /HOME/TSTOWNER/.npm/_logs/2018-11-19T11_10_57_804Z-debug.log
[0m$
0 info it worked if it ends with ok
1 verbose cli [ '/QOpenSys/pkgs/lib/nodejs8/bin/node',
1 verbose cli '/QOpenSys/pkgs/bin/npm',
1 verbose cli '-g',
1 verbose cli 'install',
1 verbose cli 'idb-connector-1.1.4.tgz' ]
2 info using npm@6.4.1
3 info using node@v8.12.0
4 verbose npm-session e99cd6118b9060f3
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 silly pacote file manifest for undefined@file:idb-connector-1.1.4.tgz fetched in 370ms
8 timing stage:loadCurrentTree Completed in 842ms
9 silly install loadIdealTree
10 silly install cloneCurrentTreeToIdealTree
11 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
12 silly install loadShrinkwrap
13 timing stage:loadIdealTree:loadShrinkwrap Completed in 4ms
14 silly install loadAllDepsIntoIdealTree
15 silly resolveWithNewModule idb-connector@1.1.4 checking installable status
16 silly tarball trying file:/idb-connector/idb-connector-1.1.4.tgz by hash: sha512-CEnmTL6nSFG7pKtcVLeXVQ3Cl6s8VeZ/Czt0rm0hBL8YLEr7 17 silly extract file:/idb-connector/idb-connector-1.1.4.tgz extracted to /tmp/npm-4619-a95e2e58/unpack-09877dfb (1128ms)
18 silly addBundled read tarball
19 silly cleanup remove extracted module
20 silly fetchPackageMetaData error for node-addon-api@^1.2.0 request to https://10.6.227.35:4873/node-addon-api failed, reason: soc 21 timing stage:rollbackFailedOptional Completed in 1ms
22 timing stage:runTopLevelLifecycles Completed in 72994ms
23 verbose type system
24 verbose stack FetchError: request to https://10.6.227.35:4873/node-addon-api failed, reason: socket hang up
24 verbose stack at ClientRequest.req.on.err (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-fetch-npm/src/in 24 verbose stack at emitOne (events.js:116:13)
24 verbose stack at ClientRequest.emit (events.js:211:7)
24 verbose stack at TLSSocket.socketErrorListener (_http_client.js:387:9)
24 verbose stack at emitOne (events.js:116:13)
24 verbose stack at TLSSocket.emit (events.js:211:7)
24 verbose stack at emitErrorNT (internal/streams/destroy.js:66:8)
24 verbose stack at _combinedTickCallback (internal/process/next_tick.js:139:11)
24 verbose stack at process._tickCallback (internal/process/next_tick.js:181:9)
25 verbose cwd /idb-connector
26 verbose OS400 7.3
27 verbose argv "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/bin/npm" "-g" "install" "idb-connector-1.1.4.tgz"
28 verbose node v8.12.0
29 verbose npm v6.4.1
30 error code ECONNRESET
31 error errno ECONNRESET
32 error network request to https://10.6.227.35:4873/node-addon-api failed, reason: socket hang up
33 error network This is a problem related to network connectivity.
33 error network In most cases you are behind a proxy or have bad network settings.
33 error network
33 error network If you are behind a proxy, please make sure that the
33 error network 'proxy' config is set properly. See: 'npm help config'
34 verbose exit [ 1, true ]
****End of Data****

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu Meng,

I got the below error I have upload the tar file in idb-connector folder and run the following command as advice but still not install idb-connector please any one help I am struggling long time with profoundjs and idb-connector.

cd '/idb-connector'

npm set registry https://registry.npmjs.org
$
npm -g install idb-connector-1.1.4.tgz
[K [?25h [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mcode [0m ENOTFOUNDleanup [0m remove extracted modu [0m [Km [K[0m [K
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35merrno [0m ENOTFOUND
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m request to https://registry.npmjs.org/node-addon-api failed, reason : getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m This is a problem related to network connectivity.
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m In most cases you are behind a proxy or have bad network settings. [0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m If you are behind a proxy, please make sure that the
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mnetwork [0m 'proxy' config is set properly. See: 'npm help config'
[0m
[37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m A complete log of this run can be found in:
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m /HOME/TSTOWNER/.npm/_logs/2018-11-19T10_48_14_796Z-debug.log
[0m$

0 info it worked if it ends with ok
1 verbose cli [ '/QOpenSys/pkgs/lib/nodejs8/bin/node',
1 verbose cli '/QOpenSys/pkgs/bin/npm',
1 verbose cli '-g',
1 verbose cli 'install',
1 verbose cli 'idb-connector-1.1.4.tgz' ]
2 info using npm@6.4.1
3 info using node@v8.12.0
4 verbose npm-session a29093152d9563ad
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 silly pacote file manifest for undefined@file:idb-connector-1.1.4.tgz fetched in 423ms
8 timing stage:loadCurrentTree Completed in 892ms
9 silly install loadIdealTree
10 silly install cloneCurrentTreeToIdealTree
11 timing stage:loadIdealTree:cloneCurrentTree Completed in 1ms
12 silly install loadShrinkwrap
13 timing stage:loadIdealTree:loadShrinkwrap Completed in 3ms
14 silly install loadAllDepsIntoIdealTree
15 silly resolveWithNewModule idb-connector@1.1.4 checking installable status
16 silly tarball trying file:/idb-connector/idb-connector-1.1.4.tgz by hash: sha512-CEnmTL6nSFG7pKtcVLeXVQ3Cl6s8VeZ/Czt0rm0hBL8YLEr 17 silly extract file:/idb-connector/idb-connector-1.1.4.tgz extracted to /tmp/npm-4612-71971335/unpack-961d8199 (1415ms)
18 silly addBundled read tarball
19 silly cleanup remove extracted module
20 silly fetchPackageMetaData error for node-addon-api@^1.2.0 request to https://registry.npmjs.org/node-addon-api failed, reason: 21 timing stage:rollbackFailedOptional Completed in 2ms
22 timing stage:runTopLevelLifecycles Completed in 33760ms
23 verbose type system
24 verbose stack FetchError: request to https://registry.npmjs.org/node-addon-api failed, reason: getaddrinfo ENOTFOUND registry.np 24 verbose stack at ClientRequest.req.on.err (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-fetch-npm/src/i 24 verbose stack at emitOne (events.js:116:13)
24 verbose stack at ClientRequest.emit (events.js:211:7)
24 verbose stack at TLSSocket.socketErrorListener (_http_client.js:387:9)
24 verbose stack at emitOne (events.js:116:13)
24 verbose stack at TLSSocket.emit (events.js:211:7)
24 verbose stack at emitErrorNT (internal/streams/destroy.js:66:8)
24 verbose stack at _combinedTickCallback (internal/process/next_tick.js:139:11)
24 verbose stack at process._tickCallback (internal/process/next_tick.js:181:9)
25 verbose cwd /idb-connector
26 verbose OS400 7.3
27 verbose argv "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/bin/npm" "-g" "install" "idb-connector-1.1.4.tgz"
28 verbose node v8.12.0
29 verbose npm v6.4.1
30 error code ENOTFOUND
31 error errno ENOTFOUND
32 error network request to https://registry.npmjs.org/node-addon-api failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org regis 33 error network This is a problem related to network connectivity.
33 error network In most cases you are behind a proxy or have bad network settings.
33 error network
33 error network If you are behind a proxy, please make sure that the
33 error network 'proxy' config is set properly. See: 'npm help config'
34 verbose exit [ 1, true ]

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

@sheikhifti Any folder in which you run then command npm. As for registry, you may need to reset to the default one --> 

#!bash

npm set registry https://registry.npmjs.org
abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

In which folder I have to put idb-connector tar file and what registry I have to set in order to install successfully.

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

@sheikhifti I have uploaded the tar file idb-connector-1.1.4.tgz . You can download it to your IBM i system and install it locally-->

#!bash
npm -g install idb-connector-1.1.4.tgz
abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

I have update json file with latest version and tried but no luck the json file again updated with the old version I have also tried to install idb-connector stand alone in separate directory getting the below error please explain me the work around step by step I am new to npm and node js many thanks in advance.

npm set registry http://10.6.227.35:4873
$
npm install idb-connector@1.1.4
[K [?25h [27m [90m...... [0m] \ install:fs-minipass: [32minfo [0m [35mlifecycle [0m fs-minipass@1.2.5~in [0m [K [K
idb-connector@1.1.4 install /test-idb/node_modules/idb-connector
node-pre-gyp install --fallback-to-build

[37;40mnode-pre-gyp [0m [0m [30;43mWARN [0m [0m [35mUsing needle for node-pre-gyp https download [0m
[0m [37;40mnode-pre-gyp [0m [0m [30;43mWARN [0m [0m [35mPre-built binaries not installable for idb-connector@1.1.4 and node@8. 12.0 (node-v57 ABI, unknown) (falling back to source compile with node-gyp) [0m
[0m [37;40mnode-pre-gyp [0m [0m [30;43mWARN [0m [0m [35mHit error socket hang up [0m
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mconfigure error [0m
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m Error: Can't find Python executable "python", you can set the PYTHON env variable.
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at PythonFinder.failNoPython (/QOpenSys/pkgs/lib/nodejs8/lib/node _modules/npm/nodemodules/node-gyp/lib/configure.js:484:19)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at PythonFinder. (/QOpenSys/pkgs/lib/nodejs8/lib/node modules/npm/node_modules/node-gyp/lib/configure.js:406:16)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at F (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_module s/which/which.js:68:16)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at E (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_module s/which/which.js:80:29)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/w hich/which.js:89:16
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/i sexe/index.js:42:5
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/i sexe/mode.js:8:5
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at FSReqWrap.oncomplete (fs.js:152:21)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mSystem [0m OS400 7.3
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mcommand [0m "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/lib/nodejs8/l ib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/test-idb/node_modules/idb -connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node" "--module_name=db2ia" "--module_path=/test-idb/node_modules/idb-co nnector/lib/binding/Release/node-v57-ibmi-ppc64" "--napi_version=3" "--node_abi_napi=napi" "--napi_build_version=0" "--nodenapi label=node-v57"
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mcwd [0m /test-idb/node_modules/idb-connector
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnode -v [0m v8.12.0
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnode-gyp -v [0m v3.8.0
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnot ok [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mbuild error [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m Error: Failed to execute '/QOpenSys/pkgs/lib/nodejs8/bin/nod e /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/t est-idb/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node --module_name=db2ia --module_path=/test-idb /node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64 --napi_version=3 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v57' (1)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at ChildProcess. (/test-idb/node_modules/idb- connector/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at emitTwo (events.js:126:13)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at ChildProcess.emit (events.js:214:7)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at maybeClose (internal/child_process.js:915:16)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at Process.ChildProcess._handle.onexit (internal/child_p rocess.js:209:5)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mSystem [0m OS400 7.3
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mcommand [0m "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/test-idb/node_modu les/idb-connector/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mcwd [0m /test-idb/node_modules/idb-connector
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mnode -v [0m v8.12.0
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35m -v [0m v0.11.0
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mnot ok [0m
[0mFailed to execute '/QOpenSys/pkgs/lib/nodejs8/bin/node /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-gyp/ bin/node-gyp.js configure --fallback-to-build --module=/test-idb/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc 64/db2ia.node --module_name=db2ia --module_path=/test-idb/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64 --na pi_version=3 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v57' (1)
[K [?25h [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35menoent [0m ENOENT: no such file or directory, open '/test-idb/package.json '
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [35m [0m test-idb No description
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [35m [0m test-idb No repository field.
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [35m [0m test-idb No README data
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [35m [0m test-idb No license field.
[0m
[37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mcode [0m ELIFECYCLE
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35merrno [0m 1
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m idb-connector@1.1.4 install: node-pre-gyp install --fallback-to-build
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m Exit status 1
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m Failed at the idb-connector@1.1.4 install script.
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m This is probably not a problem with npm. There is likely additional logging out put above.
[0m
[37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m A complete log of this run can be found in:
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m /HOME/TSTOWNER/.npm/_logs/2018-10-25T11_28_32_267Z-debug.log
[0m$

abmusse commented 5 years ago

Original comment by Tim Waddle (Bitbucket: Tim_Waddle, GitHub: Unknown).

@Musse I am trying to do this locally. That explains my issues...Thanks

abmusse commented 5 years ago

@Tim_Waddle Thanks

I noticed that the download failed finding https://bitbucket.org/litmis/nodejs-idb-connector/downloads/db2ia-v1.1.4-node-v57-ibmi-x64.tar.gz

the script generates the path to the tarball based on your node version and architecture of your machine.

{module_name}-v{version}-{node_abi}-ibmi-{arch}.tar.gz

Looks like the arch that the install script found x64.

Were you trying to install the idb-connector on your local machine?

If so , FYI currently the idb-connector only supports IBM i installs.

All prebuilt binaries are built for ppc arch

prebuilts.png

abmusse commented 5 years ago

Original comment by Tim Waddle (Bitbucket: Tim_Waddle, GitHub: Unknown).

Running npm install idb-connector gives the same errors as OP. NPM gets most of the way through the install and the following warnings are thrown

node-pre-gyp WARN Using needle for node-pre-gyp https download

node-pre-gyp WARN Tried to download(404): https://bitbucket.org/litmis/nodejs-idb-connector/downloads/db2ia-v1.1.4-node-v57-ibmi-x64.tar.gz

node-pre-gyp WARN Pre-built binaries not found for idb-connector@1.1.4 and node@8.12.0 (node-v57 ABI, unknown) (falling back to source compile with node-gyp)

I'm guessing based on the downloads page for the project it is trying to get db2ia-v1.1.4-node-v57-ibmi-ppc64.tar.gz.

abmusse commented 5 years ago

@Tim_Waddle

Is your your IBM i also running offline like the OP?

Did you have trouble installing with npm install idb-connector ?

abmusse commented 5 years ago

Original comment by Tim Waddle (Bitbucket: Tim_Waddle, GitHub: Unknown).

I am having issues installing this package as well. @David Russo seems to be correct, the problem seems to be with the binaries not being found. I think the issue is actually in the package.json, where it tells npm how to find the binaries.

I cloned the project and was able to get the package installed when I changed the following line in the package.json "package_name": "{module_name}-v{version}-{node_abi}-ibmi-{arch}.tar.gz" changed to "package_name": "db2ia-v1.1.4-node-v64-ibmi-ppc64.tar.gz".

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

I have run the command rpm --rebuilddb which solved the problem to install the Node JS8-8.12.0 but now I am afraid to install the profound js if I am getting the same error of idb-connetcor lets try and let you know.

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu Meng,

I have refresh the yum and now trying to install Node JS getting the below error please advise.

yum install nodejs
Repository ibm is listed more than once in the configuration
Setting up Install Process
Package nodejs is obsoleted by nodejs8, trying to install nodejs8-8.12.0-1.ppc64 instead
Resolving Dependencies
--> Running transaction check
---> Package nodejs8.ppc64 0:8.12.0-1 will be installed
--> Processing Dependency: lib:/QOpenSys/pkgs/lib/libssl.so.1.0.0(shr_64.o)(ppc64) for package: nodejs8-8.12.0-1.ppc64
error: db4 error(-30986) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
--> Processing Dependency: lib:/QOpenSys/pkgs/lib/libcrypto.so.1.0.0(shr_64.o)(ppc64) for package: nodejs8-8.12.0-1.ppc64
--> Processing Dependency: lib:/QOpenSys/pkgs/lib/libstdc++.so.6(shr_64.o)(ppc64) for package: nodejs8-8.12.0-1.ppc64
--> Processing Dependency: nodever for package: nodejs8-8.12.0-1.ppc64
--> Processing Dependency: /bin/bash for package: nodejs8-8.12.0-1.ppc64
--> Running transaction check
---> Package bash.ppc64 0:4.4-0 will be installed

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

No I have only one repo file.

Browse : /QOpenSys/etc/yum/repos.d/ibm.repo

****Beginning of data**
[ibm]
name=ibm
baseurl=file:///QOpenSys/etc/yum/IBMRepoLocalMirror/repo

****End of Data****

yum install nodejs8-8.12.0-1.ibmi7.2.ppc64.rpm
Repository ibm is listed more than once in the configuration
ibm | 2.1 kB 00:00
ibm/primary | 117 kB 00:00
ibm 318/318
Setting up Install Process
No package nodejs8-8.12.0-1.ibmi7.2.ppc64.rpm available.
Error: Nothing to do
$

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

How can I download full repo directory to update it on IBM I

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

Seems your yum is broken. Please check if more than one repo file /QOpenSys/etc/yum/repos.d/*.repo starting with [ibm]

And make sure that you run the yum install command in the same directory that the file nodejs8-8.12.0-1.ibmi7.2.ppc64.rpm located (not the ppc64 folder).

abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

I have downloaded the above files and placed in repo directory folder ppc64. I am getting the below error.

yum install nodejs8-8.12.0-1.ibmi7.2.ppc64.rpm
Repository ibm is listed more than once in the configuration
Setting up Install Process
No package nodejs8-8.12.0-1.ibmi7.2.ppc64.rpm available.
Error: Nothing to do
$

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

You may also try node.js 10 --> nodejs10-10.11.0-0.ibmi7.2.ppc64.rpm

#!shell
yum install nodejs10-10.11.0-0.ibmi7.2.ppc64.rpm
nodever 10
abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

Would you try to download the new Node.js version --> nodejs8-8.12.0-1.ibmi7.2.ppc64.rpm and transfer the file to your IBM i system. And then run below command to upgrade your node.js from 8.11.4 to 8.12.0 -->

#!shell
yum install nodejs8-8.12.0-1.ibmi7.2.ppc64.rpm
abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Please see below thanks for your help

mkdir /idb-connector
$
cd /idb-connector
$
npm set registry http://10.6.227.35:4873
$
npm install idb-connector@1.1.4
[K [?25h [27m [90m...... [0m] / install:idb-connector: [7msill [0m [35mdoSerial [0m install 412 [0m [Kle' } [0m [K
idb-connector@1.1.4 install /idb-connector/node_modules/idb-connector
node-pre-gyp install --fallback-to-build

[37;40mnode-pre-gyp [0m [0m [30;43mWARN [0m [0m [35mUsing needle for node-pre-gyp https download [0m
[0m [37;40mnode-pre-gyp [0m [0m [30;43mWARN [0m [0m [35mPre-built binaries not installable for idb-connector@1.1.4 and node@8. 11.4 (node-v57 ABI, unknown) (falling back to source compile with node-gyp) [0m
[0m [37;40mnode-pre-gyp [0m [0m [30;43mWARN [0m [0m [35mHit error socket hang up [0m
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mconfigure error [0m
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m Error: Can't find Python executable "python", you can set the PYTHON env variable.
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at PythonFinder.failNoPython (/QOpenSys/pkgs/lib/nodejs8/lib/node _modules/npm/nodemodules/node-gyp/lib/configure.js:484:19)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at PythonFinder. (/QOpenSys/pkgs/lib/nodejs8/lib/node modules/npm/node_modules/node-gyp/lib/configure.js:406:16)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at F (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_module s/which/which.js:68:16)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at E (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_module s/which/which.js:80:29)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/w hich/which.js:89:16
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/i sexe/index.js:42:5
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/i sexe/mode.js:8:5
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at FSReqWrap.oncomplete (fs.js:152:21)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mSystem [0m OS400 7.3
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mcommand [0m "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/lib/nodejs8/l ib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/idb-connector/node_modul s/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node" "--module_name=db2ia" "--module_path=/idb-connector/node_mod les/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64" "--napi_version=3" "--node_abi_napi=napi" "--napi_build_version=0" "- node_napi_label=node-v57"
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mcwd [0m /idb-connector/node_modules/idb-connector
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnode -v [0m v8.11.4
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnode-gyp -v [0m v3.8.0
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnot ok [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mbuild error [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m Error: Failed to execute '/QOpenSys/pkgs/lib/nodejs8/bin/no e /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/ db-connector/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node --module_name=db2ia --module_path=/id -connector/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64 --napi_version=3 --node_abi_napi=napi --napi_build version=0 --node_napi_label=node-v57' (1)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at ChildProcess. (/idb-connector/node_module /idb-connector/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at emitTwo (events.js:126:13)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at ChildProcess.emit (events.js:214:7)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at maybeClose (internal/child_process.js:925:16)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at Process.ChildProcess._handle.onexit (internal/child_p rocess.js:209:5)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mSystem [0m OS400 7.3
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mcommand [0m "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/idb-connector/node _modules/idb-connector/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mcwd [0m /idb-connector/node_modules/idb-connector
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mnode -v [0m v8.11.4
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35m -v [0m v0.11.0
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mnot ok [0m
[0mFailed to execute '/QOpenSys/pkgs/lib/nodejs8/bin/node /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-gyp/ bin/node-gyp.js configure --fallback-to-build --module=/idb-connector/node_modules/idb-connector/lib/binding/Release/node-v57-ibm i-ppc64/db2ia.node --module_name=db2ia --module_path=/idb-connector/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi- ppc64 --napi_version=3 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v57' (1)
[K [?25h [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35menoent [0m ENOENT: no such file or directory, open '/idb-connector/package .json'
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [35m [0m idb-connector No description
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [35m [0m idb-connector No repository field.
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [35m [0m idb-connector No README data
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [35m [0m idb-connector No license field.
[0m
[37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mcode [0m ELIFECYCLE
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35merrno [0m 1
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m idb-connector@1.1.4 install: node-pre-gyp install --fallback-to-build
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m Exit status 1
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m Failed at the idb-connector@1.1.4 install script.
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m This is probably not a problem with npm. There is likely additional logging out put above.
[0m
[37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m A complete log of this run can be found in:
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m /HOME/TSTOWNER/.npm/_logs/2018-10-23T07_22_35_975Z-debug.log
[0m$

I am dealing Node JS first Time please stay with me until we resolved this issue.

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

@sheikhifti you may need to leave the profoundjs directory otherwise it will always download the old version idb-connector@1.0.3. For example

#!
mkdir /idb-connector
cd /idb-connector
npm set registry http://10.6.227.35:4873 
npm install idb-connector@1.1.4
abmusse commented 5 years ago

Original comment by Iftikhar Ahmed (Bitbucket: sheikhifti, GitHub: Unknown).

Dear Xu Meng, Please see below error I have tried the same as you instruct please stay with me to resolve this issue many thanks in advance.

npm install idb-connector@1.1.4
[K [?25h [27m [90m...... [0m] / install:idb-connector: [7msill [0m [35mdoSerial [0m install 1106 [0m [K [0m [Km [K idb-connector@1.0.13 install /profoundjs/node_modules/profoundjs/node_modules/idb-connector
node-pre-gyp install --fallback-to-build
[37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mTried to download(undefined): https://bitbucket.org/litmis/nodejs-idb-conn ector/downloads/db2ia-v1.0.13-node-v57-ibmi-ppc64.tar.gz [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mPre-built binaries not found for idb-connector@1.0.13 and node@8.11.4 (node-v57 ABI, unknown) (falling back to source compile with node-gyp) [0m
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mconfigure error [0m
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m Error: Can't find Python executable "python", you can set the PYTHON env variable.
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at PythonFinder.failNoPython (/QOpenSys/pkgs/lib/nodejs8/lib/node _modules/npm/nodemodules/node-gyp/lib/configure.js:484:19)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at PythonFinder. (/QOpenSys/pkgs/lib/nodejs8/lib/node modules/npm/node_modules/node-gyp/lib/configure.js:406:16)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at F (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_module s/which/which.js:68:16)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at E (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_module s/which/which.js:80:29)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/w hich/which.js:89:16
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/i sexe/index.js:42:5
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/i sexe/mode.js:8:5
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at FSReqWrap.oncomplete (fs.js:152:21)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mSystem [0m OS400 7.3
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mcommand [0m "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/lib/nodejs8/l ib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/profoundjs/node_modules/p rofoundjs/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node" "--module_name=db2ia" "--module_path=/pr ofoundjs/node_modules/profoundjs/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64"
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mcwd [0m /profoundjs/node_modules/profoundjs/node_modules/idb-connector
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnode -v [0m v8.11.4
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnode-gyp -v [0m v3.8.0
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnot ok [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mbuild error [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m Error: Failed to execute '/QOpenSys/pkgs/lib/nodejs8/bin/nod e /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/p rofoundjs/node_modules/profoundjs/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node --module_name=db2 ia --module_path=/profoundjs/node_modules/profoundjs/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64' (1)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at ChildProcess. (/profoundjs/node_modules/pr ofoundjs/node_modules/idb-connector/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at emitTwo (events.js:126:13)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at ChildProcess.emit (events.js:214:7)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at maybeClose (internal/child_process.js:925:16)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at Process.ChildProcess._handle.onexit (internal/child_p rocess.js:209:5)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mSystem [0m OS400 7.3
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mcommand [0m "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/profoundjs/node_mo dules/profoundjs/node_modules/idb-connector/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mcwd [0m /profoundjs/node_modules/profoundjs/node_modules/idb-connector [0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mnode -v [0m v8.11.4
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35m -v [0m v0.6.39
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mnot ok [0m
[0mFailed to execute '/QOpenSys/pkgs/lib/nodejs8/bin/node /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-gyp/ bin/node-gyp.js configure --fallback-to-build --module=/profoundjs/node_modules/profoundjs/node_modules/idb-connector/lib/binding /Release/node-v57-ibmi-ppc64/db2ia.node --module_name=db2ia --module_path=/profoundjs/node_modules/profoundjs/node_modules/idb-co nnector/lib/binding/Release/node-v57-ibmi-ppc64' (1)

idb-connector@1.1.4 install /profoundjs/node_modules/idb-connector
node-pre-gyp install --fallback-to-build

[37;40mnode-pre-gyp [0m [0m [30;43mWARN [0m [0m [35mUsing request for node-pre-gyp https download [0m
[0m [37;40mnode-pre-gyp [0m [0m [30;43mWARN [0m [0m [35mPre-built binaries not installable for idb-connector@1.1.4 and node@8. 11.4 (node-v57 ABI, unknown) (falling back to source compile with node-gyp) [0m
[0m [37;40mnode-pre-gyp [0m [0m [30;43mWARN [0m [0m [35mHit error getaddrinfo ENOTFOUND bitbucket.org bitbucket.org:443 [0m
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mconfigure error [0m
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m Error: Can't find Python executable "python", you can set the PYTHON env variable.
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at PythonFinder.failNoPython (/QOpenSys/pkgs/lib/nodejs8/lib/node _modules/npm/nodemodules/node-gyp/lib/configure.js:484:19)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at PythonFinder. (/QOpenSys/pkgs/lib/nodejs8/lib/node modules/npm/node_modules/node-gyp/lib/configure.js:406:16)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at F (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_module s/which/which.js:68:16)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at E (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_module s/which/which.js:80:29)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/w hich/which.js:89:16
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/i sexe/index.js:42:5
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/i sexe/mode.js:8:5
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at FSReqWrap.oncomplete (fs.js:152:21)
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mSystem [0m OS400 7.3
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mcommand [0m "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/lib/nodejs8/l ib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/profoundjs/node_modules/i db-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node" "--module_name=db2ia" "--module_path=/profoundjs/node_modules/id b-connector/lib/binding/Release/node-v57-ibmi-ppc64" "--napi_version=3" "--node_abi_napi=napi" "--napi_build_version=0" "--node_n api_label=node-v57"
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mcwd [0m /profoundjs/node_modules/idb-connector
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnode -v [0m v8.11.4
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnode-gyp -v [0m v3.8.0
[0m [37;40mgyp [0m [0m [31;40mERR! [0m [0m [35mnot ok [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mbuild error [0m
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m Error: Failed to execute '/QOpenSys/pkgs/lib/nodejs8/bin/nod e /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/p rofoundjs/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node --module_name=db2ia --module_path=/profou ndjs/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64 --napi_version=3 --node_abi_napi=napi --napi_build_versio n=0 --node_napi_label=node-v57' (1)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at ChildProcess. (/profoundjs/node_modules/id b-connector/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at emitTwo (events.js:126:13)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at ChildProcess.emit (events.js:214:7)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at maybeClose (internal/child_process.js:925:16)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mstack [0m at Process.ChildProcess._handle.onexit (internal/child_p rocess.js:209:5)
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mSystem [0m OS400 7.3
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mcommand [0m "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/profoundjs/node_mo dules/idb-connector/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mcwd [0m /profoundjs/node_modules/idb-connector
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mnode -v [0m v8.11.4
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35m -v [0m v0.11.0
[0m [37;40mnode-pre-gyp [0m [0m [31;40mERR! [0m [0m [35mnot ok [0m
[0mFailed to execute '/QOpenSys/pkgs/lib/nodejs8/bin/node /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-gyp/ bin/node-gyp.js configure --fallback-to-build --module=/profoundjs/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-p pc64/db2ia.node --module_name=db2ia --module_path=/profoundjs/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64 --napi_version=3 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v57' (1)
[K [?25h [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: profoundjs-node-pty@1.0.3 (node _modules/profoundjs-node-pty):
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35mnotsup [0m SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for profoundjs-no de-pty@1.0.3: wanted {"os":"!aix","arch":"!ppc64"} (current: {"os":"aix","arch":"ppc64"})
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: idb-connector@1.0.13 (node_modules/p rofoundjs/node_modules/idb-connector):
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: idb-connector@1.0.13 install: node- pre-gyp install --fallback-to-build
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: Exit status 1
[0m
[37;40mnpm [0m [0m [31;40mERR! [0m [0m [35mcode [0m ELIFECYCLE
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [0m [35merrno [0m 1
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m idb-connector@1.1.4 install: node-pre-gyp install --fallback-to-build
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m Exit status 1
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m Failed at the idb-connector@1.1.4 install script.
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m This is probably not a problem with npm. There is likely additional logging out put above.
[0m
[37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m A complete log of this run can be found in:
[0m [37;40mnpm [0m [0m [31;40mERR! [0m [35m [0m /HOME/TSTOWNER/.npm/_logs/2018-10-23T06_40_09_566Z-debug.log
[0m$

/home/TSTOWNER/.npm/_logs/2018-10-23T06_40_09_566Z-debug.log

3129 verbose lifecycle idb-connector@1.0.13~install: CWD: /profoundjs/node_modules/profoundjs/node_modules/idb-connector
3130 silly lifecycle idb-connector@1.0.13~install: Args: [ '-c', 'node-pre-gyp install --fallback-to-build' ]
3131 silly lifecycle idb-connector@1.0.13~install: Returned: code: 1 signal: null
3132 info lifecycle idb-connector@1.0.13~install: Failed to exec install script
3133 silly install node-pre-gyp@0.11.0
3134 info lifecycle node-pre-gyp@0.11.0~install: node-pre-gyp@0.11.0
3135 silly install node-addon-api@1.5.0
3136 info lifecycle node-addon-api@1.5.0~install: node-addon-api@1.5.0
3137 silly install idb-connector@1.1.4
3138 info lifecycle idb-connector@1.1.4~install: idb-connector@1.1.4
3139 verbose lifecycle idb-connector@1.1.4~install: unsafe-perm in lifecycle true
3140 verbose lifecycle idb-connector@1.1.4~install: PATH: /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/npm-lifecyc 3141 verbose lifecycle idb-connector@1.1.4~install: CWD: /profoundjs/node_modules/idb-connector
3142 silly lifecycle idb-connector@1.1.4~install: Args: [ '-c', 'node-pre-gyp install --fallback-to-build' ]
3143 silly lifecycle idb-connector@1.1.4~install: Returned: code: 1 signal: null
3144 info lifecycle idb-connector@1.1.4~install: Failed to exec install script
3145 timing action:install Completed in 84429ms
3146 verbose unlock done using /HOME/TSTOWNER/.npm/_locks/staging-7d6606f2f1193bbd.lock for /profoundjs/node_modules/.staging
3147 timing stage:rollbackFailedOptional Completed in 3831ms
3150 warn optional SKIPPING OPTIONAL DEPENDENCY: profoundjs-node-pty@1.0.3 (node_modules/profoundjs-node-pty):
3151 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for profoundjs-node-pty@1.0.3: wanted {"os":"!aix","arch":"!ppc6 3152 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: !aix
3152 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: !ppc64
3152 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: !ppc64
3152 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: aix
3152 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: ppc64
3153 warn optional SKIPPING OPTIONAL DEPENDENCY: idb-connector@1.0.13 (node_modules/profoundjs/node_modules/idb-connector):
3154 warn optional SKIPPING OPTIONAL DEPENDENCY: idb-connector@1.0.13 install: node-pre-gyp install --fallback-to-build
3154 warn optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
3155 verbose optional SKIPPING OPTIONAL DEPENDENCY:
3155 verbose optional Failed at the idb-connector@1.0.13 install script.
3155 verbose optional SKIPPING OPTIONAL DEPENDENCY: This is probably not a problem with npm. There is likely additional logging outp 3156 verbose stack Error: idb-connector@1.1.4 install: node-pre-gyp install --fallback-to-build
3156 verbose stack Exit status 1
3156 verbose stack at EventEmitter. (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/npm-lifecycle/index 3156 verbose stack at emitTwo (events.js:126:13)
3156 verbose stack at EventEmitter.emit (events.js:214:7)
3156 verbose stack at ChildProcess. (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/npm-lifecycle/lib/s 3156 verbose stack at emitTwo (events.js:126:13)
3156 verbose stack at ChildProcess.emit (events.js:214:7)
3156 verbose stack at maybeClose (internal/child_process.js:925:16)
3156 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
3156 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
3157 verbose pkgid idb-connector@1.1.4
3158 verbose cwd /profoundjs
3159 verbose OS400 7.3
3160 verbose argv "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/bin/npm" "install" "idb-connector@1.1.4"
3161 verbose node v8.11.4
3162 verbose npm v6.4.1
3163 error code ELIFECYCLE
3164 error errno 1
3165 error idb-connector@1.1.4 install: node-pre-gyp install --fallback-to-build
3165 error Exit status 1
3166 error Failed at the idb-connector@1.1.4 install script.
3166 error This is probably not a problem with npm. There is likely additional logging output above.
3167 verbose exit [ 1, true ]
****End of Data****

abmusse commented 5 years ago

Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).

@sheikhifti Seems profoundjs still tries to download the old idb-connector@1.0.13.

Would you try to install the latest idb-connector@1.1.4 directly? 

#!
npm set registry http://10.6.227.35:4873 
npm uninstall idb-connector 
npm install idb-connector@1.1.4