Node Red will not boot after updating to v 1.2.5

Last night I updated two Windows 10 PC to Node Red version 1.2.5. This morning, I tried to boot node red and it will not complete the process. The startup begins normally until the "Starting flows" routine begins. From then on, I get a continuous flow of error messages that does not stop indicating that none of the flows can be detected. This same condition exists on both Windows 10 PC. Prior to this update, Node Red started up correctly and all flows were present.

I would appreciate any suggestions on how to correct this problem.
Regards, Bob W.

Post a text copy of your terminal (from the first message after launching node-red until a few errors have passed (use the Pause button or CTRL+C to stop the flow of constant messages)

PS, Node-red 1.2.6 has just been released (like 10min ago) - perhaps you might want to try upgrading once more before digging further?

Thanks, Steve. I will try upgrading to 1.2.6 If nothing changes, I will post the data from the terminal.
Bob W.

Just tried upgrading to V 1.2.6 and I also reloaded nodejs v 12.18.4 and results are the same. Here is a partial terminal dump

Welcome to Node-RED

25 Nov 16:37:22 - [info] Node-RED version: v1.2.6
25 Nov 16:37:22 - [info] Node.js version: v14.15.1
25 Nov 16:37:22 - [info] Windows_NT 10.0.19042 x64 LE
25 Nov 16:37:25 - [info] Loading palette nodes
25 Nov 16:37:34 - [info] Dashboard version 2.23.4 started at /ui
25 Nov 16:37:37 - [info] Settings file : \Users\kn4hh.node-red\settings.js
25 Nov 16:37:37 - [info] Context store : 'default' [module=memory]
25 Nov 16:37:37 - [info] User directory : \Users\kn4hh.node-red
25 Nov 16:37:37 - [warn] Projects disabled : editorTheme.projects.enabled=false
25 Nov 16:37:37 - [info] Flows file : \Users\kn4hh.node-red\flows_KN4HH-FLEX-RADIO.json
25 Nov 16:37:37 - [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.

25 Nov 16:37:37 - [info] Starting flows
25 Nov 16:37:37 - [info] Started flows
25 Nov 16:37:37 - [info] [udp in:64b3a52.78ace5c] udp listener at 0.0.0.0:4996
25 Nov 16:37:37 - [info] Server now running at http://127.0.0.1:1880/
25 Nov 16:37:37 - [error] [function:35ed2a47.bffeee] TypeError: Cannot read property 'substr' of undefined
25 Nov 16:37:38 - [error] [function:35ed2a47.bffeee] TypeError: Cannot read property 'substr' of undefined
25 Nov 16:37:38 - [error] [function:35ed2a47.bffeee] TypeError: Cannot read property 'substr' of undefined
25 Nov 16:37:38 - [error] [http request:GetSPEINFO] Error: Invalid URI "http:///SPEAMP/INFO"

Thanks for having a look.

Bob W.

So these are just something in your flow. If i was to guess, you have an inject set to repeat firing a function node with some misconfiguration / bug

OR worse, you have created a loop that is running node-red to crash point.



Your editor is running - http://127.0.0.1:1880/ - open it up

If the editor is un-responsive (or node-red is crashing) then start node-red in safe mode
node-red --safe

Use the search (CTRL+F) and find 35ed2a47.bffeee or substr

then fix your flow & deploy.

Thank you, Steve. I booted up in safe mode and had access to the workspace. I then redeployed the flow that was incorrect and loaded Dashboard. I was then able to normally load Node Red. All seems to be fine now.

I very much appreciate the assistance.

Regards,
Bob W.

Steve-Mcl
25 November

BobW:

[error] [function:35ed2a47.bffeee] TypeError: Cannot read property 'substr' of undefined

So these are just something in your flow. If i was to guess, you have an inject set to repeat firing a function node with some misconfiguration / bug

OR worse, you have created a loop that is running node-red to crash point.

Your editor is running - http://127.0.0.1:1880/ - open it up

BobW:

25 Nov 16:37:37 - [info] Server now running at http://127.0.0.1:1880/

If the editor is un-responsive (or node-red is crashing) then start node-red in safe mode
node-red --safe

Use the search (CTRL+F) and find 35ed2a47.bffeee or substr

then fix your flow & deploy.

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