# Node-RED doesn't start anymore

**URL:** <https://discourse.nodered.org/t/node-red-doesnt-start-anymore/8698>\
**Category:** General\
**Created:** [7 March 2019 09:45 UTC](https://discourse.nodered.org/t/node-red-doesnt-start-anymore/8698 "2019-03-07T09:45:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kees](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kees/32/5881_2.png) [@Kees](https://discourse.nodered.org/u/Kees)\
**Post date:** [7 March 2019 09:45 UTC](https://discourse.nodered.org/t/node-red-doesnt-start-anymore/8698/1 "2019-03-07T09:45:46Z")

</div>

My Node\_RED on Raspberry Pi doesn't start anymore.  
What can I do?

Log:

# 7 Mar 10:32:05 - [info] Welcome to Node-RED

## 7 Mar 10:32:05 - [info] Node-RED version: v0.19.5 7 Mar 10:32:05 - [info] Node.js version: v8.15.1 7 Mar 10:32:05 - [info] Linux 4.14.98-v7+ arm LE 7 Mar 10:32:06 - [info] Loading palette nodes 7 Mar 10:32:12 - [info] Dashboard version 2.10.1 started at /ui 7 Mar 10:32:13 - [warn] ------------------------------------------------------ 7 Mar 10:32:13 - [warn] [node-red-contrib-join/join] Type already registered 7 Mar 10:32:13 - [warn] ------------------------------------------------------ 7 Mar 10:32:13 - [info] Settings file : /home/pi/.node-red/settings.js 7 Mar 10:32:13 - [info] HTTP Static : /home/pi 7 Mar 10:32:13 - [info] Context store : 'default' [module=memory] 7 Mar 10:32:13 - [info] User directory : /home/pi/.node-red 7 Mar 10:32:13 - [warn] Projects disabled : editorTheme.projects.enabled=false 7 Mar 10:32:13 - [info] Flows file : /home/pi/.node-red/flows\_RasPi3.json 7 Mar 10:32:13 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/) 7 Mar 10:32:13 - [warn]

## Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials file will not be recoverable, you will have to delete it and re-enter your credentials. You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

7 Mar 10:32:13 - [info] Starting flows  
7 Mar 10:32:14 - [info] Started flows  
7 Mar 10:32:14 - [info] [sqlitedb:e16c76ef.539d58] opened sqlite/nieuws.db ok  
7 Mar 10:32:14 - [info] [sqlitedb:e16c76ef.539d58] opened sqlite/nieuws.db ok  
7 Mar 10:32:14 - [info] [sqlitedb:457cf60e.f0cf48] opened sqlite/nodered.db ok  
7 Mar 10:32:14 - [info] [sqlitedb:457cf60e.f0cf48] opened sqlite/nodered.db ok  
7 Mar 10:32:14 - [info] [sqlitedb:457cf60e.f0cf48] opened sqlite/nodered.db ok  
7 Mar 10:32:14 - [info] [mqtt-broker:ac303ca4.001af] Connected to broker: mqtt://192.168.0.118:1883  
7 Mar 10:32:16 - [error] [function:Set maanstand] TypeError: Cannot read property 'ageOfMoon' of undefined  
7 Mar 10:32:21 - [red] Uncaught Exception:  
7 Mar 10:32:21 - TypeError: Cannot read property 'code' of undefined  
at /home/pi/.node-red/node\_modules/node-red-contrib-broadlink-control/nodes/RMNode.js:92:143  
nodered.service: Main process exited, code=exited, status=1/FAILURE  
nodered.service: Unit entered failed state.  
nodered.service: Failed with result 'exit-code'.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [7 March 2019 10:17 UTC](https://discourse.nodered.org/t/node-red-doesnt-start-anymore/8698/2 "2019-03-07T10:17:22Z")

</div>

The problem is with the broadlink node  
node-red-contrib-broadlink-control which should handle the error gracefully. So one thing you need to do is log an issue with the nodes author to get it fixed.  
You can follow a link from [flows.nodered.org](http://flows.nodered.org) to the nodes github page.

Next thing is to try rolling back to your last version.  
If you cd into your .node-red directory and list all the files there is a hidden file called  
`.flows_RasPi3.json.backup` (note the leading dot)

copy your existing flows file to a new location (just to be safe) and then rename the backup file to `flows_RasPi3.json` and restart node-RED.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [7 March 2019 10:19 UTC](https://discourse.nodered.org/t/node-red-doesnt-start-anymore/8698/3 "2019-03-07T10:19:00Z")

</div>

Well as you can see you have several errors there. The first is that you have two join nodes installed so I suggest removing node-red-contrib-join unless you really need it.

The next is that you have an error in function:Set maanstand.

The third, which is the one that is killing node-red appears to be a bug in node-red-contrib-broadlink-control. If you uninstall that node from the command line using

```auto
cd .node-red
npm remove node-red-contrib-broadlink-control

```

then restart node-red you will at least be able to get into the editor and can then work out where to go from there.

---

<div class="post-metadata">

**Author:** ![Kees](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kees/32/5881_2.png) [@Kees](https://discourse.nodered.org/u/Kees)\
**Post date:** [8 March 2019 12:34 UTC](https://discourse.nodered.org/t/node-red-doesnt-start-anymore/8698/4 "2019-03-08T12:34:25Z")

</div>

Thanks for your help.  
However I had the same issue with the backup file. I had to remove node-red-contrib-broadlink-control.