Good morning,
I had a power outage a few days ago and since getting things back up and running i’ve noticed a strange issue whereby my TasmotaAdmin add-on fails to start. I’m not sure if it’s related to the power outage or if something else has caused the problem.
The behaviour I witness is that when starting the add-on via the UI the Start button spins for a while and then just goes back to ‘Start’.
Log files don’t yield much info:
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: TasmoAdmin
Centrally manage all your Sonoff-Tasmota devices
-----------------------------------------------------------
Add-on version: 0.25.0
You are running the latest version of this add-on.
System: Home Assistant OS 10.5 (amd64 / qemux86-64)
Home Assistant Core: 2023.7.3
Home Assistant Supervisor: 2023.08.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
Log level is set to DEBUG
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-tasmoadmin: starting
s6-rc: info: service init-nginx: starting
[10:27:38] DEBUG: Data directory not initialized, doing that now...
[10:27:38] DEBUG: Symlinking data directory to persistent storage location...
s6-rc: info: service init-tasmoadmin successfully started
s6-rc: info: service php-fpm: starting
s6-rc: info: service php-fpm successfully started
[10:27:38] INFO: Starting PHP-FPM server...
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
[10:27:39] INFO: Starting NGINX server...
However, using the command docker ps -a and then inspecting the container used for the add-on I can see it’s in an unhealthy state. It keeps logging the following out:
Does anyone know what might be causing this? I’ve tried the usual solutions like fully removing and then reinstalling the add-on but to no avail.
Thanks
Pete
