Since 4th of October victoriametrics does not start anymore

I was on the home assistant beta channel and received an update on the 4th of October Since then unfortunately, my victoriametrics add-on does not start anymore with the configuration that used to work for months. I can’t really find out what’s wrong as the VM log does not show anything particular (see further down). However, I can find entries in the log file that show login issues. How can I fix this with my plain vanilla configuration taken over from the documentation?

homeassistant.components.influxdb] Cannot connect to InfluxDB due to 'HTTPConnectionPool(host='homeassistant.local', port=8428): Max retries exceeded with url: /write?db=home_assistant (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f5f135e50>: Failed to establish a new connection: [Errno 22] Invalid argument'))'. Please check that the provided connection details (host, port, etc.) are correct and that your InfluxDB server is running and accessible. Retrying in 60 seconds.

Log file:

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [06:52:32] INFO: Starting Victoria Metrics with retention set to 99y [06:52:32] INFO: Starting Victoria Metrics with args set to 2023-10-10T04:52:32.929Z info VictoriaMetrics/lib/logger/flag.go:12 build version: victoria-metrics-20231002-214442-tags-v1.94.0-0-gf13a96f42 2023-10-10T04:52:32.932Z info VictoriaMetrics/lib/logger/flag.go:13 command-line flags 2023-10-10T04:52:32.933Z info VictoriaMetrics/lib/logger/flag.go:20 -retentionPeriod="99y" 2023-10-10T04:52:32.933Z info VictoriaMetrics/lib/logger/flag.go:20 -storageDataPath="/share/victoria-metrics-data" 2023-10-10T04:52:32.933Z info VictoriaMetrics/app/victoria-metrics/main.go:70 starting VictoriaMetrics at ":8428"... 2023-10-10T04:52:32.936Z info VictoriaMetrics/app/vmstorage/main.go:108 opening storage at "/share/victoria-metrics-data" with -retentionPeriod=99y 2023-10-10T04:52:32.953Z info VictoriaMetrics/lib/memory/memory.go:42 limiting caches to 2386204262 bytes, leaving 1590802842 bytes to the OS according to -memory.allowedPercent=60 2023-10-10T04:52:33.265Z info VictoriaMetrics/app/vmstorage/main.go:122 successfully opened storage "/share/victoria-metrics-data" in 0.328 seconds; partsCount: 211; blocksCount: 61659; rowsCount: 13829967; sizeBytes: 31961533 2023-10-10T04:52:33.278Z info VictoriaMetrics/app/vmselect/promql/rollup_result_cache.go:114 loading rollupResult cache from "/share/victoria-metrics-data/cache/rollupResult"... 2023-10-10T04:52:33.292Z info VictoriaMetrics/app/vmselect/promql/rollup_result_cache.go:142 loaded rollupResult cache from "/share/victoria-metrics-data/cache/rollupResult" in 0.014 seconds; entriesCount: 0, sizeBytes: 0 2023-10-10T04:52:33.296Z info VictoriaMetrics/app/victoria-metrics/main.go:80 started VictoriaMetrics in 0.359 seconds 2023-10-10T04:52:33.296Z info VictoriaMetrics/lib/httpserver/httpserver.go:96 starting http server at 2023-10-10T04:52:33.296Z info VictoriaMetrics/lib/httpserver/httpserver.go:97 pprof handlers are exposed at

retention: 99y
additionalArguments: ""
enableHTTPAuth: false
username: ""
password: ""
enablePrometheusScrape: false
prometheusScrapeHTTPS: false
prometheusScrapeInterval: 20s
prometheusScrapeTimeout: 15s
longelivedToken: ""
homeassistantUrl: ""
# Prometheus
  namespace: hass
      override_metric: battery_percent
      - sensor
#      - sensor.waqi*
      - climate.refrigerator*
# Victoria Metrics InfluxDB
  api_version: 1
  host: homeassistant.local
  port: 8428
  max_retries: 3
  measurement_attr: entity_id
    - friendly_name
    - unit_of_measurement
    - icon
    - source
    - options
    - editable
    - min
    - max
    - step
    - mode
    - marker_type
    - preset_modes
    - supported_features
    - supported_color_modes
    - effect_list
    - attribution
    - assumed_state
    - state_open
    - state_closed
    - writable
    - stateExtra
    - event
    - friendly_name
    - device_class
    - state_class
    - ip_address
    - device_file
    - unit_of_measurement
    - unitOfMeasure
      - sensor
      - binary_sensor
      - light
      - switch
      - cover
      - climate
      - input_boolean
      - input_select
      - number
      - lock
      - weather
      - sensor.clock*
      - sensor.glances*
      - sensor.time*
      - sensor.uptime*
      - sensor.dwd_weather_warnings_*
      - weather.weatherstation
      - binary_sensor.*_smartphone_*
      - sensor.*_smartphone_*
      - sensor.adguard_home_*
      - binary_sensor.*_internet_access

Hey @hartmood,
From your error message I suggest that you din’t set database name via flag for VictoriaMetrics.
-influxDBLabel string Default label for the DB name sent over '?db={db_name}' query parameter (default "db")
Checkout the list of command-line flags VictoriaMetrics · VictoriaMetrics

Hey @dengolius
Thanks for your reply. After spending days fixing my database issue, I decided to use MariaDB and InfluxDB Cloud for long-term storage. Therefore, I cannot use victoriametrics anymore as there does not seem to be a connection with VM and Inflxudb Cloud. Sorry, I should have closed the case earlier. It all started with a corrupt SQLite database. And it took me some time to find out what caused the problem.