Starting as a systemd service.
20 May 11:57:03 - [info]
Welcome to Node-RED
20 May 11:57:03 - [info] Node-RED version: v1.0.6
20 May 11:57:03 - [info] Node.js version: v14.3.0
20 May 11:57:03 - [info] Linux 5.4.0-1008-raspi arm64 LE
20 May 11:57:04 - [info] Loading palette nodes
/bin/sh: 1: /home/ubuntu/.node-red/node_modules/node-red-node-pi-gpio/testgpio.py: not found
20 May 11:57:06 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
20 May 11:57:06 - [warn] ------------------------------------------------------
20 May 11:57:06 - [warn] [node-red-node-serialport/serialport] Error: /snap/core/current/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/ubuntu/.node-red/node_modules/@serialport/bindings/build/Release/bindings.node)
20 May 11:57:06 - [warn] ------------------------------------------------------
20 May 11:57:06 - [info] Settings file : /home/ubuntu/.node-red/settings.js
20 May 11:57:06 - [info] Context store : 'default' [module=memory]
20 May 11:57:06 - [info] User directory : /home/ubuntu/.node-red
Yep, I edited settings.js. I think this node was loading in a previous node-red install - that's why I am wondering whether others are having issues with it or whether maybe my new install (new version too) is screwed up somehow?
Thanks for giving it a try, that's encouraging! I'll see if I can figure out how to downgrade to v12.13.0. Would you mind sharing what you did in the CLI to get successful install - what directory you were in/ what options you specified etc - or was it just npm install node-red-contrib-solace?
It seems to have worked in the CLI for me too - but the node-red web interface isn't happy with something and the nodes don't appear on the palette for use
interesting, on my Pi I get this at startup
Welcome to Node-RED
===================
20 May 09:45:54 - [info] Node-RED version: v1.0.6
20 May 09:45:54 - [info] Node.js version: v12.16.3
20 May 09:45:54 - [info] Linux 4.19.97-v7+ arm LE
20 May 09:45:55 - [info] Loading palette nodes
20 May 09:45:57 - [info] Dashboard version 2.22.1 started at /ui
20 May 09:45:58 - [warn] ------------------------------------------------------
20 May 09:45:58 - [warn] [node-red-contrib-solace/solace] Error: Cannot find module '/usr/lib/node_modules/node-red/red/red'
Require stack:
- /home/pi/.node-red/node_modules/node-red-contrib-solace/solace/lib/solaceConnectionPool.js
- /home/pi/.node-red/node_modules/node-red-contrib-solace/solace/solace.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/loader.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/index.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/index.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/index.js
- /usr/lib/node_modules/node-red/lib/red.js
- /usr/lib/node_modules/node-red/red.js
20 May 09:45:58 - [warn] ------------------------------------------------------
On my mac I'm running
Welcome to Node-RED
===================
20 May 13:46:37 - [info] Node-RED version: v1.0.6
20 May 13:46:37 - [info] Node.js version: v12.13.0
20 May 13:46:37 - [info] Darwin 18.7.0 x64 LE
20 May 13:46:38 - [info] Loading palette nodes
20 May 13:46:41 - [info] Worldmap version 2.3.10
20 May 13:46:41 - [info] Dashboard version 2.22.1 started at /ui
the big clue is Error: Cannot find module '/usr/lib/node_modules/node-red/red/red' on the pi.
// get the global settings so we can check log level for solace
var settings = require(process.env.NODE_RED_HOME+"/red/red").settings;
Interestingly, the log level is something you are instructed to set in the settings.js file specified in installation docs. I'm going to see what happens if I edit to hard code the path to that file