Bepacom-Raalte / Bepacom-BACnet-IP-Integration

Bepacom BACnet Integration Repository
Apache License 2.0
12 stars 2 forks source link

/run/s6/basedir/scripts/rc.init: s6-rc failed to properly bring all the services up! #28

Closed jamel-86 closed 1 day ago

jamel-86 commented 2 weeks ago

This happens when I try to start the Add-on for the first time, I have also tried to re-install the addon without success:

System: Raspberry PI 4 8GB Core: 2024.6.3 Supervisor: 2024.06.0 Operating System: 12.1 Frontend: 20240610.1

HA log:

Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:135
integration: Home Assistant Supervisor (documentation, issues)
First occurred: 9:48:32 AM (1 occurrences)
Last logged: 9:48:32 AM

Failed to to call /addons/dca55f82_bacnetinterface/stats - Container addon_dca55f82_bacnetinterface is not running

Addon Log:

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: Bepacom BACnet/IP Interface Development Version
 Bepacom BACnet/IP interface for the Bepacom EcoPanel. Allows BACnet/IP devices to be available to Home Assistant through an API
-----------------------------------------------------------
 Add-on version: 1.4.1b8
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.1  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.6.3
 Home Assistant Supervisor: 2024.06.0
-----------------------------------------------------------
 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-interface: starting
[09:52:07] INFO: Running init-interface.
[09:52:07] INFO: Running init-nginx.
[09:52:07] INFO: Allowed addresses for NGINX: 127.0.0.1 192.168.50.220 172.30.232.1 172.30.32.1
/etc/s6-overlay/s6-rc.d/init-interface/run: line 58: ipaddr: unbound variable
s6-rc: warning: unable to start service init-interface: command exited 1
[09:52:08] INFO: Generated ingress configuration successfully!
s6-rc: info: service init-nginx successfully started
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service init-nginx: stopping
s6-rc: info: service init-nginx 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
GravySeal commented 1 day ago

Hello, this is an issue with the add-on. This repository is for the integration side of things, so preferably report the issues for the add-on there. This issue has been reported in the add-on repository as well The problem should be solved in the latest dev version, however. A workaround would be to manually fill in the ip address to get the add-on to work.