Lost Basic-Pallete Nodes

#1

Greetings

I have 'lost' a number of basic nodes from the initial NR install set, all related to http-request etc. I do have backups and can reinstall, but that won't help me to learn either the source of the problem or methodology to cure.

If I go to manage the palette, the basic node-red node (0.20.2) shows a red error triangle and the term "[object Object]". Looking at the list of individual nodes within the group shows a number that have 'marching ants' around their symbol; all of these are missing from the general node-red palette. Most are related to HTTP Requests but also MQTT Broker.

Any hints would be gratefully received.

Tom

#2

Did you follow the upgrade procedure as described in:
https://nodered.org/docs/getting-started/upgrading

#3

Hi Colin

Yes. Initially I had a wider issue with NR. Running the re-istallation process (on a Rpi) got me back up and running, albeit with the missing nodes issue.

#4

Did you use the bash <(curl script?

Show us the output you get from

node-red-stop
node-red

Copy/paste it rather than screenshot if possible please

#5

Thanks Colin... Start and Stop outputs follow....

pi@Burrow : ~/.node-red $ node-red-stop

Stop Node-RED

Use node-red-start to start Node-RED again

pi@Burrow : ~/.node-red $

pi@Burrow : ~/.node-red $ node-red

17 Mar 18:57:40 - [info]

Welcome to Node-RED

===================

17 Mar 18:57:40 - [info] Node-RED version: v0.20.2

17 Mar 18:57:40 - [info] Node.js version: v8.11.1

17 Mar 18:57:40 - [info] Linux 4.14.98-v7+ arm LE

17 Mar 18:57:43 - [info] Loading palette nodes

17 Mar 18:57:53 - [info] Dashboard version 2.9.8 started at /ui

17 Mar 18:57:53 - [warn] ------------------------------------------------------

17 Mar 18:57:53 - [warn] [node-red/httpin] SyntaxError: Invalid or unexpected token

17 Mar 18:57:53 - [warn] [node-red-node-feedparser/feedparse] SyntaxError: Invalid or unexpected token

17 Mar 18:57:53 - [warn] [node-red-node-twitter/twitter] SyntaxError: Invalid or unexpected token

17 Mar 18:57:53 - [warn] [node-red-contrib-sqldbs/sqldbs] SyntaxError: Invalid or unexpected token

17 Mar 18:57:53 - [warn] [node-red-node-twilio/twilio] SyntaxError: Invalid or unexpected token

17 Mar 18:57:53 - [warn] [node-red-contrib-http-request/www-request] SyntaxError: Invalid or unexpected token

17 Mar 18:57:53 - [warn] ------------------------------------------------------

17 Mar 18:57:53 - [info] Settings file : /home/pi/.node-red/settings.js

17 Mar 18:57:53 - [info] HTTP Static : /home/pi/.node-red/public

17 Mar 18:57:53 - [info] Context store : 'default' [module=memory]

17 Mar 18:57:53 - [info] User directory : /home/pi/.node-red

17 Mar 18:57:53 - [warn] Projects disabled : editorTheme.projects.enabled=false

17 Mar 18:57:53 - [info] Flows file : /home/pi/.node-red/flows.json

17 Mar 18:57:54 - [info] Server now running at http://127.0.0.1:1880/

17 Mar 18:57:54 - [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.


17 Mar 18:57:54 - [info] Starting flows

17 Mar 18:57:56 - [info] Started flows

17 Mar 18:57:56 - [info] [mqtt-broker:74c316c3.026408] Connected to broker: mqtt://192.168.1.11:1883

17 Mar 18:57:56 - [info] [mqtt-broker:dada5f69.223af] Connected to broker: mqtt://192.168.1.11:1883

17 Mar 18:57:56 - [info] [mqtt-broker:50f5ed4f.6d0c74] Connected to broker: mqtt://192.168.1.11:1883

17 Mar 18:57:56 - [info] [mqtt-broker:e5246d28.e8b65] Connected to broker: mqtt://192.168.1.11:1883

17 Mar 18:57:56 - [info] [lifx:Tiffany LIFX ON] New bulb found: Tiffany : d073d524dc9a

17 Mar 18:57:56 - [info] [lifx:Tiffany LIFX OFF] New bulb found: Tiffany : d073d524dc9a

^C17 Mar 18:58:42 - [info] Stopping flows

#6

At the command line can you run
npm -v
And report which version it says ?

#7

dceejay, it's 6.4.1

Thanks