InfluxDB addon won´t start anymore

[m-wo]

Problem/Motivation

My addon won´t start anymore (I guess after the update to 4.8.0)

Expected behavior

Addon starting

Actual behavior

Stuck in a starting/restarting loop, no more details even in debug log mode

Steps to reproduce

Trying to start the addon

Log (debug):

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: InfluxDB
 Scalable datastore for metrics, events, and real-time analytics
-----------------------------------------------------------
 Add-on version: 4.8.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.5  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.10.3
 Home Assistant Supervisor: 2023.10.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-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[16:28:45] INFO: Configuring timezone (Europe/Berlin)...
Log level is set to DEBUG
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
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
[16:28:49] DEBUG: Requested API resource: http://supervisor/dns/info
[16:28:49] DEBUG: Request method: GET
[16:28:49] DEBUG: Request data: {}
[16:28:49] DEBUG: API HTTP Response code: 200
[16:28:49] DEBUG: API Response: {"result": "ok", "data": {"version": "2023.06.2", "version_latest": "2023.06.2", "update_available": false, "host": "172.30.32.3", "servers": [], "locals": ["dns://192.168.0.1", "dns://192.168.200.1"], "mdns": true, "llmnr": true, "fallback": true}}
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
[16:28:49] INFO: Kapacitor is waiting until InfluxDB is available...
[16:28:49] INFO: Chronograf is waiting until InfluxDB is available...
[16:28:50] INFO: Starting the InfluxDB...
[16:29:17] INFO: InfluxDB stopped, restarting...
[16:29:18] INFO: Starting the InfluxDB...
[16:29:49] INFO: InfluxDB stopped, restarting...
[16:29:50] INFO: Starting the InfluxDB...
[16:30:18] INFO: InfluxDB stopped, restarting...
[16:30:20] INFO: Starting the InfluxDB...
[16:30:47] INFO: InfluxDB stopped, restarting...
[16:30:48] INFO: Starting the InfluxDB...
[16:31:15] INFO: InfluxDB stopped, restarting...
[16:31:16] INFO: Starting the InfluxDB...
[16:31:46] INFO: InfluxDB stopped, restarting...
[16:31:47] INFO: Starting the InfluxDB...
[16:32:17] INFO: InfluxDB stopped, restarting...
[16:32:18] INFO: Starting the InfluxDB...
[16:32:45] INFO: InfluxDB stopped, restarting...
[16:32:46] INFO: Starting the InfluxDB...

Proposed changes

none

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!