addon not started according to supervisor, although it does seem to start?

[R5fan]

This is a relatively fresh installation for a friend. I added node red, configured the credentials, and started it. The logs seem ok:

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: 14.0.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.3  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2022.12.7
 Home Assistant Supervisor: 2022.11.2
-----------------------------------------------------------
 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
patching file nodes/ui_base.html
Hunk #1 succeeded at 1164 (offset 633 lines).
s6-rc: info: service init-nginx successfully started
up to date, audited 1 package in 340ms
found 0 vulnerabilities
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered 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
[11:52:19] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
22 Dec 11:52:24 - [info] 
Welcome to Node-RED
===================
22 Dec 11:52:24 - [info] Node-RED version: v3.0.2
22 Dec 11:52:24 - [info] Node.js  version: v18.12.1
22 Dec 11:52:24 - [info] Linux 5.15.61-v8 arm64 LE
22 Dec 11:52:26 - [info] Loading palette nodes
22 Dec 11:52:31 - [info] Dashboard version 3.2.3 started at /endpoint/ui
22 Dec 11:52:32 - [info] Settings file  : /etc/node-red/config.js
22 Dec 11:52:32 - [info] Context store  : 'default' [module=memory]
22 Dec 11:52:32 - [info] User directory : /config/node-red/
22 Dec 11:52:32 - [warn] Projects disabled : editorTheme.projects.enabled=false
22 Dec 11:52:32 - [info] Flows file     : /config/node-red/flows.json
22 Dec 11:52:32 - [warn] Encrypted credentials not found
22 Dec 11:52:32 - [info] Server now running at http://127.0.0.1:46836/
22 Dec 11:52:32 - [info] Starting flows
22 Dec 11:52:32 - [info] Started flows
[11:52:33] INFO: Starting NGinx...
22 Dec 11:52:37 - [info] [server:Home Assistant] Connecting to http://supervisor/core
22 Dec 11:52:37 - [info] [server:Home Assistant] Connected to http://supervisor/core

But supervisor doesnt seem to think its running:

Pressing start again does nothing. When i try to access the web UI via the side bar

I am accessing the machine remotely, but that shouldnt matter or?

[frenck]

This is an issue with the Home Assistant Supervisor. Reboot your system (not just restart, full reboot cycle) to fix it.

This is not something the add-on can do anything about. Please report is to the Supervisor project.

../Frenck