# Daily crashes with ELIFECYCLE. Unable to identify offending node

**URL:** <https://discourse.nodered.org/t/daily-crashes-with-elifecycle-unable-to-identify-offending-node/29692>\
**Category:** General\
**Created:** [8 July 2020 03:46 UTC](https://discourse.nodered.org/t/daily-crashes-with-elifecycle-unable-to-identify-offending-node/29692 "2020-07-08T03:46:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Antil](https://avatars.discourse-cdn.com/v4/letter/a/b2d939/32.png) [@Antil](https://discourse.nodered.org/u/Antil)\
**Post date:** [8 July 2020 03:46 UTC](https://discourse.nodered.org/t/daily-crashes-with-elifecycle-unable-to-identify-offending-node/29692/1 "2020-07-08T03:46:59Z")

</div>

I am getting a daily crash where the system restarts but the error log does not identify the offending node as there is no trace dump. Any pointers appreciated on how to find it.

```auto
npm ERR! errno 1
npm ERR! node-red-docker@1.1.0 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"`
npm ERR! Exit status 1
npm ERR! Failed at the node-red-docker@1.1.0 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! /data/.npm/_logs/2020-07-07T17_23_54_716Z-debug.log

```

Looking at the debug log leaves me with not much either.

```auto
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'start',
1 verbose cli '--cache',
1 verbose cli '/data/.npm',
1 verbose cli '--',
1 verbose cli '--userDir',
1 verbose cli '/data' ]
2 info using npm@6.14.4
3 info using node@v10.21.0
4 verbose config Skipping project config: /usr/src/node-red/.npmrc. (matches userconfig)
5 verbose run-script ['prestart', 'start', 'poststart']
6 info lifecycle node-red-docker@1.1.0~prestart: node-red-docker@1.1.0
7 info lifecycle node-red-docker@1.1.0~start: node-red-docker@1.1.0
8 verbose lifecycle node-red-docker@1.1.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle node-red-docker@1.1.0~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
10 verbose lifecycle node-red-docker@1.1.0~start: CWD: /usr/src/node-red
11 silly lifecycle node-red-docker@1.1.0~start: Args: [ '-c',
11 silly lifecycle 'node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"' ]
12 silly lifecycle node-red-docker@1.1.0~start: Returned: code: 1 signal: null
13 info lifecycle node-red-docker@1.1.0~start: Failed to exec start script
14 verbose stack Error: node-red-docker@1.1.0 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
14 verbose stack at EventEmitter.emit (events.js:198:13)
14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
14 verbose stack at ChildProcess.emit (events.js:198:13)
14 verbose stack at maybeClose (internal/child_process.js:982:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
15 verbose pkgid node-red-docker@1.1.0
16 verbose cwd /usr/src/node-red
17 verbose Linux 4.19.118-v7l+
18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" "--cache" "/data/.npm" "--" "--userDir" "/data"
19 verbose node v10.21.0
20 verbose npm v6.14.4
21 error code ELIFECYCLE
22 error errno 1
23 error node-red-docker@1.1.0 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"`
23 error Exit status 1
24 error Failed at the node-red-docker@1.1.0 start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [1, true]

```

I have tried the suggestions solutions found by a search that involved cleaning the cache and deleting the node\_modules folder followed by a new install. Even completely deployed a freshly build container instance and ported the flows. I am convinced this is related to a installed node, but which one?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [6 September 2020 03:47 UTC](https://discourse.nodered.org/t/daily-crashes-with-elifecycle-unable-to-identify-offending-node/29692/2 "2020-09-06T03:47:03Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.