BScrk
ECONNRESET issue
Hello. I permanently get this error. Windows10x64 with nodejs
`2018/01/24 11:49:19 INFO # Work from t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen accepted 2018/01/24 11:49:29 INFO # Submit work for t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen 2018/01/24 11:49:30 INFO # Work from t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen accepted 2018/01/24 11:49:34 INFO # Submit work for t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen 2018/01/24 11:49:34 INFO # Work from t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen accepted 2018/01/24 11:49:54 ERROR # Network error, Error: read ECONNRESET 2018/01/24 11:49:54 INFO # Connecting to zec-eu1.nanopool.org:6666 2018/01/24 11:49:55 INFO # Connected to pool zec-eu1.nanopool.org:6666 2018/01/24 11:49:55 WARN # Creating workers listner... 2018/01/24 11:49:55 INFO # Subscribing to pool... events.js:183 throw er; // Unhandled 'error' event ^
Error: listen EADDRINUSE :::8000
at Object._errnoException (util.js:1022:11)
at _exceptionWithHostPort (util.js:1044:20)
at Server.setupListenHandle [as _listen2] (net.js:1351:14)
at listenInCluster (net.js:1392:12)
at Server.listen (net.js:1476:7)
at new MinersController (C:\zecproxy\lib\miners_controller.js:23:8)
at PoolConnector.onConnect (C:\zecproxy\lib\pool_connector.js:32:27)
at Socket.poolSocket.on (C:\zecproxy\lib\pool_connector.js:161:60)
at emitNone (events.js:111:20)
at Socket.emit (events.js:208:7)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node proxy.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start 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! C:\Users\User\AppData\Roaming\npm-cache_logs\2018-01-24T08_49_55_171Z-debug.log`
log
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\zecproxy\node_modules.bin;C:\Users\User\AppData\Roaming\npm;C:\Program Files\nodejs;C:\Python27;C:\Python27\Scripts;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\MSI Afterburner;;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\nodejs;C:\Users\User\AppData\Local\Microsoft\WindowsApps;C:\Users\User\AppData\Roaming\npm
9 verbose lifecycle [email protected]~start: CWD: C:\zecproxy
10 silly lifecycle [email protected]~start: Args: [ '/d /s /c', 'node proxy.js' ]
11 silly lifecycle [email protected]~start: Returned: code: 1 signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: node proxy.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.node proxy.js
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Error: listen EADDRINUSE :::8000
means that you need to change the port in config because you already have something using that port
