Jeffrey Osborne
Forum Replies Created
Viewing 11 posts - 1 through 11 (of 11 total)
-
One last thing I just realized. In my npm-debug file, I have the following:
0 info it worked if it ends with ok 1 verbose cli [ 'node', '/usr/bin/npm', 'install', 'node-red-node-mysql' ] 2 info using npm@1.4.28 3 info using node@v0.10.40 4 verbose cache add [ 'node-red-node-mysql', null ] 5 verbose cache add name=undefined spec="node-red-node-mysql" args=["node-red-node-mysql",null] 6 verbose parsed url { protocol: null, 6 verbose parsed url slashes: null, 6 verbose parsed url auth: null, 6 verbose parsed url host: null, 6 verbose parsed url port: null, 6 verbose parsed url hostname: null, 6 verbose parsed url hash: null, 6 verbose parsed url search: null, 6 verbose parsed url query: null, 6 verbose parsed url pathname: 'node-red-node-mysql', 6 verbose parsed url path: 'node-red-node-mysql', 6 verbose parsed url href: 'node-red-node-mysql' } 7 silly makeCacheDir cache dir uid, gid [ 0, 0 ] 8 silly lockFile dbd87e05-node-red-node-mysql node-red-node-mysql 9 verbose lock node-red-node-mysql /home/root/.npm/dbd87e05-node-red-node-mysql.lock 10 silly lockFile dbd87e05-node-red-node-mysql node-red-node-mysql 11 silly lockFile dbd87e05-node-red-node-mysql node-red-node-mysql 12 verbose addNamed [ 'node-red-node-mysql', '' ] 13 verbose addNamed [ null, '*' ] 14 silly lockFile 313b7776-node-red-node-mysql node-red-node-mysql@ 15 verbose lock node-red-node-mysql@ /home/root/.npm/313b7776-node-red-node-mysql.lock 16 silly addNameRange { name: 'node-red-node-mysql', range: '*', hasData: false } 17 verbose request where is /node-red-node-mysql 18 verbose request registry https://registry.npmjs.org/ 19 verbose request id e85f32bedf8a2218 20 verbose url raw /node-red-node-mysql 21 verbose url resolving [ 'https://registry.npmjs.org/', './node-red-node-mysql' ] 22 verbose url resolved https://registry.npmjs.org/node-red-node-mysql 23 verbose request where is https://registry.npmjs.org/node-red-node-mysql 24 info trying registry request attempt 1 at 23:09:10 25 http GET https://registry.npmjs.org/node-red-node-mysql 26 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND 27 info trying registry request attempt 2 at 23:09:22 28 http GET https://registry.npmjs.org/node-red-node-mysql 29 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND 30 info trying registry request attempt 3 at 23:10:22 31 http GET https://registry.npmjs.org/node-red-node-mysql 32 silly lockFile 313b7776-node-red-node-mysql node-red-node-mysql@ 33 silly lockFile 313b7776-node-red-node-mysql node-red-node-mysql@ 34 error network getaddrinfo ENOTFOUND 34 error network This is most likely not a problem with npm itself 34 error network and is related to network connectivity. 34 error network In most cases you are behind a proxy or have bad network settings. 34 error network 34 error network If you are behind a proxy, please make sure that the 34 error network 'proxy' config is set properly. See: 'npm help config' 35 error System Linux 3.12.27 36 error command "node" "/usr/bin/npm" "install" "node-red-node-mysql" 37 error cwd / 38 error node -v v0.10.40 39 error npm -v 1.4.28 40 error syscall getaddrinfo 41 error code ENOTFOUND 42 error errno ENOTFOUND 43 verbose exit [ 1, true ]I’m going to jump into this conversation as I’m having the same issue and not sure how to resolve it.
I am trying to add a node, specifically a mysql node). I attempted the following:
1) Copy and past the 68-mysql.html and 68-mysql.json files from the above link to
/opt/node-red/nodes/core/storage. Restarted the Conduit, but the mySQL node was not added. I looked at the .config file, and it was updated to include the 68-mysql files. The entry looks like:
`”mysql”: {
“name”: “mysql”,
“types”: [
“MySQLdatabase”,
“mysql”
],
“enabled”: true,
“module”: “node-red”,
“file”: “/opt/node-red/nodes/core/storage/68-mysql.js”
}`2) I tried to add this node via npm (I SSH’d into the Conduit using PuTTY). I did the following
cd /opt/node-red/nodes
npm install node-red-node-mysql
From that, I got the following error`npm WARN package.json mts-gpio@ No descriptionnpm WARN package.json mts-gpio@ No repository field. npm WARN package.json mts-gpio@ No README data npm WARN package.json mts-mcard@ No description npm WARN package.json mts-mcard@ No repository field. npm WARN package.json mts-mcard@ No README data npm WARN package.json mts-serial@ No description npm WARN package.json mts-serial@ No repository field. npm WARN package.json mts-serial@ No README data npm ERR! network getaddrinfo ENOTFOUND npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! System Linux 3.12.27 npm ERR! command "node" "/usr/bin/npm" "install" "node-red-node-mysql" npm ERR! cwd /opt/node-red/nodes npm ERR! node -v v0.10.40 npm ERR! npm -v 1.4.28 npm ERR! syscall getaddrinfo npm ERR! code ENOTFOUND npm ERR! errno ENOTFOUND npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /opt/node-red/nodes/npm-debug.log npm ERR! not ok code 0And alas, the node hasn’t been added to node-red on the Conduit :(. Anyone know what is the cause of this?
Viewing 11 posts - 1 through 11 (of 11 total)