Looks Like I Broken Node-Red Restoring Flows To Different Instance?

Looks like I broken node-red restoring flows to different instance? I backed up the flows on node-red instance A, then restored flows to node-red B. I had already changed the settings.js file to not use hostname as part of the flows* file names. After the restore to B using files from A, the editor web page does not respond, browser can't load it at all. I guess there is something I missed in doing the above?

What does the log say when you start node-red?

Good question...

Also did one more test, back and restore to the same instance, editor did not fail this time, but the backup/restore failed. So I am definitely not doing the backup and restore correctly yet.

Procedural steps, backup and restore on same instance:

  1. As backup, I download the files using pscp on Windows 10 desktop
  2. Changed a simple flow, just one debug node removed
  3. As restore, use pscp on WIndows 10 desktop to upload the files
  4. After restore, I restart node-red
  5. Start editor, this time it did open, unlike when I did the backup A and restore B scenario

Log from above procedure...

27 Jun 15:53:45 - [warn] Projects disabled : editorTheme.projects.enabled=false
27 Jun 15:53:45 - [info] Flows file     : /root/.node-red/flows_pizero5.dachshund-digital.org.json
27 Jun 15:53:45 - [info] Server now running at http://127.0.0.1:1880/
27 Jun 15:53:45 - [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 Jun 15:53:45 - [info] Starting flows
27 Jun 15:53:45 - [info] Started flows
27 Jun 16:01:04 - [info] Stopping flows
27 Jun 16:01:04 - [info] Stopped flows
27 Jun 16:01:04 - [info] Starting flows
27 Jun 16:01:04 - [info] Started flows
27 Jun 16:02:19 - [info] Stopping flows
Stopping Node-RED graphical event wiring tool...
27 Jun 16:02:19 - [info] Stopped flows
nodered.service: Succeeded.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
27 Jun 16:02:35 - [info]
Welcome to Node-RED
===================
27 Jun 16:02:35 - [info] Node-RED version: v1.0.6
27 Jun 16:02:35 - [info] Node.js  version: v12.16.2
27 Jun 16:02:35 - [info] Linux 5.4.47+ arm LE
27 Jun 16:02:44 - [info] Loading palette nodes
27 Jun 16:03:06 - [info] Settings file  : /root/.node-red/settings.js
27 Jun 16:03:06 - [info] Context store  : 'default' [module=memory]
27 Jun 16:03:06 - [info] User directory : /root/.node-red
27 Jun 16:03:06 - [warn] Projects disabled : editorTheme.projects.enabled=false
27 Jun 16:03:06 - [info] Flows file     : /root/.node-red/flows_pizero5.dachshund-digital.org.json
27 Jun 16:03:07 - [info] Server now running at http://127.0.0.1:1880/
27 Jun 16:03:07 - [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 Jun 16:03:07 - [info] Starting flows
27 Jun 16:03:07 - [info] Started flows

The problem is, the flow that was changed, removed the debug node, is not restored as expected. So I have two issues, 1) backup and restore on same node is not working as yet, and 2) backup A and restore to B, is not working, appears to break editor.

Wait... I just noticed the flow file being used on node-red start up is the wrong file, from the wrong directory.

I was about to say that you shouldn't be running as root unless you have a good reason.

Right, I think when I ran the install script to test if the ARM v6 install would move to ARM v7 instruction set, I was under root... which should not have been the case.

Also, I think there may well be other stuff installed using the v6 instruction set. Basically it just isn't a very good idea to mix them.

Thinking same. I was thinking I could use a single base image... and then just upgrade as needed. But... the more I test and validate, the more I think I will need two base images. One for ARM v6 older Pi devices, and another one for ARM v7 based Pi devices.

I am going to deploy node-red via the standard install script, but trigger it via something like ansible or such. Also thinking about using a local git server to deploy the flows to every Pi. I could deploy the flows via ansible as well, but the opportunity to learn how to setup a local git server is significant.

There is nothing to install other than git itself. It is a client and a server. You can use ssh for remote access so if that is setup then nothing more to do.

Nice, thanks for insight. I have used git for years, related to devepment work... but never created a server before from scratch.