Giter VIP home page Giter VIP logo

Comments (72)

abmusse avatar abmusse commented on May 23, 2024

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?

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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)

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


What path I have to set for installation.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


Dear Xu Meng,

Which folder I have to copy these rpm files.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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 ")".
$

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


I have to check below is it correct syntax.

node require('idb-connector')

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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": "[email protected]",
"_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": "[email protected]"
},
{
"name": "Abdirahim Musse",
"email": "[email protected]"
},
{
"name": "Aaron Bartell",
"email": "[email protected]"
}
],
"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://[email protected]/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********

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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')

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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 [email protected]
3 info using [email protected]
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 [email protected] 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********

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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 [email protected]
3 info using [email protected]
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 [email protected] 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 ]

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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 [email protected]
[K [?25h [27m [90m...... [0m] \ install:fs-minipass: [32minfo [0m [35mlifecycle [0m [email protected]~in [0m [K [K
[email protected] 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 [email protected] 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/node_modules/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" "--node_napi_
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 [email protected] 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 [email protected] 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$

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

@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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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 [email protected] and [email protected] (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.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

@Tim_Waddle

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

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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
$

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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
$

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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 [email protected]
[K [?25h [27m [90m...... [0m] / install:idb-connector: [7msill [0m [35mdoSerial [0m install 412 [0m [Kle' } [0m [K
[email protected] 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 [email protected] 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/node_modules/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 [email protected] 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 [email protected] 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.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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 [email protected]. For example

#!
mkdir /idb-connector
cd /idb-connector
npm set registry http://10.6.227.35:4873 
npm install [email protected]

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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 [email protected]
[K [?25h [27m [90m...... [0m] / install:idb-connector: [7msill [0m [35mdoSerial [0m install 1106 [0m [K [0m [Km [K
[email protected] 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 [email protected] and [email protected]
(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/node_modules/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)

[email protected] 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 [email protected] 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/node_modules/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: [email protected] (node
_modules/profoundjs-node-pty):
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35mnotsup [0m SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for profoundjs-no
[email protected]: wanted {"os":"!aix","arch":"!ppc64"} (current: {"os":"aix","arch":"ppc64"})
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/p
rofoundjs/node_modules/idb-connector):
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: [email protected] 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 [email protected] 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 [email protected] 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 [email protected]install: CWD: /profoundjs/node_modules/profoundjs/node_modules/idb-connector
3130 silly lifecycle [email protected]
install: Args: [ '-c', 'node-pre-gyp install --fallback-to-build' ]
3131 silly lifecycle [email protected]install: Returned: code: 1 signal: null
3132 info lifecycle [email protected]
install: Failed to exec install script
3133 silly install [email protected]
3134 info lifecycle [email protected]install: [email protected]
3135 silly install [email protected]
3136 info lifecycle [email protected]
install: [email protected]
3137 silly install [email protected]
3138 info lifecycle [email protected]install: [email protected]
3139 verbose lifecycle [email protected]
install: unsafe-perm in lifecycle true
3140 verbose lifecycle [email protected]install: PATH: /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/npm-lifecyc
3141 verbose lifecycle [email protected]
install: CWD: /profoundjs/node_modules/idb-connector
3142 silly lifecycle [email protected]install: Args: [ '-c', 'node-pre-gyp install --fallback-to-build' ]
3143 silly lifecycle [email protected]
install: Returned: code: 1 signal: null
3144 info lifecycle [email protected]~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: [email protected] (node_modules/profoundjs-node-pty):
3151 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: 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: [email protected] (node_modules/profoundjs/node_modules/idb-connector):
3154 warn optional SKIPPING OPTIONAL DEPENDENCY: [email protected] 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 [email protected] 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: [email protected] 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 [email protected]
3158 verbose cwd /profoundjs
3159 verbose OS400 7.3
3160 verbose argv "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/bin/npm" "install" "[email protected]"
3161 verbose node v8.11.4
3162 verbose npm v6.4.1
3163 error code ELIFECYCLE
3164 error errno 1
3165 error [email protected] install: node-pre-gyp install --fallback-to-build
3165 error Exit status 1
3166 error Failed at the [email protected] 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********

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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 [email protected]

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


I am following the instruction to install the profound js on IBM i offline system from day one I am facing the below error please help me out to resolve it. I am wondering either it is idb-connector error or node-gyp error or network error.

Node.js v8.11.4 with npm v6.4.1 will now be used.
$

cd /
$
cd /profoundjs
$
npm set registry http://10.6.227.35:4873
$
npm install profoundjs
[K [?25h [27m [90m...... [0m] \ install:process-nextick-args: [32minfo [0m [35mlifecycle [0m process-nex [0m [K[KK
[email protected] install /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 [email protected] and [email protected]
(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/node_modules/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"
[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' (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.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/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'
(1)
> [email protected] install /profoundjs/node_modules/profoundjs-fibers

node build.js || nodejs build.js

aix-ppc64-57 exists; testing
Binary is fine; exiting

[email protected] install /profoundjs/node_modules/profoundjs
node setup/setup.js

package.json file exists.

modules directory exists.
Found Standard puiscreens.json file version >= 4.8.0, no need for update.
puiuplexit.js file exists.
Copying pjssamples.
store_credentials.js file exists.
call.js file exists.
start.js file exists.

[1G [0JSpecify Profound UI installation library (PROFOUNDUI): [56G

[1G [0JInstall Profound.js Connector IBM i ILE components (y)? [57G

[1G [0JEnter Profound.js Connector library name (PROFOUNDJS): [56G

[1G [0J
Create/replace server instance configuration for STRTCPSVR/ENDTCPSVR commands (y)? [84G

[1G [0JServer instance name (PROFOUNDJS): [36G

[1G [0JSpecify CCSID for instance PROFOUNDJS (37): [45G

[1G [0JSpecify Node.js path for instance PROFOUNDJS (/QOpenSys/pkgs/bin/node): [73G

[1G [0JAutostart server instance PROFOUNDJS when TCP/IP starts (y)? [62G

Command finished successfully.

Profound.js successfully installed.

[K [?25h [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: [email protected] (nod
_modules/profoundjs-node-pty):
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35mnotsup [0m SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for profoundjs-n
[email protected]: wanted {"os":"!aix","arch":"!ppc64"} (current: {"os":"aix","arch":"ppc64"})
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/
db-connector):
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: [email protected] 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

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


@sheikhifti I am not sure if sinopia support Node.js 10.
I have just upgraded idb-connector to v1.1.4 to resolve the node-pre-gyp issue.
Now you may try the instruction for Node.js 8 + IBM i + Profoundjs again.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


Dear Xu Meng,

I have installed Node JS 10 on IBM I and my PC after installing Node JS 10 on my PC I am installing Sinopia to install the profound JS offline by setting the local registry. But Sinopia is not installing Correctly it is giving below error.
C:\Windows\System32>npm install -g sinopia
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: The major version is no longer supported. Please update to 4.x or newer
npm WARN deprecated [email protected]: catastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible
C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\sinopia -> C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\sinopia\bin\sinopia

[email protected] install C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\sinopia\node_modules\bunyan\node_modules\dtrace-provider
node scripts/install.js

[email protected] install C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\sinopia\node_modules\crypt3
node-gyp rebuild

C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\sinopia\node_modules\crypt3>if not defined npm_config_node_gyp (node "C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets(34,5): error MSB
8036: The Windows SDK version 8.1 was not found. Install the required version of Windows SDK or change the SDK version
in the project property pages or by right-clicking the solution and selecting "Retarget solution". [C:\Users\iftikhar.a
hmed8\AppData\Roaming\npm\node_modules\sinopia\node_modules\crypt3\build\crypt3.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: C:\Program Files\MSBuild\14.0\bin\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:239:12)
gyp ERR! System Windows_NT 10.0.16299
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\sinopia\node_modules\crypt3
gyp ERR! node -v v10.9.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

[email protected] install C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\sinopia\node_modules\fs-ext
node-gyp configure build

C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\sinopia\node_modules\fs-ext>if not defined npm_config_node_gyp (node "C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" configure build ) else (node "C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" configure build )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets(34,5): error MSB
8036: The Windows SDK version 8.1 was not found. Install the required version of Windows SDK or change the SDK version
in the project property pages or by right-clicking the solution and selecting "Retarget solution". [C:\Users\iftikhar.a
hmed8\AppData\Roaming\npm\node_modules\sinopia\node_modules\fs-ext\build\fs-ext.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: C:\Program Files\MSBuild\14.0\bin\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:239:12)
gyp ERR! System Windows_NT 10.0.16299
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "configure" "build"
gyp ERR! cwd C:\Users\iftikhar.ahmed8\AppData\Roaming\npm\node_modules\sinopia\node_modules\fs-ext
gyp ERR! node -v v10.9.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\sinopia\node_modules\crypt3):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: node-gyp rebuild
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\sinopia\node_modules\fs-ext):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: node-gyp configure build
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

I have install node-gyp but still the same.
C:\Windows\System32>npm install node-gyp
npm WARN saveError ENOENT: no such file or directory, open 'C:\Windows\System32\package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open 'C:\Windows\System32\package.json'
npm WARN System32 No description
npm WARN System32 No repository field.
npm WARN System32 No README data
npm WARN System32 No license field.

  • [email protected]
    added 96 packages from 66 contributors and audited 182 packages in 41.228s
    found 0 vulnerabilities

Please help this issue is killing my time.
Thanks in advance.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


Duplicated with issue #43.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


Would you try to upgrade nodejs to a newer version and retry?

#!shell

yum clean all
yum update

Or try nodejs10?

#!shell

yum install nodejs10
nodever 10

And you may also want to check if idb-connector is already installed -->

#!shell

npm ls | grep idb-connector

If so, remove it first

#!shell

npm un idb-connector

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


Please help us if it available on the website then it will be network issue.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


/home/TSTOWNER/.npm/_logs/2018-10-18T04_30_31_748Z-debug.log

1162 info lifecycle [email protected]install: [email protected]
1163 verbose lifecycle [email protected]
install: unsafe-perm in lifecycle true
1164 verbose lifecycle [email protected]install: PATH: /QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/npm-lifecycle
1165 verbose lifecycle [email protected]
install: CWD: /node_modules/idb-connector
1166 silly lifecycle [email protected]install: Args: [ '-c', 'node-pre-gyp install --fallback-to-build' ]
1167 silly lifecycle [email protected]
install: Returned: code: 1 signal: null
1168 info lifecycle [email protected]~install: Failed to exec install script
1169 timing action:install Completed in 53494ms
1170 verbose unlock done using /HOME/TSTOWNER/.npm/_locks/staging-781faa38490e6896.lock for /node_modules/.staging
1171 timing stage:rollbackFailedOptional Completed in 1469ms
1172 timing stage:runTopLevelLifecycles Completed in 72681ms
1174 warn @1.0.0 No description
1175 warn @1.0.0 No repository field.
1176 verbose stack Error: [email protected] install: node-pre-gyp install --fallback-to-build
1176 verbose stack Exit status 1
1176 verbose stack at EventEmitter. (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/npm-lifecycle/index
1176 verbose stack at emitTwo (events.js:126:13)
1176 verbose stack at EventEmitter.emit (events.js:214:7)
1176 verbose stack at ChildProcess. (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/npm-lifecycle/lib/s
1176 verbose stack at emitTwo (events.js:126:13)
1176 verbose stack at ChildProcess.emit (events.js:214:7)
1176 verbose stack at maybeClose (internal/child_process.js:925:16)
1176 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
1177 verbose pkgid [email protected]
1178 verbose cwd /
1179 verbose OS400 7.3
1180 verbose argv "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/bin/npm" "install" "idb-connector"
1181 verbose node v8.11.4
1182 verbose npm v6.4.1
1183 error code ELIFECYCLE
1184 error errno 1
1185 error [email protected] install: node-pre-gyp install --fallback-to-build
1185 error Exit status 1
1186 error Failed at the [email protected] install script.
1186 error This is probably not a problem with npm. There is likely additional logging output above.
1187 verbose exit [ 1, true ]
End of Data********

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


C:\Windows\System32> sinopia
warn --- config file - C:\Users\iftikhar.ahmed8\AppData\Roaming\sinopia\config.yaml
warn --- http address - http://0.0.0.0:4873/
http --> 304, req: 'GET https://registry.npmjs.org/idb-connector', bytes: 0/0
http <-- 304, user: undefined, req: 'GET /idb-connector', bytes: 0/0
http --> 200, req: 'GET https://registry.npmjs.org/idb-connector/-/idb-connector-1.1.3.tgz' (streaming)
http <-- 200, user: undefined, req: 'GET /idb-connector/-/idb-connector-1.1.3.tgz', bytes: 0/643994
(node:32436) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated.
http --> 200, req: 'GET https://registry.npmjs.org/node-addon-api', bytes: 0/41773
http <-- 200, user: undefined, req: 'GET /node-addon-api', bytes: 0/6717
http <-- 400, user: undefined, req: 'POST /-/npm/v1/security/audits/quick', error: Unexpected token '\u001f' at 1:1
� �
^

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


Dear Musse,

Thanks for your help and advise we have follow the same steps as you advise but still no success. Please see the below error.

login as: tstowner
[email protected]'s password:
$ PATH=/QOpenSys/pkgs/bin:$PATH
$ PATH=/QOpenSys/pkgs/bin:$PATH
$ export PATH
$ yum install python2 gcc make-gnu
Repository ibm is listed more than once in the configuration
ibm | 2.2 kB 00:00
Setting up Install Process
Package python2-2.7.15-1.ppc64 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package gcc-aix.fat 0:6.3.0-19 will be installed
ibm/filelists | 415 kB 00:00
--> Processing Dependency: gcc-cpp-aix = 6.3.0 for package: gcc-aix-6.3.0-19.fat
--> Processing Dependency: /QOpenSys/pkgs/lib/libatomic.so.1 for package: gcc-aix-6.3.0-19.fat
---> Package make-gnu.ppc64 0:4.2-0 will be installed
--> Running transaction check
---> Package gcc-cpp-aix.fat 0:6.3.0-19 will be installed
--> Processing Dependency: lib:/QOpenSys/pkgs/lib/libmpfr.a(libmpfr.so.4)(ppc) for package: gcc-cpp-aix-6.3.0-19.fat
--> Processing Dependency: lib:/QOpenSys/pkgs/lib/libgmp.a(libgmp.so.10)(ppc) for package: gcc-cpp-aix-6.3.0-19.fat
--> Processing Dependency: lib:/QOpenSys/pkgs/lib/libmpc.a(libmpc.so.3)(ppc) for package: gcc-cpp-aix-6.3.0-19.fat
---> Package libatomic1.ppc64 0:6.3.0-19 will be installed
--> Running transaction check
---> Package gmp-aix.fat 0:5.1.3-12 will be installed
--> Processing Dependency: lib:/QOpenSys/pkgs/lib/libstdc++.a(libstdc++.so.6)(ppc64) for package: gmp-aix-5.1.3-12.fat
--> Processing Dependency: lib:/QOpenSys/pkgs/lib/libstdc++.a(libstdc++.so.6)(ppc) for package: gmp-aix-5.1.3-12.fat
---> Package libmpc.fat 0:1.0.3-12 will be installed
---> Package mpfr-aix.fat 0:3.1.2-11 will be installed
--> Running transaction check
---> Package libstdcplusplus-aix.fat 0:6.3.0-19 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
Package Arch Version Repository Size

Installing:
gcc-aix fat 6.3.0-19 ibm 25 M
make-gnu ppc64 4.2-0 ibm 467 k
Installing for dependencies:
gcc-cpp-aix fat 6.3.0-19 ibm 8.2 M
gmp-aix fat 5.1.3-12 ibm 594 k
libatomic1 ppc64 6.3.0-19 ibm 58 k
libmpc fat 1.0.3-12 ibm 166 k
libstdcplusplus-aix fat 6.3.0-19 ibm 6.6 M
mpfr-aix fat 3.1.2-11 ibm 445 k

Transaction Summary

Install 8 Packages

Total download size: 42 M
Installed size: 149 M
Is this ok [y/N]: y
Downloading Packages:

Total 16 MB/s | 42 MB 00:02
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : libstdcplusplus-aix-6.3.0-19.fat 1/8
Installing : gmp-aix-5.1.3-12.fat 2/8
Installing : mpfr-aix-3.1.2-11.fat 3/8
Installing : libmpc-1.0.3-12.fat 4/8
Installing : gcc-cpp-aix-6.3.0-19.fat 5/8
Installing : libatomic1-6.3.0-19.ppc64 6/8
Installing : gcc-aix-6.3.0-19.fat 7/8
Installing : make-gnu-4.2-0.ppc64 8/8

Installed:
gcc-aix.fat 0:6.3.0-19 make-gnu.ppc64 0:4.2-0

Dependency Installed:
gcc-cpp-aix.fat 0:6.3.0-19 gmp-aix.fat 0:5.1.3-12
libatomic1.ppc64 0:6.3.0-19 libmpc.fat 0:1.0.3-12
libstdcplusplus-aix.fat 0:6.3.0-19 mpfr-aix.fat 0:3.1.2-11

Complete!
$ cd /
$ mkdir test-idb
$ npm init -y
Wrote to /package.json:

{
"name": "",
"version": "1.0.0",
"description": "",
"main": "jquery-1.8.2.js",
"directories": {
"lib": "lib"
},
"scripts": {
"test": "echo "Error: no test specified" && exit 1"
},
"keywords": [],
"author": "",
"license": "ISC"
}

$ npm install idb-connector

[email protected] install /node_modules/idb-connector
node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using needle for node-pre-gyp https download
node-pre-gyp WARN Pre-built binaries not installable for [email protected] and [email protected] (node-v57 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error socket hang up
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: This is most likely not a problem with node-gyp or the package itself and
gyp ERR! stack is related to network connectivity. In most cases you are behind a proxy or have bad
gyp ERR! stack network settings.
gyp ERR! stack at Request. (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:197:21)
gyp ERR! stack at emitOne (events.js:116:13)
gyp ERR! stack at Request.emit (events.js:211:7)
gyp ERR! stack at Request.onRequestError (/QOpenSys/pkgs/lib/nodejs8/lib/node_modules/npm/node_modules/request/request.js:881:8)
gyp ERR! stack at emitOne (events.js:116:13)
gyp ERR! stack at ClientRequest.emit (events.js:211:7)
gyp ERR! stack at TLSSocket.socketErrorListener (_http_client.js:387:9)
gyp ERR! stack at emitOne (events.js:116:13)
gyp ERR! stack at TLSSocket.emit (events.js:211:7)
gyp ERR! stack at emitErrorNT (internal/streams/destroy.js:64:8)
gyp ERR! System OS400 7.3
gyp ERR! command "/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=/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node" "--module_name=db2ia" "--module_path=/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64" "--napi_version=3" "--node_abi_napi=napi"
gyp ERR! cwd /node_modules/idb-connector
gyp ERR! node -v v8.11.4
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed 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=/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node --module_name=db2ia --module_path=/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64 --napi_version=3 --node_abi_napi=napi' (1)
node-pre-gyp ERR! stack at ChildProcess. (/node_modules/idb-connector/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:126:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:214:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:925:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
node-pre-gyp ERR! System OS400 7.3
node-pre-gyp ERR! command "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/node_modules/idb-connector/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /node_modules/idb-connector
node-pre-gyp ERR! node -v v8.11.4
node-pre-gyp ERR! -v v0.10.3
node-pre-gyp ERR! not ok
Failed 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=/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64/db2ia.node --module_name=db2ia --module_path=/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64 --napi_version=3 --node_abi_napi=napi' (1)
npm WARN @1.0.0 No description
npm WARN @1.0.0 No repository field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! /HOME/TSTOWNER/.npm/_logs/2018-10-18T04_30_31_748Z-debug.log
$

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

Original comment by David Russo (Bitbucket: DavidRusso, GitHub: DavidRusso).


I'm a developer at Profound Logic, we provide the 'profoundjs' package that the reporter is trying to install. We have 2 other users that have had the same problem installing 'idb-connector'. It seems to me that the real problem is that the installation process is not finding/downloading the pre-built binary -- users shouldn't have to build from source code.

From the log messages above:

#!

node-pre-gyp ERR! Tried to download(undefined): https://bitbucket.org/litmis/nodejs-idb-connector/downloads/db2ia-v1.0.13-node-v57-ibmi-ppc64.tar.gz node-pre-gyp ERR! Pre-built binaries not found for [email protected] and node @8.11.4 (node-v57 ABI, unknown) (falling back to source compile with node-gyp) 

Why does the download fail? The binary is present on the website...

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

Ok, From reading the logs above, it seems that error stems from failing to build idb-connector from source.

To do so you would need to have some additional packages installed.

Get packages

The packages you will need are: python2, gcc, make-gnu

These are available in RPM form

if you have access to the rpm repos you can run

yum install python2 gcc make-gnu

Otherwise you would need to get the RPMs usings offline methods link

After installation create a symbolic link for python:

ln -s /QOpenSys/pkgs/bin/python2 /QOpenSys/pkgs/bin/python

Ensure that /QOpenSys/pkgs/bin is on your PATH link

Get idb-connector

Now create a folder to install the idb-connector

For example:

mkdir ~/test-idb

cd ~/test-idb

generate a package.json

npm init -y

Install

npm install idb-connector

profoundjs should also be able to install idb-connector.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


IFS Z-debug.log
Browse : /home/TSTOWNER/.npm/_logs/2018-10-17T09_44_49_861Z-debug.log
Record : 1 of 22 by 18 Column : 1 534 by 131
Control :

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2....+....3.
Beginning of data**
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 'install',
1 verbose cli 'profoundjs\u001b[D\u001b[D\u001b[D\u001b[D\u001b[D\u001b[D\u001b[D\u001b[D\u001b[D\u001b[D\u001b[D\u001b[D\u001b[D
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session 8b20f03d3830aa97
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData error for file:profoundjs [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [DPATH=QopenSy
8 timing stage:rollbackFailedOptional Completed in 3ms
9 timing stage:runTopLevelLifecycles Completed in 4051ms
10 verbose stack Error: ENOENT: no such file or directory, open '/profoundjs/profoundjs [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D
11 verbose cwd /profoundjs
12 verbose OS400 7.3
13 verbose argv "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/bin/npm" "install" "profoundjs\u001b[D\u001b[D\u001b[D\u001b[D
14 verbose node v8.11.4
14 verbose node v8.11.4
15 verbose npm v6.4.1
16 error code ENOLOCAL
17 error Could not install from "profoundjs [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D [D
[DPATH=QopenSys/pkgs/bin=/QOpenSys/pkgs/bin:/QOpenSys/pkgs/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin" as it does not conntain a package.json file.

18 verbose exit [ 1, true ]

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


I have install PuTTY to try it on SSH terminal but no luck please advise what is wrong here.

$ PATH=/QOpenSys/pkgs/bin:$PATH
$ export PATH
$ npm set registry http://10.6.227.35:4873
$ npm install profoundjs

[email protected] install /profoundjs/node_modules/idb-connector
node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(undefined): https://bitbucket.org/litmis/nod ejs-idb-connector/downloads/db2ia-v1.0.13-node-v57-ibmi-ppc64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and node @8.11.4 (node-v57 ABI, unknown) (falling back to source compile with node-gyp)
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: This is most likely not a problem with node-gyp or the pac kage itself and
gyp ERR! stack is related to network connectivity. In most cases you are behind a proxy or have bad
gyp ERR! stack network settings.
gyp ERR! stack at Request. (/QOpenSys/pkgs/lib/nodejs8/lib/node_m odules/npm/node_modules/node-gyp/lib/install.js:197:21)
gyp ERR! stack at emitOne (events.js:116:13)
gyp ERR! stack at Request.emit (events.js:211:7)
gyp ERR! stack at Request.onRequestError (/QOpenSys/pkgs/lib/nodejs8/lib/nod e_modules/npm/node_modules/request/request.js:881:8)
gyp ERR! stack at emitOne (events.js:116:13)
gyp ERR! stack at ClientRequest.emit (events.js:211:7)
gyp ERR! stack at TLSSocket.socketErrorListener (_http_client.js:387:9)
gyp ERR! stack at emitOne (events.js:116:13)
gyp ERR! stack at TLSSocket.emit (events.js:211:7)
gyp ERR! stack at emitErrorNT (internal/streams/destroy.js:64:8)
gyp ERR! System OS400 7.3
gyp ERR! command "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/QOpenSys/pkgs/lib/nodej s8/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fa llback-to-build" "--module=/profoundjs/node_modules/idb-connector/lib/binding/Re lease/node-v57-ibmi-ppc64/db2ia.node" "--module_name=db2ia" "--module_path=/prof oundjs/node_modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64"
gyp ERR! cwd /profoundjs/node_modules/idb-connector
gyp ERR! node -v v8.11.4
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed 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-ppc64/db2ia.node --module_name=db2ia --module_path=/profoundjs/node_modules/idb-connector/lib/binding/Release/node-v 57-ibmi-ppc64' (1)
node-pre-gyp ERR! stack at ChildProcess. (/profoundjs/node_module s/idb-connector/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:126:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:214:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:925:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/chi ld_process.js:209:5)
node-pre-gyp ERR! System OS400 7.3
node-pre-gyp ERR! command "/QOpenSys/pkgs/lib/nodejs8/bin/node" "/profoundjs/nod e_modules/idb-connector/node_modules/.bin/node-pre-gyp" "install" "--fallback-to -build"
node-pre-gyp ERR! cwd /profoundjs/node_modules/idb-connector
node-pre-gyp ERR! node -v v8.11.4
node-pre-gyp ERR! -v v0.6.39
node-pre-gyp ERR! not ok
Failed to execute '/QOpenSys/pkgs/lib/nodejs8/bin/node /QOpenSys/pkgs/lib/nodejs 8/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallbac k-to-build --module=/profoundjs/node_modules/idb-connector/lib/binding/Release/n ode-v57-ibmi-ppc64/db2ia.node --module_name=db2ia --module_path=/profoundjs/node _modules/idb-connector/lib/binding/Release/node-v57-ibmi-ppc64' (1)

[email protected] install /profoundjs/node_modules/profoundjs-fibers
node build.js || nodejs build.js

aix-ppc64-57 exists; testing
Binary is fine; exiting

[email protected] install /profoundjs/node_modules/profoundjs
node setup/setup.js

package.json file exists.
modules directory exists.
Found Standard puiscreens.json file version >= 4.8.0, no need for update.
puiuplexit.js file exists.
Copying pjssamples.
store_credentials.js file exists.
call.js file exists.
start.js file exists.

Specify Profound UI installation library (PROFOUNDUI):
Install Profound.js Connector IBM i ILE components (y)?
Enter Profound.js Connector library name (PROFOUNDJS):

Create/replace server instance configuration for STRTCPSVR/ENDTCPSVR commands (y )?
Server instance name (PROFOUNDJS):
Specify CCSID for instance PROFOUNDJS (37):
Specify Node.js path for instance PROFOUNDJS (/QOpenSys/pkgs/bin/node):
Autostart server instance PROFOUNDJS when TCP/IP starts (y)?

Executing command: CPYFRMSTMF FROMSTMF('/profoundjs/node_modules/profoundjs/setu p/pjsdist.savf') TOMBR('/QSYS.LIB/QGPL.LIB/PJSDIST.FILE') MBROPT(*REPLACE)
CPCA081: Stream file copied to object.
Command finished successfully.

Executing command: RSTOBJ OBJ(PJSINSTALL) SAVLIB(PJSDIST) DEV(*SAVF) OBJTYPE(*AL L) SAVF(QGPL/PJSDIST) RSTLIB(QGPL)
CPC3703: 4 objects restored from PJSDIST to QGPL.
Command finished successfully.

Executing command: QGPL/PJSINSTALL CONNLIB(PROFOUNDJS) CONNHOST('localhost') CON NPORT(8081) SVRNAME(PROFOUNDJS) SVRDIR('/profoundjs') SVRAUTO(*YES) CCSID(37) NO DEPATH('/QOpenSys/pkgs/bin/node')
PJI0001: Profound.js installation complete.
Command finished successfully.

Cleaning up...

Executing command: DLTPGM PGM(QGPL/PJSINSTALL)
CPC2191: Object PJSINSTALL in QGPL type *PGM deleted.
Command finished successfully.

Executing command: DLTCMD CMD(QGPL/PJSINSTALL)
CPC2191: Object PJSINSTALL in QGPL type *CMD deleted.
Command finished successfully.

Executing command: DLTPNLGRP PNLGRP(QGPL/PJSINSTALL)
CPC2191: Object PJSINSTALL in QGPL type *PNLGRP deleted.
Command finished successfully.

Executing command: DLTMSGF MSGF(QGPL/PJSINSTALL)
CPC2191: Object PJSINSTALL in QGPL type *MSGF deleted.
Command finished successfully.

Executing command: DLTF FILE(QGPL/PJSDIST)
CPC2191: Object PJSDIST in QGPL type *FILE deleted.
Command finished successfully.

Profound.js successfully installed.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_ modules/profoundjs-node-pty):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for profoundj [email protected]: wanted {"os":"!aix","arch":"!ppc64"} (current: {"os":"aix","ar ch":"ppc64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modul es/idb-connector):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: n ode-pre-gyp install --fallback-to-build
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


We are using SSH terminal by giving STRQSH command.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

Original comment by Jesse G (Bitbucket: ThePrez, GitHub: ThePrez).


Can you please try in an SSH terminal? Also, try setting your PATH as documented here: https://bitbucket.org/ibmi/opensource/src/master/docs/troubleshooting/SETTING_PATH.md

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


Please some one help to resolve the issue we are stuck here.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


Please find below full log of the error

npm set registry http://10.6.227.35:4873
$
npm install profoundjs
[K [?25h [27m [90m...... [0m] \ install:htmlencode: [32minfo [0m [35mlifecycle [0m [email protected]~inst [0m [K [K
[email protected] install /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 [email protected] and [email protected]
(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/node_modules/node-gyp/lib/configure.js:483: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:397: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/w
hich/node_modules/isexe/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/w
hich/node_modules/isexe/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"
[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.6.2
[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' (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.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/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'
(1)

[email protected] install /profoundjs/node_modules/profoundjs-fibers
node build.js || nodejs build.js

aix-ppc64-57 exists; testing
Binary is fine; exiting

[email protected] install /profoundjs/node_modules/profoundjs
node setup/setup.js
package.json file exists.
modules directory exists.
Found Standard puiscreens.json file version >= 4.8.0, no need for update.
puiuplexit.js file exists.
Copying pjssamples.
store_credentials.js file exists.
call.js file exists.
start.js file exists.

[1G [0JSpecify Profound UI installation library (PROFOUNDUI): [56G

[1G [0JInstall Profound.js Connector IBM i ILE components (y)? [57G

[1G [0JEnter Profound.js Connector library name (PROFOUNDJS): [56G

[1G [0J
Create/replace server instance configuration for STRTCPSVR/ENDTCPSVR commands (y)? [84G

[1G [0JServer instance name (PROFOUNDJS): [36G

[1G [0JSpecify CCSID for instance PROFOUNDJS (37): [45G

[1G [0JSpecify Node.js path for instance PROFOUNDJS (/QOpenSys/pkgs/bin/node): [73G

[1G [0JAutostart server instance PROFOUNDJS when TCP/IP starts (y)? [62G

Executing command: CPYFRMSTMF FROMSTMF('/profoundjs/node_modules/profoundjs/setup/pjsdist.savf') TOMBR('/QSYS.LIB/QGPL.LIB/PJSDIS
T.FILE') MBROPT(*REPLACE)
CPCA081: Stream file copied to object.
Command finished successfully.

Executing command: RSTOBJ OBJ(PJSINSTALL) SAVLIB(PJSDIST) DEV(*SAVF) OBJTYPE(*ALL) SAVF(QGPL/PJSDIST) RSTLIB(QGPL)
CPC3703: 4 objects restored from PJSDIST to QGPL.
Command finished successfully.

Executing command: QGPL/PJSINSTALL CONNLIB(PROFOUNDJS) CONNHOST('localhost') CONNPORT(8081) SVRNAME(PROFOUNDJS) SVRDIR('/profound
js') SVRAUTO(*YES) CCSID(37) NODEPATH('/QOpenSys/pkgs/bin/node')
PJI0001: Profound.js installation complete.
Command finished successfully.

Cleaning up...
Profound.js successfully installed.

[K [?25h [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: [email protected] (node
_modules/profoundjs-node-pty):
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35mnotsup [0m SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for profoundjs-no
[email protected]: wanted {"os":"!aix","arch":"!ppc64"} (current: {"os":"aix","arch":"ppc64"})
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/i
db-connector):
[0m [37;40mnpm [0m [0m [30;43mWARN [0m [0m [35moptional [0m SKIPPING OPTIONAL DEPENDENCY: [email protected] 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

but it is not working profound JS instance not getting active.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


We are getting this error while installing profound JS "npm install profoundjs" profound js install successfully but idb-connector given the error.

[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 [email protected] and [email protected] (node-v57 ABI, unknown) (falling back to source compile with node-gyp) [0m

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

Ok Thanks,

Which Step of the instructions are you experiencing the error?

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


How we connect IBM i to internet for installing Profound JS or only we need to open repository URL or few more ULR like bitbucket etc.

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

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


We are installing profound js on IBM i offline system by using sinopia as profound logic instructed on the below link

http://www.profoundlogic.com/docs/display/PUI/Installing+Profound.js+onto+an+offline+system

from nodejs-idb-connector.

abmusse avatar abmusse commented on May 23, 2024

@sheikhifti

Says you are running your IBM i offline but to download npm packages you will need to be connected to the internet.

  1. Ensure you are connected to the internet.

I was able to install profoundjs on the IBM i node version 8.11.3

$ npm i profoundjs

> [email protected] install 
> node-pre-gyp install --fallback-to-build

[idb-connector] Success:  is installed via remote

from nodejs-idb-connector.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.