# Missing node error on deploy... But it's still in palette manager...(?)

**URL:** <https://discourse.nodered.org/t/missing-node-error-on-deploy-but-its-still-in-palette-manager/55745>\
**Category:** General\
**Created:** [27 December 2021 10:24 UTC](https://discourse.nodered.org/t/missing-node-error-on-deploy-but-its-still-in-palette-manager/55745 "2021-12-27T10:24:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jay1234](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@Jay1234](https://discourse.nodered.org/u/Jay1234)\
**Post date:** [27 December 2021 10:24 UTC](https://discourse.nodered.org/t/missing-node-error-on-deploy-but-its-still-in-palette-manager/55745/1 "2021-12-27T10:24:35Z")

</div>

I've been experimenting with the Aedes MQTT broker, but have run into an issue where i receive a yellow warning message after deploying changes that reads "Flows stopped due to missing node times: aedes broker"

I have already tried removing the node and re-installing the, while performing multiple reboots of the pi running NR along the way. I even removed all MQTT nodes and deleted the MQTT server before re-installing. But... the issue doesn't want to go away... So, below is a trace log of NR starting and changes being deployed that I'm hoping someone can use to help point me in the right direction...

```auto
Welcome to Node-RED
===================
27 Dec 20:48:28 - [info] Node-RED version: v2.1.4
27 Dec 20:48:28 - [info] Node.js version: v14.18.2
27 Dec 20:48:28 - [info] Linux 5.10.63-v7+ arm LE
27 Dec 20:48:31 - [info] Loading palette nodes
27 Dec 20:48:32 - [debug] Module: node-red-contrib-aedes 0.6.0 /home/astroberry/.node-red/node_modules/node-red-contrib-aedes
27 Dec 20:48:32 - [debug] Module: node-red-contrib-metric-per-topic 0.2.0 /home/astroberry/.node-red/node_modules/node-red-contrib-metric-per-topic
27 Dec 20:48:32 - [debug] Module: node-red-contrib-mqtt-broker 0.2.9 /home/astroberry/.node-red/node_modules/node-red-contrib-mqtt-broker
27 Dec 20:48:32 - [debug] Module: node-red-contrib-play-audio 2.5.0 /home/astroberry/.node-red/node_modules/node-red-contrib-play-audio
27 Dec 20:48:32 - [debug] Module: node-red-contrib-python-function 0.0.5 /home/astroberry/.node-red/node_modules/node-red-contrib-python-function
27 Dec 20:48:32 - [debug] Module: node-red-contrib-rpi-imagecapture 0.0.2 /home/astroberry/.node-red/node_modules/node-red-contrib-rpi-imagecapture
27 Dec 20:48:32 - [debug] Module: node-red-contrib-rpi-shutdown 0.0.2 /home/astroberry/.node-red/node_modules/node-red-contrib-rpi-shutdown
27 Dec 20:48:32 - [debug] Module: node-red-contrib-ui-digital-display 1.0.3 /home/astroberry/.node-red/node_modules/node-red-contrib-ui-digital-display
27 Dec 20:48:32 - [debug] Module: node-red-dashboard 3.1.3 /home/astroberry/.node-red/node_modules/node-red-dashboard
27 Dec 20:48:32 - [debug] Module: node-red-node-pi-gpio 2.0.1 /home/astroberry/.node-red/node_modules/node-red-node-pi-gpio
27 Dec 20:48:32 - [debug] Module: node-red-node-ping 0.3.1 /home/astroberry/.node-red/node_modules/node-red-node-ping
27 Dec 20:48:32 - [debug] Module: node-red-node-random 0.4.0 /home/astroberry/.node-red/node_modules/node-red-node-random
27 Dec 20:48:32 - [debug] Module: node-red-node-serialport 0.15.0 /home/astroberry/.node-red/node_modules/node-red-node-serialport
27 Dec 20:48:32 - [debug] Module: node-red-node-smooth 0.1.2 /home/astroberry/.node-red/node_modules/node-red-node-smooth
27 Dec 20:48:41 - [info] Dashboard version 3.1.3 started at /ui
27 Dec 20:48:42 - [warn] ------------------------------------------------------
27 Dec 20:48:42 - [warn] [node-red-contrib-aedes/aedes-mqtt-broker] Error: Could not locate the bindings file. Tried:
 â /home/astroberry/.node-red/node_modules/snappy/build/binding.node
 â /home/astroberry/.node-red/node_modules/snappy/build/Debug/binding.node
 â /home/astroberry/.node-red/node_modules/snappy/build/Release/binding.node
 â /home/astroberry/.node-red/node_modules/snappy/out/Debug/binding.node
 â /home/astroberry/.node-red/node_modules/snappy/Debug/binding.node
 â /home/astroberry/.node-red/node_modules/snappy/out/Release/binding.node
 â /home/astroberry/.node-red/node_modules/snappy/Release/binding.node
 â /home/astroberry/.node-red/node_modules/snappy/build/default/binding.node
 â /home/astroberry/.node-red/node_modules/snappy/compiled/14.18.2/linux/arm/binding.node
27 Dec 20:48:42 - [warn] ------------------------------------------------------
27 Dec 20:48:42 - [info] Settings file : /home/astroberry/.node-red/settings.js
27 Dec 20:48:42 - [info] Context store : 'default' [module=memory]
27 Dec 20:48:42 - [info] User directory : /home/astroberry/.node-red
27 Dec 20:48:42 - [warn] Projects disabled : editorTheme.projects.enabled=false
27 Dec 20:48:42 - [info] Flows file : /home/astroberry/.node-red/flows.json
27 Dec 20:48:42 - [info] Server now running at http://127.0.0.1:1880/
27 Dec 20:48:42 - [debug] loaded flow revision: 94ee9fce362f3ff4306de24c4c921e3e
27 Dec 20:48:42 - [debug] red/runtime/nodes/credentials.load : no user key present
27 Dec 20:48:42 - [debug] red/runtime/nodes/credentials.load : using default key
27 Dec 20:48:42 - [debug] red/runtime/nodes/credentials.load : keyType=system
27 Dec 20:48:42 - [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.
---------------------------------------------------------------------
27 Dec 20:48:42 - [trace] runtime event: {"id":"runtime-state","retain":true}
27 Dec 20:48:42 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"94ee9fce362f3ff4306de24c4c921e3e"},"retain":true}
27 Dec 20:48:42 - [info] Waiting for missing types to be registered:
27 Dec 20:48:42 - [info] - aedes broker
27 Dec 20:48:42 - [trace] runtime event: {"id":"runtime-state","payload":{"error":"missing-types","type":"warning","text":"notification.warnings.missing-types","types":["aedes broker"]},"retain":true}
27 Dec 20:48:42 - [trace] comms.open 6A2FWOBurYD4LSuGzEdbqwg1um1co2k2h8B0+2EQStU=
27 Dec 20:49:37 - [trace] utils.writeFile - copied /home/astroberry/.node-red/flows.json TO /home/astroberry/.node-red/.flows.json.backup
27 Dec 20:49:37 - [trace] utils.writeFile - written content to /home/astroberry/.node-red/flows.json.$$$
27 Dec 20:49:37 - [trace] utils.writeFile - renamed /home/astroberry/.node-red/flows.json.$$$ to /home/astroberry/.node-red/flows.json
27 Dec 20:49:37 - [debug] saved flow revision: 44fba06ed053541db2a0f8c91467f91e
27 Dec 20:49:37 - [info] Stopping flows
27 Dec 20:49:37 - [info] Stopped flows
27 Dec 20:49:37 - [info] Waiting for missing types to be registered:
27 Dec 20:49:37 - [info] - aedes broker
27 Dec 20:49:37 - [trace] runtime event: {"id":"runtime-state","payload":{"error":"missing-types","type":"warning","text":"notification.warnings.missing-types","types":["aedes broker"]},"retain":true}
27 Dec 20:49:37 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"44fba06ed053541db2a0f8c91467f91e"},"retain":true}
27 Dec 20:59:24 - [trace] utils.writeFile - copied /home/astroberry/.node-red/flows.json TO /home/astroberry/.node-red/.flows.json.backup
27 Dec 20:59:24 - [trace] utils.writeFile - written content to /home/astroberry/.node-red/flows.json.$$$
27 Dec 20:59:24 - [trace] utils.writeFile - renamed /home/astroberry/.node-red/flows.json.$$$ to /home/astroberry/.node-red/flows.json
27 Dec 20:59:24 - [debug] saved flow revision: 94ee9fce362f3ff4306de24c4c921e3e
27 Dec 20:59:24 - [info] Stopping flows
27 Dec 20:59:24 - [info] Stopped flows
27 Dec 20:59:24 - [info] Waiting for missing types to be registered:
27 Dec 20:59:24 - [info] - aedes broker
27 Dec 20:59:24 - [trace] runtime event: {"id":"runtime-state","payload":{"error":"missing-types","type":"warning","text":"notification.warnings.missing-types","types":["aedes broker"]},"retain":true}
27 Dec 20:59:24 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"94ee9fce362f3ff4306de24c4c921e3e"},"retain":true}

```

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [27 December 2021 11:23 UTC](https://discourse.nodered.org/t/missing-node-error-on-deploy-but-its-still-in-palette-manager/55745/2 "2021-12-27T11:23:54Z")

</div>

I would start node-red in safe mode:  
`node-red --safe`  
go to the `Configuration nodes` tab  
 ![Screen Shot 2021-12-27 at 6.22.04 AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/0/00d87457171731e99530ee3d9987e6204f3dbbb9.png)  
and see what is there. If you find a broker, delete it and then do a deploy and see what shows on the log.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [27 December 2021 11:31 UTC](https://discourse.nodered.org/t/missing-node-error-on-deploy-but-its-still-in-palette-manager/55745/3 "2021-12-27T11:31:13Z")

</div>

No need to do what @zenofmud says. The startup log tells us what is happening

> [@Jay1234](#):
>
> ```auto
> 27 Dec 20:48:42 - [warn] [node-red-contrib-aedes/aedes-mqtt-broker] Error: Could not locate the bindings file. Tried:
> â /home/astroberry/.node-red/node_modules/snappy/build/binding.node
> â /home/astroberry/.node-red/node_modules/snappy/build/Debug/binding.node
> â /home/astroberry/.node-red/node_modules/snappy/build/Release/binding.node
> â /home/astroberry/.node-red/node_modules/snappy/out/Debug/binding.node
> â /home/astroberry/.node-red/node_modules/snappy/Debug/binding.node
> â /home/astroberry/.node-red/node_modules/snappy/out/Release/binding.node
> â /home/astroberry/.node-red/node_modules/snappy/Release/binding.node
> â /home/astroberry/.node-red/node_modules/snappy/build/default/binding.node
> â /home/astroberry/.node-red/node_modules/snappy/compiled/14.18.2/linux/arm/binding.node
> 
> ```

The `node-red-contrib-aedes` module is failing to load. This error is usually due to a missing or incompatible binary component of the module.

You can try rebuilding it with:

```auto
cd /home/astroberry/.node-red/
npm rebuild node-red-contrib-aedes

```

---

<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:** [25 February 2022 11:31 UTC](https://discourse.nodered.org/t/missing-node-error-on-deploy-but-its-still-in-palette-manager/55745/4 "2022-02-25T11:31:50Z")

</div>

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