Addons not starting

Configuration
40

Same issue after restoring from backup to new SD card. Deleting home-assistant_v2.db did not work for me. Deleted file, restarted, same issue with add-ons starting but not available from the interface.

Additional troubleshooting:


Home Assistant 2022.8.5
Supervisor 2022.08.3
Operating System 8.4
Frontend 20220802.0 - latest

For further troubleshooting, I un-installed NodeRed addon and reinstalled from Add on Store. To be clear, all add-ons are having same issue, but I chose one to document here.

Log file suggests that it is running normally.

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 13.3.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.4  (aarch64 / raspberrypi3-64)
 Home Assistant Core: 2022.8.5
 Home Assistant Supervisor: 2022.08.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/customizations.sh
cont-init: info: /etc/cont-init.d/customizations.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/node-red.sh
patching file nodes/ui_base.html
Hunk #1 succeeded at 1164 (offset 633 lines).
up to date, audited 86 packages in 6s
5 packages are looking for funding
  run `npm fund` for details
7 vulnerabilities (1 low, 1 moderate, 1 high, 4 critical)
To address issues that do not require attention, run:
  npm audit fix
To address all issues (including breaking changes), run:
  npm audit fix --force
Run `npm audit` for details.
cont-init: info: /etc/cont-init.d/node-red.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun nodered (no readiness notification)
s6-rc: info: service legacy-services successfully started
[13:40:21] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
16 Aug 13:40:29 - [info] 
Welcome to Node-RED
===================
16 Aug 13:40:29 - [info] Node-RED version: v3.0.2
16 Aug 13:40:29 - [info] Node.js  version: v16.16.0
16 Aug 13:40:29 - [info] Linux 5.15.32-v8 arm64 LE
16 Aug 13:40:32 - [info] Loading palette nodes
16 Aug 13:40:53 - [info] Dashboard version 3.1.7 started at /endpoint/ui
16 Aug 13:40:57 - [info] Settings file  : /etc/node-red/config.js
16 Aug 13:40:57 - [info] Context store  : 'default' [module=memory]
16 Aug 13:40:57 - [info] User directory : /config/node-red/
16 Aug 13:40:57 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 Aug 13:40:57 - [info] Flows file     : /config/node-red/flows.json
16 Aug 13:40:57 - [info] Server now running at http://127.0.0.1:46836/
16 Aug 13:41:03 - [info] [server:Home Assistant] Connecting to http://supervisor/core
16 Aug 13:41:03 - [info] [server:Home Assistant] Connected to http://supervisor/core

When I go to Settings->Add-ons, the Node-RED add-on is gray in color. When I click on the sidebar icon to access the flows UI, I get the message: “Add-on is not running. Please start it first.”

Screen Shot 2022-08-16 at 1.33.12 PM

‘ha addons’ command shows the state as “unknown”:

- advanced: false
  available: true
  build: false
  description: Flow-based programming for the Internet of Things
  detached: false
  homeassistant: 2021.3.0
  icon: true
  logo: true
  name: Node-RED
  repository: a0d7b954
  slug: a0d7b954_nodered
  stage: stable
  state: unknown
  update_available: false
  url: https://github.com/hassio-addons/addon-node-red
  version: 13.3.1
  version_latest: 13.3.1

I would appreciate any other ideas about what is going on.

1 Like
41

For me, the solution was indeed to delete the DB file. I managed to do this by adding a screen to my NUC and deleting the file over the cmd line.

42

Hi all,
I’ve the same problem after restoring from backup, but I’m not able to delete the v2.db because Terminal & ssh is not working. Do you have any ideas?

1 Like
43

Tried it - nothing happened.
Did you directly restart after? Or could you just start them after deleting the file?

44

Hi everyone. I see this issue is marked as solved, but I have the same issue after restoring from backup: my addons are running (no errors in the log) but their web-UI interfaces are inaccessible and i’m prompted to start the (running) addons.
Deleting the v2.db file did nothing. Does anyone have any other ideas?

3 Likes
45

Finally working for me.

I first deleted the v2.db and restarted HA but that didn’t work or at least was not sufficient.

Then the day after I coincidentally figured out that after I completely shutdown the HA (Settings > System > Hardware > press three dots > shutdown Hardware), unplug power cable and back in after some seconds to trigger the HA to boot up again. Now I had to login again and the new add-ons were all working.

The difference with the regular reboot is that I had to login again which was not the for a reboot as it then goes automatically to the main page of HA.

Before deleting the v2.db I think it’s worth to first try the shutdown procedure above as I don’t know exactly what was the trigger to have it working. Maybe a simple log out/in is already sufficient!

63 Likes
46

Yeah I did a full restart directly afterwards.

2 Likes
47

Yes, now working fine also for me.
Thank you!

1 Like
48

Your solution works fine for me. No need to remove v2.db :slight_smile:
Thanks.

2 Likes
49

Yes! Thx.
Your solution works fine for me as well.
No need to remove v2.db also.

1 Like
51

Good news: a power cycle reboot solved it.
Bad news: I have pattern baldness from pulling clumps of my hair out.

THANK YOU !!!

2 Likes
52

Same here. Turning off and on solve problem.
Thanks!

53

Yes, it worked. But you lose all your historical data like energy consuption. Not a good solution for me.

54

This solution worked for me also. The deletion of the whole database is not a good solution.

55

The deletion of the database was never a solution.

56

That is the trick :heart_eyes:

57

thanks, it works

58

Had to do full reboot as well. Simple logout procedure didn’t work!

Bad timing on my end - was upgrading to NUC now and all went to s…t.

Thank you for that!

59

Went through the same nightmare just now after a full restore on my Rpi4. A full restart (System–> Hardware → three dots up right → Restart Host) did the trick for me too know. While I see how that should be good practice anyway, it should just be included in the process of running a full restore HA-wise.

4 Likes
60

Thanks for this solution. Worked for me as well. Without deleting the DB.

And I also plugged out a couple of hair before everything back on track.

Alexandre