Last active
February 22, 2016 18:08
-
-
Save MrChrisJ/61ff07629cb4c79bcfd5 to your computer and use it in GitHub Desktop.
IPFS Station Crashing on Raspberry Pi 2
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| pi@raspberrypi:~ $ cd bin/station/ | |
| pi@raspberrypi:~/bin/station $ npm start | |
| > ipfs-station@1.0.0-alpha.1 prestart /home/pi/bin/station | |
| > npm run clean && npm run build:babel | |
| > ipfs-station@1.0.0-alpha.1 clean /home/pi/bin/station | |
| > rimraf build && mkdir build | |
| > ipfs-station@1.0.0-alpha.1 build:babel /home/pi/bin/station | |
| > babel app/config.js -o build/config.js && babel app/controls -d build/controls && babel app/init.js -o build/init.js | |
| app/controls/drag-drop.js -> build/controls/drag-drop.js | |
| app/controls/open-browser.js -> build/controls/open-browser.js | |
| app/controls/open-console.js -> build/controls/open-console.js | |
| app/controls/open-settings.js -> build/controls/open-settings.js | |
| app/controls/utils.js -> build/controls/utils.js | |
| > ipfs-station@1.0.0-alpha.1 start /home/pi/bin/station | |
| > concurrent --kill-others 'node dev-server.js' 'npm run electron' | |
| [0] Development server started at http://localhost:3000 | |
| [1] | |
| [1] > ipfs-station@1.0.0-alpha.1 electron /home/pi/bin/station | |
| [1] > electron index.js | |
| [1] | |
| [1] info: Application is ready | |
| [1] info: Starting tray | |
| [1] info: Initialzing new node | |
| [0] webpack built b81196ecf04a17b19064 in 50732ms | |
| [1] info: Initializing new node with key size: 4096 in /home/pi/.ipfs. | |
| [1] (node) warning: possible EventEmitter memory leak detected. 11 did-finish-load listeners added. Use emitter.setMaxListeners() to increase limit. | |
| [1] Trace | |
| [1] at EventEmitter.addListener (events.js:239:17) | |
| [1] at EventEmitter.webContents.executeJavaScript (/home/pi/bin/station/node_modules/electron-prebuilt/dist/resources/atom.asar/browser/api/lib/web-contents.js:73:28) | |
| [1] at /home/pi/bin/station/node_modules/electron-safe-ipc/host.js:19:24 | |
| [1] at Array.forEach (native) | |
| [1] at EventEmitter.ipc.send (/home/pi/bin/station/node_modules/electron-safe-ipc/host.js:14:33) | |
| [1] at /home/pi/bin/station/build/init.js:60:9 | |
| [1] at finish (/home/pi/bin/station/node_modules/wreck/lib/index.js:319:16) | |
| [1] at wrapped (/home/pi/bin/station/node_modules/wreck/node_modules/hoek/lib/index.js:867:20) | |
| [1] at [object Object].onReaderFinish (/home/pi/bin/station/node_modules/wreck/lib/index.js:365:16) | |
| [1] --------------------------------------------- | |
| [1] at [object Object].internals.Client.request.collector.once.internals.Client.read.onReaderError [as read] (/home/pi/bin/station/node_modules/wreck/lib/index.js:368:12) | |
| [1] at /home/pi/bin/station/node_modules/ipfsd-ctl/node_modules/ipfs-api/src/request-api.js:55:11 | |
| [1] at finish (/home/pi/bin/station/node_modules/wreck/lib/index.js:146:20) | |
| [1] at wrapped (/home/pi/bin/station/node_modules/wreck/node_modules/hoek/lib/index.js:867:20) | |
| [1] at ClientRequest.onResponse (/home/pi/bin/station/node_modules/wreck/lib/index.js:169:20) | |
| [1] at emitOne (events.js:77:13) | |
| [1] at ClientRequest.emit (events.js:169:7) | |
| [1] --------------------------------------------- | |
| [1] at [object Object].internals.Client.request.collector.once.req.abort [as request] (/home/pi/bin/station/node_modules/wreck/lib/index.js:207:9) | |
| [1] at requestAPI (/home/pi/bin/station/node_modules/ipfsd-ctl/node_modules/ipfs-api/src/request-api.js:111:9) | |
| [1] at Object.peers (/home/pi/bin/station/node_modules/ipfsd-ctl/node_modules/ipfs-api/src/cmd-helpers.js:9:12) | |
| [1] at pollStats (/home/pi/bin/station/build/init.js:56:14) | |
| [1] at [object Object].<anonymous> (/home/pi/bin/station/build/init.js:99:9) | |
| [1] at [object Object].wrapper [as _onTimeout] (timers.js:275:19) | |
| [1] at Timer.listOnTimeout (timers.js:92:15) | |
| [1] npm run electron exited with code 0 | |
| --> Sending SIGTERM to other processes.. | |
| [0] node dev-server.js exited with code null | |
| npm ERR! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ELIFECYCLE | |
| npm ERR! ipfs-station@1.0.0-alpha.1 start: `concurrent --kill-others 'node dev-server.js' 'npm run electron'` | |
| npm ERR! Exit status 1 | |
| npm ERR! | |
| npm ERR! Failed at the ipfs-station@1.0.0-alpha.1 start script 'concurrent --kill-others 'node dev-server.js' 'npm run electron''. | |
| npm ERR! Make sure you have the latest version of node.js and npm installed. | |
| npm ERR! If you do, this is most likely a problem with the ipfs-station package, | |
| npm ERR! not with npm itself. | |
| npm ERR! Tell the author that this fails on your system: | |
| npm ERR! concurrent --kill-others 'node dev-server.js' 'npm run electron' | |
| npm ERR! You can get information on how to open an issue for this project with: | |
| npm ERR! npm bugs ipfs-station | |
| npm ERR! Or if that isn't available, you can get their info via: | |
| npm ERR! npm owner ls ipfs-station | |
| npm ERR! There is likely additional logging output above. | |
| npm ERR! Please include the following file with any support request: | |
| npm ERR! /home/pi/bin/station/npm-debug.log | |
| pi@raspberrypi:~/bin/station $ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ## No idea what's causing this as I have no proxy running. Tor and VPN are uninstalled. | |
| pi@raspberrypi:~/bin/station $ npm install | |
| npm ERR! tar.unpack error reading /tmp/npm-1287-53dd813e/registry.npmjs.org/bl/-/bl-1.0.3.tgz | |
| npm ERR! tar.unpack error reading /tmp/npm-1287-53dd813e/registry.npmjs.org/binary/-/binary-0.3.0.tgz | |
| npm ERR! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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' | |
| ^C | |
| pi@raspberrypi:~/bin/station $ | |
| pi@raspberrypi:~/bin/station $ sudo reboot | |
| Connection to 192.168.0.2 closed by remote host. | |
| Connection to 192.168.0.2 closed. | |
| Chriss-MacBook-Pro-4:~ chris$ ssh pi@192.168.0.2 | |
| pi@192.168.0.2's password: | |
| The programs included with the Debian GNU/Linux system are free software; | |
| the exact distribution terms for each program are described in the | |
| individual files in /usr/share/doc/*/copyright. | |
| Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent | |
| permitted by applicable law. | |
| Last login: Mon Feb 22 16:54:15 2016 | |
| pi@raspberrypi:~ $ cd bin/station/ | |
| pi@raspberrypi:~/bin/station $ npm install | |
| npm ERR! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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' | |
| ^C | |
| pi@raspberrypi:~/bin/station $ | |
| pi@raspberrypi:~/bin/station $ sudo apt-get remove --purge openvpn resolvconf -yReading package lists... Done | |
| Building dependency tree | |
| Reading state information... Done | |
| The following packages were automatically installed and are no longer required: | |
| easy-rsa libpkcs11-helper1 opensc opensc-pkcs11 torsocks | |
| Use 'apt-get autoremove' to remove them. | |
| The following packages will be REMOVED: | |
| openvpn* resolvconf* | |
| 0 upgraded, 0 newly installed, 2 to remove and 10 not upgraded. | |
| After this operation, 1,180 kB disk space will be freed. | |
| (Reading database ... 102984 files and directories currently installed.) | |
| Removing openvpn (2.3.4-5+deb8u1) ... | |
| Purging configuration files for openvpn (2.3.4-5+deb8u1) ... | |
| Removing resolvconf (1.76.1) ... | |
| resolvconf.postrm: Reboot recommended | |
| Purging configuration files for resolvconf (1.76.1) ... | |
| Processing triggers for man-db (2.7.0.2-5) ... | |
| Processing triggers for libc-bin (2.19-18+deb8u2) ... | |
| pi@raspberrypi:~/bin/station $ sudo reboot | |
| Connection to 192.168.0.2 closed by remote host. | |
| Connection to 192.168.0.2 closed. | |
| Chriss-MacBook-Pro-4:~ chris$ ssh pi@192.168.0.2 | |
| pi@192.168.0.2's password: | |
| The programs included with the Debian GNU/Linux system are free software; | |
| the exact distribution terms for each program are described in the | |
| individual files in /usr/share/doc/*/copyright. | |
| Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent | |
| permitted by applicable law. | |
| Last login: Mon Feb 22 16:58:41 2016 | |
| pi@raspberrypi:~ $ cd bin/station/ | |
| pi@raspberrypi:~/bin/station $ nmp cache clean | |
| -bash: nmp: command not found | |
| pi@raspberrypi:~/bin/station $ npm cache clean | |
| pi@raspberrypi:~/bin/station $ npm install | |
| npm ERR! tar.unpack error reading /tmp/npm-545-18fa98fc/registry.npmjs.org/babel-generator/-/babel-generator-6.5.0.tgz | |
| npm ERR! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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! Linux 4.1.17-v7+ | |
| npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" | |
| npm ERR! node v4.0.0 | |
| npm ERR! npm v3.7.3 | |
| npm ERR! code ECONNRESET | |
| npm ERR! errno ECONNRESET | |
| npm ERR! syscall read | |
| npm ERR! network read ECONNRESET | |
| 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' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment