# Node red wont start - INFO: Service Node-RED exited with code 1 (by signal 0)

**URL:** <https://discourse.nodered.org/t/node-red-wont-start-info-service-node-red-exited-with-code-1-by-signal-0/86906>\
**Category:** General\
**Tags:** home-assistant\
**Created:** [1 April 2024 05:57 UTC](https://discourse.nodered.org/t/node-red-wont-start-info-service-node-red-exited-with-code-1-by-signal-0/86906 "2024-04-01T05:57:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MankiniChykan](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mankinichykan/32/89774_2.png) [@MankiniChykan](https://discourse.nodered.org/u/MankiniChykan)\
**Post date:** [1 April 2024 05:57 UTC](https://discourse.nodered.org/t/node-red-wont-start-info-service-node-red-exited-with-code-1-by-signal-0/86906/1 "2024-04-01T05:57:47Z")

</div>

My Error Log below:

I HAVE A FEELING IT HAS SOMETHING TO DO WITH THIS NODE NOT BEING SETUP CORRECTLY. Node Red would not deploy the node when I was editing it. I run Node Red on a Homesassistant Blue Odroid N2+

1 Apr 16:47:01 - [red] Uncaught Exception:  
1 Apr 16:47:01 - [error] Error: Invalid username  
at Client.connect (/config/node\_modules/ssh2/lib/client.js:203:13)  
at \_connectClient (/config/node\_modules/@jorgelserve/node-red-contrib-ssh-v3/ssh.js:56:21)

## s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service base-addon-banner: starting

## Add-on: Node-RED Flow-based programming for the Internet of Things

## Add-on version: 17.0.11 You are running the latest version of this add-on. System: Home Assistant OS 12.1 (aarch64 / odroid-n2) Home Assistant Core: 2024.3.3 Home Assistant Supervisor: 2024.03.1

## Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started  
s6-rc: info: service fix-attrs: starting  
s6-rc: info: service base-addon-log-level: starting  
s6-rc: info: service fix-attrs successfully started  
s6-rc: info: service base-addon-log-level successfully started  
s6-rc: info: service legacy-cont-init: starting  
s6-rc: info: service legacy-cont-init successfully started  
s6-rc: info: service init-nginx: starting  
s6-rc: info: service init-customizations: starting  
s6-rc: info: service init-customizations successfully started  
s6-rc: info: service init-nodered: starting  
s6-rc: info: service init-nginx successfully started

s6-rc: info: service base-addon-banner successfully started  
s6-rc: info: service fix-attrs: starting  
s6-rc: info: service base-addon-log-level: starting  
s6-rc: info: service fix-attrs successfully started  
s6-rc: info: service base-addon-log-level successfully started  
s6-rc: info: service legacy-cont-init: starting  
s6-rc: info: service legacy-cont-init successfully started  
s6-rc: info: service init-nginx: starting  
s6-rc: info: service init-customizations: starting  
s6-rc: info: service init-customizations successfully started  
s6-rc: info: service init-nodered: starting  
s6-rc: info: service init-nginx successfully started

up to date, audited 390 packages in 4s

69 packages are looking for funding  
run `npm fund` for details

18 vulnerabilities (17 moderate, 1 critical)

To address issues that do not require attention, run:  
npm audit fix

To address all issues possible (including breaking changes), run:  
npm audit fix --force

Some issues need review, and may require choosing  
a different dependency.

Run `npm audit` for details.  
npm notice  
npm notice New minor version of npm available! 10.2.4 -\> 10.5.0  
npm notice Changelog: [https://github.com/npm/cli/releases/tag/v10.5.0](https://github.com/npm/cli/releases/tag/v10.5.0)  
npm notice Run `npm install -g npm@10.5.0` to update!  
npm notice  
s6-rc: info: service init-nodered successfully started  
s6-rc: info: service nodered: starting  
s6-rc: info: service nodered successfully started  
s6-rc: info: service nginx: starting  
s6-rc: info: service nginx successfully started  
s6-rc: info: service legacy-services: starting  
s6-rc: info: service legacy-services successfully started  
[16:46:52] INFO: Starting Node-RED...

> start  
> node $NODE\_OPTIONS node\_modules/node-red/red.js --settings /etc/node-red/config.js

1 Apr 16:46:54 - [info]

# Welcome to Node-RED

1 Apr 16:46:54 - [info] Node-RED version: v3.1.8  
1 Apr 16:46:54 - [info] Node.js version: v18.19.1  
1 Apr 16:46:54 - [info] Linux 6.6.20-haos arm64 LE  
1 Apr 16:46:55 - [info] Loading palette nodes  
1 Apr 16:46:55 - [info] Node-RED Contrib Theme Collection version: v3.1.11  
1 Apr 16:46:58 - [info] Dashboard version 3.6.5 started at /endpoint/ui  
1 Apr 16:47:00 - [info] Settings file : /etc/node-red/config.js  
1 Apr 16:47:00 - [info] Context store : 'default' [module=memory]  
1 Apr 16:47:00 - [info] User directory : /config/  
1 Apr 16:47:00 - [warn] Projects disabled : editorTheme.projects.enabled=false  
1 Apr 16:47:00 - [info] Flows file : /config/flows.json  
1 Apr 16:47:00 - [info] Server now running at [http://127.0.0.1:46836/](http://127.0.0.1:46836/)  
[16:47:00] INFO: Starting NGinx...  
1 Apr 16:47:00 - [info] Starting flows  
1 Apr 16:47:01 - [error] [persist-store:62c146efef17dd2b] /home/Node-RED/persistance.json: ENOENT: no such file or directory, open '/home/Node-RED/persistance.json'  
1 Apr 16:47:01 - [error] [persist-store:42dd5cc5.694f1c] /home/Node-RED/persistance.json: ENOENT: no such file or directory, open '/home/Node-RED/persistance.json'  
1 Apr 16:47:01 - [info] [tcp in:1da40daa7ab33221] connecting to 192.168.1.72:23  
1 Apr 16:47:01 - [warn] [RED.events] Deprecated use of "nodes-started" event from "/config/node\_modules/node-red-contrib-persist/persist.js:164:20". Use "flows:started" instead.  
1 Apr 16:47:01 - [error] [trigger-state:200c386fe013d6ce] ConfigError: trigger-state.error.enttity\_id\_required  
1 Apr 16:47:01 - [info] Started flows  
1 Apr 16:47:01 - [red] Uncaught Exception:  
1 Apr 16:47:01 - [error] Error: Invalid username  
at Client.connect (/config/node\_modules/ssh2/lib/client.js:203:13)  
at \_connectClient (/config/node\_modules/@jorgelserve/node-red-contrib-ssh-v3/ssh.js:56:21)  
[16:47:01] INFO: Service Node-RED exited with code 1 (by signal 0)  
s6-rc: info: service legacy-services: stopping  
s6-rc: info: service legacy-services successfully stopped  
s6-rc: info: service nginx: stopping  
[16:47:01] INFO: Service NGINX exited with code 0 (by signal 0)  
s6-rc: info: service nginx successfully stopped  
s6-rc: info: service init-nginx: stopping  
s6-rc: info: service nodered: stopping  
s6-rc: info: service init-nginx successfully stopped  
s6-rc: info: service nodered successfully stopped  
s6-rc: info: service init-nodered: stopping  
s6-rc: info: service init-nodered successfully stopped  
s6-rc: info: service init-customizations: stopping  
s6-rc: info: service init-customizations successfully stopped  
s6-rc: info: service legacy-cont-init: stopping  
s6-rc: info: service legacy-cont-init successfully stopped  
s6-rc: info: service fix-attrs: stopping  
s6-rc: info: service base-addon-log-level: stopping  
s6-rc: info: service base-addon-log-level successfully stopped  
s6-rc: info: service fix-attrs successfully stopped  
s6-rc: info: service base-addon-banner: stopping  
s6-rc: info: service base-addon-banner successfully stopped  
s6-rc: info: service s6rc-oneshot-runner: stopping  
s6-rc: info: service s6rc-oneshot-runner successfully stopped

---

<div class="post-metadata">

**Author:** ![MankiniChykan](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mankinichykan/32/89774_2.png) [@MankiniChykan](https://discourse.nodered.org/u/MankiniChykan)\
**Post date:** [1 April 2024 06:24 UTC](https://discourse.nodered.org/t/node-red-wont-start-info-service-node-red-exited-with-code-1-by-signal-0/86906/2 "2024-04-01T06:24:05Z")

</div>

- Restarting Home Assistant did not work
- Power Cycling my Home Assistant Blue did not work

OK... I managed to fix this by starting Node Red in Safe Mode.  
I deleted the node that was not setup correctly and it is all working again now.

Anyone who has the same problem...

- Select Safe Mode from the configuration menu.
- The flows will load but not started
- Make repairs, then re-deploy the nodes.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/1/b1bf125ae95bfcdd19c41d62a07e0e4185d9034a.png)

---

<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:** [15 April 2024 06:24 UTC](https://discourse.nodered.org/t/node-red-wont-start-info-service-node-red-exited-with-code-1-by-signal-0/86906/3 "2024-04-15T06:24:21Z")

</div>

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