No logs = no issue.
Hi Nick, which log would you like to see? In my last comment I put the add-on log but that just says that the service is started. I just started with Home-assistant so not so familiar with the logs yet.
1 Like
Try supervisor log home assistant core log.
I can’t believe the log is only 3 lines.
I just reproduced the problem to fetch the supervisor log:
-
In sidebar I press the “Backups” button to open the add-on “Home Assistant Google Drive Backup”. I get right away a popup with the message “Add-on is not running. Please start it first”
-
Then I go to Settings > Add-ons > “Home Assistant Google Drive Backup” and press “Start”.
-
When I try to open the add-on in the sidebar again I get the same message that the service is not running and I need to start it.
Supervisor log gives after pressing Start:
22-08-16 14:35:33 WARNING (MainThread) [supervisor.addons.addon] cebe7a76_hassio_google_drive_backup is already running!
The supervisor log shows that the service was running already as I saw the following lines before I pressed the Start button:
22-08-16 14:29:17 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
22-08-16 14:29:17 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
@nickrout this is the full log since I installed the add-on yesterday. Looks like underwater it’s running as it should be but it’s the GUI that is not in sync:
08-15 23:22:57 INFO Starting server on port 8099
08-15 23:22:57 INFO Server started
08-15 23:22:57 INFO Syncing Backups
08-16 00:22:57 INFO Syncing Backups
08-16 01:22:58 INFO Syncing Backups
08-16 02:22:58 INFO Syncing Backups
08-16 03:22:58 INFO Syncing Backups
08-16 04:22:58 INFO Syncing Backups
08-16 05:22:58 INFO Syncing Backups
08-16 06:22:58 INFO Syncing Backups
08-16 07:22:59 INFO Syncing Backups
08-16 08:22:59 INFO Syncing Backups
08-16 09:22:59 INFO Syncing Backups
08-16 09:29:15 INFO Backup directory changed
08-16 09:29:15 INFO Syncing Backups
08-16 10:29:16 INFO Syncing Backups
08-16 11:29:16 INFO Syncing Backups
08-16 12:29:16 INFO Syncing Backups
08-16 13:29:17 INFO Syncing Backups
08-16 14:29:17 INFO Syncing Backups
I have the same problem.
HA stopped working out of nowhere and I had to restore a backup (12h old).
The UI of the addons won’t start - the services itself are running, HA just does not know it. For example: Node-Red is running, with all the flows - I can access the http-interface through a browser. The partial restore also did nothing for me - I still can’t start the UI from HA.
Hey Guys,
I don’t know what’s happened here. I pushed an update for 2022.8.5 and Frigate has disappeared. In addition to this, none of my addons are working. They refuse to start. To top it off, my last full backup on Google Drive has been wiped so I have to start from further behind to some extent. File editor is not working, SHA Web Terminal is not working…Someone PLEASE HELP!
Check your github repository. Is github repository in addon store? If isn’t add it again.
Can you post your supervisor log?
Same exact issue after reimaging HAS onto a different device. Deleting home-assistant_v2.db was the solution. Many thanks!
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.”
‘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
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.
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
Tried it - nothing happened.
Did you directly restart after? Or could you just start them after deleting the file?
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
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!
62 Likes
Yeah I did a full restart directly afterwards.
2 Likes
Yes, now working fine also for me.
Thank you!
1 Like
Your solution works fine for me. No need to remove v2.db 
Thanks.
2 Likes
Yes! Thx.
Your solution works fine for me as well.
No need to remove v2.db also.
1 Like
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