InfluxDB fails to start after installation

When trying to start influxdb for the first time afer installing it, it stops after the line “INFO: Starting NGINX…” stops in the sense that nothing happens (waiting for 30 minutes). Have unistalled and reinstalled with the same result. Any suggestions on what to do? (I tried both enabled and disabled ssl on the config tab).

Please see attach log below

Add-on version: 4.8.0
System: Home Assistant OS 11.2 (amd64 / generic-x86-64)
Home Assistant Core: 2023.12.3
Home Assistant Supervisor: 2023.11.6

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[13:02:15] INFO: Configuring timezone (Europe/Stockholm)…
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/create-users.sh
[13:02:19] INFO: InfluxDB init process in progress…
[13:02:24] INFO: InfluxDB init process in progress…
[13:02:29] INFO: InfluxDB init process in progress…
[13:02:34] INFO: InfluxDB init process in progress…
[tcp] 2023/12/17 13:02:41 tcp.Mux: Listener at 127.0.0.1:8088 failed failed to accept a connection, closing all listeners - accept tcp 127.0.0.1:8088: use of closed network connection
cont-init: info: /etc/cont-init.d/create-users.sh exited 0
cont-init: info: running /etc/cont-init.d/influxdb.sh
cont-init: info: /etc/cont-init.d/influxdb.sh exited 0
cont-init: info: running /etc/cont-init.d/kapacitor.sh
cont-init: info: /etc/cont-init.d/kapacitor.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.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 chronograf (no readiness notification)
services-up: info: copying legacy longrun influxdb (no readiness notification)
services-up: info: copying legacy longrun kapacitor (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[13:02:43] INFO: Kapacitor is waiting until InfluxDB is available…
[13:02:43] INFO: Chronograf is waiting until InfluxDB is available…
[13:02:43] INFO: Starting the InfluxDB…
[13:03:03] INFO: Starting the Kapacitor
[13:03:03] INFO: Starting Chronograf…

‘##:::’##::::‘###::::’########:::::‘###:::::’######::‘####:’########::‘#######::’########::
##::‘##::::’## ##::: ##… ##:::‘## ##:::’##… ##:. ##::… ##…::‘##… ##: ##… ##:
2023/12/17 13:03:04 Using configuration at: /etc/kapacitor/kapacitor.conf
##:’##::::‘##:. ##:: ##:::: ##::’##:. ##:: ##:::…::: ##::::: ##:::: ##:::: ##: ##:::: ##:
#####::::‘##:::. ##: ########::’##:::. ##: ##:::::::: ##::::: ##:::: ##:::: ##: ########::
##. ##::: #########: ##…::: #########: ##:::::::: ##::::: ##:::: ##:::: ##: ##… ##:::
##:. ##:: ##… ##: ##:::::::: ##… ##: ##::: ##:: ##::::: ##:::: ##:::: ##: ##::. ##::
##::. ##: ##:::: ##: ##:::::::: ##:::: ##:. ######::'####:::: ##::::. #######:: ##:::. ##:
…::::…::…:::::…::…:::::::::…:::::…:::…:::…:::::…::::::…:::…:::::…::

time=“2023-12-17T13:03:17+01:00” level=info msg=“Reporting usage stats” component=usage freq=24h reporting_addr=“https://usage.influxdata.com” stats=“os,arch,version,cluster_id,uptime”
time=“2023-12-17T13:03:17+01:00” level=info msg=“Serving chronograf at http://127.0.0.1:8889” component=server
[13:03:18] INFO: Starting NGINX…

Hi @UrbanOlsson,

I have exactly the same problem. Did you find a solution?

Cheers,
Kai

Same here.

Add-on version: 5.0.0
You are running the latest version of this add-on.
System: Home Assistant OS 11.4 (amd64 / qemux86-64)
Home Assistant Core: 2024.1.5
Home Assistant Supervisor: 2023.12.1

I tried changing port 8088 to 8084 and then it was up and running. A bit strange as port 8088 looked like it was free:
image
But everything has worked perfectly since I changed the port.

changing the port is not a solution for me. Anybody found another solution?

2 Likes