# Npm ERR! code ELIFECYCLE - Error: read ECONNRESET
**URL:** https://discourse.nodered.org/t/npm-err-code-elifecycle-error-read-econnreset/60633
**Category:** General
**Tags:** node-red-dashboard
**Created:** [1 April 2022 07:49 UTC](https://discourse.nodered.org/t/npm-err-code-elifecycle-error-read-econnreset/60633 "2022-04-01T07:49:11Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@energyplot](https://discourse.nodered.org/u/energyplot)
#### Post date: [1 April 2022 07:49 UTC](https://discourse.nodered.org/t/npm-err-code-elifecycle-error-read-econnreset/60633/1 "2022-04-01T07:49:11Z")
I'm receiving this error and node-red is stopping every couple hours.
[red] Uncaught Exception:
Error: read ECONNRESET
at TCP.onStreamRead (internal/stream\_base\_commons.js:111:27)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-red-docker@1.3.5 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data" "--safe"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red-docker@1.3.5 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! /root/.npm/\_logs/dateT16\_41\_17\_082Z-debug.log
* * *
I can't find any solution
[info] Node-RED version: v1.3.5
[info] Node.js version: v10.24.1
[info] Linux 4.19.0-19-cloud-amd64 x64 LE
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [1 April 2022 09:12 UTC](https://discourse.nodered.org/t/npm-err-code-elifecycle-error-read-econnreset/60633/2 "2022-04-01T09:12:58Z")
Welcome to the forum @energyplot
Have you installed any non-builtin nodes?
**[Edit]** Also look in the log file mentioned to see if there is any additional information.
---
### Author:  [@energyplot](https://discourse.nodered.org/u/energyplot)
#### Post date: [4 April 2022 07:24 UTC](https://discourse.nodered.org/t/npm-err-code-elifecycle-error-read-econnreset/60633/3 "2022-04-04T07:24:20Z")
I just installed: node-red-contrib-modbus, node-red-contrib-ignition-nodes, node-red-node-ping.
I can not see something clear in log file:
2 info using npm@6.14.12
3 info using node@v10.24.1
4 verbose run-script ['prestart', 'start', 'poststart']
5 info lifecycle node-red-docker@1.3.5~prestart: node-red-docker@1.3.5
6 info lifecycle node-red-docker@1.3.5~start: node-red-docker@1.3.5
7 verbose lifecycle node-red-docker@1.3.5~start: unsafe-perm in lifecycle true
8 verbose lifecycle node-red-docker@1.3.5~start: PATH: /usr/local/lib/node\_modules/npm/node\_modules/npm-lifecycle/node-gyp-bin:/usr/src/node-red/node\_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle node-red-docker@1.3.5~start: CWD: /usr/src/node-red
10 silly lifecycle node-red-docker@1.3.5~start: Args: [ '-c',
10 silly lifecycle 'node $NODE\_OPTIONS node\_modules/node-red/red.js $FLOWS "--userDir" "/data" "--safe"' ]
11 silly lifecycle node-red-docker@1.3.5~start: Returned: code: 1 signal: null
12 info lifecycle node-red-docker@1.3.5~start: Failed to exec start script
13 verbose stack Error: node-red-docker@1.3.5 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data" "--safe"`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/lib/node\_modules/npm/node\_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/local/lib/node\_modules/npm/node\_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child\_process.js:982:16)
13 verbose stack at Process.ChildProcess.\_handle.onexit (internal/child\_process.js:259:5)
14 verbose pkgid node-red-docker@1.3.5
15 verbose cwd /usr/src/node-red
16 verbose Linux 4.19.0-19-cloud-amd64
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" "--" "--userDir" "/data" "--safe"
18 verbose node v10.24.1
19 verbose npm v6.14.12
20 error code ELIFECYCLE
21 error errno 1
22 error node-red-docker@1.3.5 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data" "--safe"`
22 error Exit status 1
23 error Failed at the node-red-docker@1.3.5 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [4 April 2022 07:52 UTC](https://discourse.nodered.org/t/npm-err-code-elifecycle-error-read-econnreset/60633/4 "2022-04-04T07:52:59Z")
Has it previously worked? If so then what changed immediately before it failed?
---
### Author:  [@energyplot](https://discourse.nodered.org/u/energyplot)
#### Post date: [4 April 2022 07:58 UTC](https://discourse.nodered.org/t/npm-err-code-elifecycle-error-read-econnreset/60633/5 "2022-04-04T07:58:20Z")
It can work for a some hours until it crashes. Everything seems to work fine, but every 24h I think fails with that same error. I'm trying to upgrade node and npm to a newer version. Any other idea?
---
### Author:  [@energyplot](https://discourse.nodered.org/u/energyplot)
#### Post date: [6 April 2022 11:40 UTC](https://discourse.nodered.org/t/npm-err-code-elifecycle-error-read-econnreset/60633/6 "2022-04-06T11:40:35Z")
I updated Node-red/NPM/NodeJS so the problem seems to be resolved
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [20 April 2022 11:41 UTC](https://discourse.nodered.org/t/npm-err-code-elifecycle-error-read-econnreset/60633/7 "2022-04-20T11:41:19Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.