Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No config file anymore after upgrading from 15.x to 16.0 #1735

Closed
dersch81 opened this issue Nov 15, 2023 · 24 comments
Closed

No config file anymore after upgrading from 15.x to 16.0 #1735

dersch81 opened this issue Nov 15, 2023 · 24 comments

Comments

@dersch81
Copy link

`s6-rc: info: service legacy-services successfully started

start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

Error loading settings file: /etc/node-red/config.js`

@frenck
Copy link
Member

frenck commented Nov 15, 2023

Is there more information in the logs?

@dersch81
Copy link
Author

dersch81 commented Nov 15, 2023

I cutted the error part:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

-----------------------------------------------------------
 Add-on: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 15.1.1
 There is an update available for this add-on!
 Latest add-on version: 16.0.0
 Please consider upgrading as soon as possible.
 System: Home Assistant OS 11.1  (amd64 / qemux86-64)
 Home Assistant Core: 2023.11.2
 Home Assistant Supervisor: 2023.11.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
[11:44:49] INFO: Starting Node-RED...
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

Error loading settings file: /etc/node-red/config.js
[11:44:50] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[11:44:50] INFO: Service NGINX exited with code 256 (by signal 15)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

@DieMetRik
Copy link

After update disappearing all flows

/usr/share/hassio/addons/data/a0d7b954_nodered is empty
/usr/share/hassio/addon_configs/a0d7b954_nodered with my flows?

@antro31
Copy link

antro31 commented Nov 15, 2023

Same for me.
All flows disappeared. Reverted back to previous version (+ had to restore backup of the configuration since data were lost also)

@dersch81
Copy link
Author

dersch81 commented Nov 15, 2023

Seems restarting missed the new version in my log upwards, here is the actual one:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

-----------------------------------------------------------
 Add-on: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 16.0.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.1  (amd64 / qemux86-64)
 Home Assistant Core: 2023.11.2
 Home Assistant Supervisor: 2023.11.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
[11:56:40] INFO: Starting Node-RED...
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

15 Nov 11:56:42 - [info] 

Welcome to Node-RED
===================

15 Nov 11:56:42 - [info] Node-RED version: v3.1.0
15 Nov 11:56:42 - [info] Node.js  version: v18.18.2
15 Nov 11:56:42 - [info] Linux 6.1.59 x64 LE
15 Nov 11:56:42 - [info] Loading palette nodes
15 Nov 11:56:44 - [info] Dashboard version 3.6.1 started at /endpoint/ui
15 Nov 11:56:45 - [info] Settings file  : /etc/node-red/config.js
15 Nov 11:56:45 - [info] Context store  : 'default' [module=memory]
15 Nov 11:56:45 - [info] User directory : /config/
15 Nov 11:56:45 - [warn] Projects disabled : editorTheme.projects.enabled=false
15 Nov 11:56:45 - [info] Flows file     : /config/flows.json
15 Nov 11:56: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.
---------------------------------------------------------------------

15 Nov 11:56:45 - [info] Server now running at http://127.0.0.1:46836/
15 Nov 11:56:45 - [warn] Encrypted credentials not found
15 Nov 11:56:45 - [info] Starting flows
15 Nov 11:56:45 - [info] Started flows
[11:56:45] INFO: Starting NGinx...
15 Nov 11:56:50 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 11:56:50 - [info] [server:Home Assistant] Connected to http://supervisor/core`

@frenck
Copy link
Member

frenck commented Nov 15, 2023

@dersch81 That is a duplicate of #1733, which is fixed by #1734, released in v16.0.1

@frenck frenck closed this as completed Nov 15, 2023
@Bloodpack
Copy link

Same here,

update from 15.x to 16.0, all flows gone....
restored nodered backup, addon not starting, all flows gone.......

@antro31
Copy link

antro31 commented Nov 15, 2023

@Bloodpack : You should also restore the configuration. (/homeassistant/node-red folder)

@dersch81
Copy link
Author

@dersch81 That is a duplicate of #1733, which is fixed by #1734, released in v16.0.1

It has been started now with 16.0 but all flows are gone

@antro31
Copy link

antro31 commented Nov 15, 2023

Migrated to 16.0.1 from 15.5.1... All flows are gone !
Looks like migration creates a new .flows.json because .flows.json.backup seems to contain all the needed data

@dersch81
Copy link
Author

can we reopen this? It is not solved

@frenck
Copy link
Member

frenck commented Nov 15, 2023

It is solved, restore a backup (don't forget to restore an HA backup, as that contains the flows), migrate from v15 -> v16.0.1 directly.

@antro31
Copy link

antro31 commented Nov 15, 2023

@frenck : Migrating from 15 -> 16.0.1 did not work for me. node-red restarted with an empty flow.

@wokkeltje13
Copy link

same for me, 16.0.1 removed the flows again

@dersch81
Copy link
Author

It is solved, restore a backup (don't forget to restore an HA backup, as that contains the flows), migrate from v15 -> v16.0.1 directly.

doing a proxmox VM restore now (from 15.11.23 02:00) because my last core backup is from upgrading 11.0 > 11.1 from last week

@nivek1612
Copy link

same for me, 16.0.1 removed the flows again

And for me

@sdavides
Copy link

same for me, update 👎

@dersch81
Copy link
Author

VM Restore done. But i'm afraid to do the 16.0.1 upgrade now. Seems it is not solved

@sdavides
Copy link

sdavides commented Nov 15, 2023

Solved
from backup "/config/nodered/flow.json"
import flow.json
deploy

After restart flow delete 👎

@Dsna1R
Copy link

Dsna1R commented Nov 15, 2023

I had to restore a full backup to recover my flows. 16.0.1 does not solve the problem either. I'm staying on 15.1.1 for now.

@MarcoL1975
Copy link

Updated to 16.0.1 and took my flows.json from my last HA backup from last week.... looks like it's working now

@nivek1612
Copy link

Updated to 16.0.1 and took my flows.json from my last HA backup from last week.... looks like it's working now

Good to know but I would have hoped an update coped with this without the need to do backups/restore of flows. I'll stay on 15.1.1 for now

@nivek1612
Copy link

This worked for me
But I always take a full HA backup before any changes, that backup when fully restored will correct the directory changes which I think is the issue with 16.0.0 and 16.0.1

Restore complete full HA backup taken before any upgrade to 16.0.x (overwrite everything)
Install 16.0.2
All works

@frenck
Copy link
Member

frenck commented Nov 15, 2023

Please see #1736

@hassio-addons hassio-addons locked as off-topic and limited conversation to collaborators Nov 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants