I turned on another RPI and decided to get it up to date.
The flows are were worked.
The only thing I updated was the dashboard.
After that I saw this error:
(All nodes listed are/were installed before the update)
As always, you need to show any errors from the Node-RED log.
Also, if the device has been off for a while, take a copy of your userDir folder and then update the device both with OS updates and npm package updates (don't forget to do both global and local updates for npm).
From the command line, you can find out what is out of date in node.js using the two commands (run from your userDir):
npm -g outdated
npm outdated
Yeah, ok.
But it wasn't a HUGE update. Not like the machine has been offline for 2 years and I am updating from dashboard 0.1.1 to current.
Maybe one step up. Two at most.
The log.
Well, this is what is shows, but I think it is all recent stuff after I installed the nodes needed.
Sorry, maybe I shouldn't have installed them. But they were (previously) installed before the update to the dashboard
pi@PIFACE:~ $ cd .node-red
pi@PIFACE:~/.node-red $ node-red-log
17 Sep 19:23:35 - [info] - node-red-contrib-ring-buffer:ring-buffer
17 Sep 19:23:35 - [info] Installing module: node-red-contrib-play-audio-file, version: 0.0.1
17 Sep 19:24:17 - [info] Installed module: node-red-contrib-play-audio-file
17 Sep 19:24:17 - [info] Missing type registered: play_audio_file
17 Sep 19:24:17 - [info] Added node types:
17 Sep 19:24:17 - [info] - node-red-contrib-play-audio-file:play_audio_file
17 Sep 19:27:34 - [info] Installing module: node-red-contrib-traffic, version: 0.2.1
17 Sep 19:28:15 - [info] Installed module: node-red-contrib-traffic
17 Sep 19:28:15 - [info] Missing type registered: traffic
17 Sep 19:28:15 - [info] Starting flows
17 Sep 19:28:17 - [info] Started flows
17 Sep 19:28:17 - [info] [mqtt-broker:281932a8.0517e6] Connected to broker: mqtt://192.168.0.99:1883
17 Sep 19:28:17 - [info] Added node types:
17 Sep 19:28:17 - [info] - node-red-contrib-traffic:traffic
17 Sep 19:28:17 - [info] [mqtt-broker:MQTT Host] Connected to broker: mqtt://192.168.0.99:1883
17 Sep 19:28:17 - [info] [mqtt-broker:e460b810.44b73] Connected to broker: mqtt://192.168.0.99:1883
17 Sep 19:28:17 - [info] [mqtt-broker:1c87feec.e99579] Connected to broker: mqtt://192.168.0.99:1883
17 Sep 19:28:17 - [info] [mqtt-broker:aa47173d.e66d2] Connected to broker: mqtt://192.168.0.99:1883
17 Sep 19:28:17 - [info] [mqtt-broker:644eec43.552964] Connected to broker: mqtt://192.168.0.99:1883
17 Sep 19:28:17 - [info] [mqtt-broker:9cb189d9.99c908] Connected to broker: mqtt://192.168.0.99:1883
17 Sep 19:28:17 - [info] [mqtt-broker:MQTT host] Connected to broker: mqtt://192.168.0.99:1883
17 Sep 19:28:39 - [info] Stopping modified nodes
17 Sep 19:28:39 - [info] Stopped modified nodes
17 Sep 19:28:39 - [info] Starting modified nodes
17 Sep 19:28:39 - [info] Started modified nodes
^Cpi@PIFACE:~/.node-red $
With respect to the latter part:
pi@PIFACE:~/.node-red $ npm -g outdated
npm ERR! Cannot read property 'length' of undefined
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2019-09-17T09_32_53_421Z-debug.log
pi@PIFACE:~/.node-red $
I won't do the last one as I think there is a problem before that.
Hang on. I'll look at the log.
pi@PIFACE:~/.node-red $ cd ..
pi@PIFACE:~ $ cd .npm
pi@PIFACE:~/.npm $ cd _logs
pi@PIFACE:~/.npm/_logs $ lf
2019-09-17T09_32_53_421Z-debug.log
pi@PIFACE:~/.npm/_logs $ ll
total 4
-rw-r--r-- 1 pi pi 2294 Sep 17 19:32 2019-09-17T09_32_53_421Z-debug.log
pi@PIFACE:~/.npm/_logs $ cat 2019-09-17T09_32_53_421Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', '-g', 'outdated' ]
2 info using npm@6.9.0
3 info using node@v10.16.3
4 verbose npm-session 0f5184889d89fb3a
5 http fetch GET 200 https://registry.npmjs.org/npm 1017ms
6 silly pacote registry packument for npm@^6.9.0 fetched in 1289ms
7 http fetch GET 200 https://registry.npmjs.org/node-red 1421ms
8 silly pacote registry packument for node-red@^0.20.7 fetched in 1565ms
9 verbose stack TypeError: Cannot read property 'length' of undefined
9 verbose stack at dotindex (/usr/lib/node_modules/npm/node_modules/text-table/index.js:59:32)
9 verbose stack at /usr/lib/node_modules/npm/node_modules/text-table/index.js:11:21
9 verbose stack at Array.forEach (<anonymous>)
9 verbose stack at forEach (/usr/lib/node_modules/npm/node_modules/text-table/index.js:73:31)
9 verbose stack at /usr/lib/node_modules/npm/node_modules/text-table/index.js:10:9
9 verbose stack at Array.reduce (<anonymous>)
9 verbose stack at reduce (/usr/lib/node_modules/npm/node_modules/text-table/index.js:63:30)
9 verbose stack at module.exports (/usr/lib/node_modules/npm/node_modules/text-table/index.js:9:20)
9 verbose stack at /usr/lib/node_modules/npm/lib/outdated.js:130:16
9 verbose stack at cb (/usr/lib/node_modules/npm/node_modules/slide/lib/async-map.js:47:24)
9 verbose stack at doIt (/usr/lib/node_modules/npm/lib/outdated.js:381:14)
9 verbose stack at updateDeps (/usr/lib/node_modules/npm/lib/outdated.js:443:9)
9 verbose stack at tryCatcher (/usr/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
9 verbose stack at Promise.successAdapter [as _fulfillmentHandler0] (/usr/lib/node_modules/npm/node_modules/bluebird/js/release/nodeify.js:23:30)
9 verbose stack at Promise._settlePromise (/usr/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:566:21)
9 verbose stack at Promise._settlePromise0 (/usr/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
10 verbose cwd /home/pi/.node-red
11 verbose Linux 4.9.35-v7+
12 verbose argv "/usr/bin/node" "/usr/bin/npm" "-g" "outdated"
13 verbose node v10.16.3
14 verbose npm v6.9.0
15 error Cannot read property 'length' of undefined
16 verbose exit [ 1, true ]
pi@PIFACE:~/.npm/_logs $
I'll start looking too.
