container solectrus-db-1 is unhealthy

[Deanw1975]

Hallo zusammen,

nach dem Update auf 0.13.2 bekomme ich den Fehler:
container solectrus-db-1 is unhealthy

Unter anderem ein Versuch den ich durchgeführt habe

pi@solectrus:~/solectrus $ sudo docker compose down
[+] Running 8/7
 ✔ Container solectrus-mqtt-collector-1      Removed                                                                     4.1s
 ✔ Container solectrus-app-1                 Removed                                                                     0.0s
 ✔ Container solectrus-forecast-collector-1  Removed                                                                     2.1s
 ✔ Container solectrus-watchtower-1          Removed                                                                     2.7s
 ✔ Container solectrus-redis-1               Removed                                                                     4.4s
 ✔ Container solectrus-db-1                  Removed                                                                     0.1s
 ✔ Container solectrus-influxdb-1            Removed                                                                     1.6s
 ! Network solectrus_default                 Resource is still in use   

Danach den Start

pi@solectrus:~/solectrus $ sudo docker compose up
WARN[0000] Found orphan containers ([solectrus-senec-collector-1]) for this project. If you removed or renamed this service in                                                                                                                your compose file, you can run this command with the --remove-orphans flag to clean it up.
[+] Running 7/7
 ✔ Container solectrus-redis-1               Created                                                                     1.9s
 ✔ Container solectrus-watchtower-1          Created                                                                     1.4s
 ✔ Container solectrus-db-1                  Created                                                                     1.9s
 ✔ Container solectrus-influxdb-1            Created                                                                     1.9s
 ✔ Container solectrus-forecast-collector-1  Created                                                                     1.3s
 ✔ Container solectrus-mqtt-collector-1      Created                                                                     1.3s
 ✔ Container solectrus-app-1                 Created                                                                     1.4s
Attaching to solectrus-app-1, solectrus-db-1, solectrus-forecast-collector-1, solectrus-influxdb-1, solectrus-mqtt-collector-1                                                                                                               , solectrus-redis-1, solectrus-watchtower-1
solectrus-influxdb-1            | 2023-10-02T07:46:50.  info    found existing boltdb file, skipping setup wrapper      {"syst                                                                                                               em": "docker", "bolt_path": "/var/lib/influxdb2/influxd.bolt"}
solectrus-influxdb-1            | 2023-10-02T07:46:51.  info    found existing boltdb file, skipping setup wrapper      {"syst                                                                                                               em": "docker", "bolt_path": "/var/lib/influxdb2/influxd.bolt"}
solectrus-redis-1               | 1:C 02 Oct 2023 07:46:51.232 # WARNING Memory overcommit must be enabled! Without it, a back                                                                                                               ground save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory                                                                                                                condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysc                                                                                                               tl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
solectrus-redis-1               | 1:C 02 Oct 2023 07:46:51.246 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
solectrus-redis-1               | 1:C 02 Oct 2023 07:46:51.246 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pi                                                                                                               d=1, just started
solectrus-redis-1               | 1:C 02 Oct 2023 07:46:51.246 # Warning: no config file specified, using the default config.                                                                                                                In order to specify a config file use redis-server /path/to/redis.conf
solectrus-redis-1               | 1:M 02 Oct 2023 07:46:51.252 * monotonic clock: POSIX clock_gettime
solectrus-redis-1               | 1:M 02 Oct 2023 07:46:51.258 * Running mode=standalone, port=6379.
solectrus-redis-1               | 1:M 02 Oct 2023 07:46:51.263 * Server initialized
solectrus-redis-1               | 1:M 02 Oct 2023 07:46:51.265 * Loading RDB produced by version 7.2.1
solectrus-redis-1               | 1:M 02 Oct 2023 07:46:51.266 * RDB age 100 seconds
solectrus-redis-1               | 1:M 02 Oct 2023 07:46:51.268 * RDB memory usage when created 1.52 Mb
solectrus-redis-1               | 1:M 02 Oct 2023 07:46:51.287 * Done loading RDB, keys loaded: 217, keys expired: 0.
solectrus-redis-1               | 1:M 02 Oct 2023 07:46:51.291 * DB loaded from disk: 0.027 seconds
solectrus-redis-1               | 1:M 02 Oct 2023 07:46:51.291 * Ready to accept connections tcp
solectrus-db-1                  |
solectrus-db-1                  | PostgreSQL Database directory appears to contain a database; Skipping initialization
solectrus-db-1                  |
solectrus-db-1                  | 2023-10-02 07:46:51.478 UTC [1] FATAL:  database files are incompatible with server
solectrus-db-1                  | 2023-10-02 07:46:51.478 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL ve                                                                                                               rsion 15, which is not compatible with this version 16.0.
solectrus-influxdb-1            | ts=2023-10-02T07:46:52.010057Z lvl=info msg="Welcome to InfluxDB" log_id=0kcqWHv0000 version                                                                                                               =v2.7.1 commit=407fa622e9 build_date=2023-04-28T13:24:42Z log_level=info
solectrus-influxdb-1            | ts=2023-10-02T07:46:52.010313Z lvl=warn msg="nats-port argument is deprecated and unused" lo                                                                                                               g_id=0kcqWHv0000
solectrus-influxdb-1            | ts=2023-10-02T07:46:52.775785Z lvl=info msg="Resources opened" log_id=0kcqWHv0000 service=bo                                                                                                               lt path=/var/lib/influxdb2/influxd.bolt
solectrus-influxdb-1            | ts=2023-10-02T07:46:52.776673Z lvl=info msg="Resources opened" log_id=0kcqWHv0000 service=sq                                                                                                               lite path=/var/lib/influxdb2/influxd.sqlite
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.382740Z lvl=info msg="Checking InfluxDB metadata for prior version."                                                                                                                log_id=0kcqWHv0000 bolt_path=/var/lib/influxdb2/influxd.bolt
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.384134Z lvl=info msg="Using data dir" log_id=0kcqWHv0000 service=stor                                                                                                               age-engine service=store path=/var/lib/influxdb2/engine/data
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.385083Z lvl=info msg="Compaction settings" log_id=0kcqWHv0000 service                                                                                                               =storage-engine service=store max_concurrent_compactions=2 throughput_bytes_per_second=50331648 throughput_bytes_per_second_bu                                                                                                               rst=50331648
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.385635Z lvl=info msg="Open store (start)" log_id=0kcqWHv0000 service=                                                                                                               storage-engine service=store op_name=tsdb_open op_event=start
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.489111Z lvl=info msg="index opened with 8 partitions" log_id=0kcqWHv0                                                                                                               000 service=storage-engine index=tsi
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.495909Z lvl=info msg="loading changes (start)" log_id=0kcqWHv0000 ser                                                                                                               vice=storage-engine engine=tsm1 op_name="field indices" op_event=start
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.496281Z lvl=info msg="loading changes (end)" log_id=0kcqWHv0000 servi                                                                                                               ce=storage-engine engine=tsm1 op_name="field indices" op_event=end op_elapsed=0.476ms
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.501598Z lvl=info msg="Reading file" log_id=0kcqWHv0000 service=storag                                                                                                               e-engine engine=tsm1 service=cacheloader path=/var/lib/influxdb2/engine/wal/24158f8871f4bb87/autogen/1/_00001.wal size=146445
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.726410Z lvl=info msg="Opened shard" log_id=0kcqWHv0000 service=storag                                                                                                               e-engine service=store op_name=tsdb_open index_version=tsi1 path=/var/lib/influxdb2/engine/data/24158f8871f4bb87/autogen/1 dur                                                                                                               ation=321.837ms
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.727118Z lvl=info msg="Open store (end)" log_id=0kcqWHv0000 service=st                                                                                                               orage-engine service=store op_name=tsdb_open op_event=end op_elapsed=341.597ms
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.727341Z lvl=info msg="Starting retention policy enforcement service"                                                                                                                log_id=0kcqWHv0000 service=retention check_interval=30m
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.727501Z lvl=info msg="Starting precreation service" log_id=0kcqWHv000                                                                                                               0 service=shard-precreation check_interval=10m advance_period=30m
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.744555Z lvl=info msg="Starting query controller" log_id=0kcqWHv0000 s                                                                                                               ervice=storage-reads concurrency_quota=1024 initial_memory_bytes_quota_per_query=9223372036854775807 memory_bytes_quota_per_qu                                                                                                               ery=9223372036854775807 max_memory_bytes=0 queue_size=1024
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.812619Z lvl=info msg="Configuring InfluxQL statement executor (zeros                                                                                                                indicate unlimited)." log_id=0kcqWHv0000 max_select_point=0 max_select_series=0 max_select_buckets=0
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.900094Z lvl=info msg=Starting log_id=0kcqWHv0000 service=telemetry in                                                                                                               terval=8h
solectrus-influxdb-1            | ts=2023-10-02T07:46:53.904149Z lvl=info msg=Listening log_id=0kcqWHv0000 service=tcp-listene                                                                                                               r transport=http addr=:8086 port=8086
solectrus-db-1 exited with code 0
solectrus-watchtower-1          | time="2023-10-02T07:46:55Z" level=info msg="Watchtower 1.5.3"
solectrus-watchtower-1          | time="2023-10-02T07:46:55Z" level=info msg="Using no notifications"
solectrus-watchtower-1          | time="2023-10-02T07:46:55Z" level=info msg="Only checking containers in scope \"solectrus\""
solectrus-watchtower-1          | time="2023-10-02T07:46:55Z" level=info msg="Scheduling first run: 2023-10-03 07:46:55 +0000                                                                                                                UTC"
solectrus-watchtower-1          | time="2023-10-02T07:46:55Z" level=info msg="Note that the first check will be performed in 2                                                                                                               3 hours, 59 minutes, 59 seconds"
solectrus-db-1                  |
solectrus-db-1                  | PostgreSQL Database directory appears to contain a database; Skipping initialization
solectrus-db-1                  |
solectrus-db-1                  | 2023-10-02 07:46:55.555 UTC [1] FATAL:  database files are incompatible with server
solectrus-db-1                  | 2023-10-02 07:46:55.555 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL ve                                                                                                               rsion 15, which is not compatible with this version 16.0.
solectrus-db-1 exited with code 0
solectrus-db-1                  |
solectrus-db-1                  | PostgreSQL Database directory appears to contain a database; Skipping initialization
solectrus-db-1                  |
solectrus-db-1                  | 2023-10-02 07:46:58.846 UTC [1] FATAL:  database files are incompatible with server
solectrus-db-1                  | 2023-10-02 07:46:58.846 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL ve                                                                                                               rsion 15, which is not compatible with this version 16.0.
solectrus-db-1 exited with code 0
solectrus-db-1                  |
solectrus-db-1                  | PostgreSQL Database directory appears to contain a database; Skipping initialization
solectrus-db-1                  |
solectrus-db-1                  | 2023-10-02 07:47:02.452 UTC [1] FATAL:  database files are incompatible with server
solectrus-db-1                  | 2023-10-02 07:47:02.452 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16.0.
solectrus-db-1 exited with code 0
solectrus-db-1                  |
solectrus-db-1                  | PostgreSQL Database directory appears to contain a database; Skipping initialization
solectrus-db-1                  |
solectrus-db-1                  | 2023-10-02 07:47:05.807 UTC [1] FATAL:  database files are incompatible with server
solectrus-db-1                  | 2023-10-02 07:47:05.807 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16.0.
solectrus-db-1 exited with code 1
solectrus-db-1                  |
solectrus-db-1                  | PostgreSQL Database directory appears to contain a database; Skipping initialization
solectrus-db-1                  |
solectrus-db-1                  | 2023-10-02 07:47:09.326 UTC [1] FATAL:  database files are incompatible with server
solectrus-db-1                  | 2023-10-02 07:47:09.326 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16.0.
solectrus-db-1 exited with code 1
solectrus-db-1                  |
solectrus-db-1                  | PostgreSQL Database directory appears to contain a database; Skipping initialization
solectrus-db-1                  |
solectrus-db-1                  | 2023-10-02 07:47:14.591 UTC [1] FATAL:  database files are incompatible with server
solectrus-db-1                  | 2023-10-02 07:47:14.591 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16.0.
solectrus-db-1 exited with code 1
solectrus-db-1                  |
solectrus-db-1                  | PostgreSQL Database directory appears to contain a database; Skipping initialization
solectrus-db-1                  |
solectrus-db-1                  | 2023-10-02 07:47:23.204 UTC [1] FATAL:  database files are incompatible with server
solectrus-db-1                  | 2023-10-02 07:47:23.204 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16.0.
dependency failed to start: container solectrus-db-1 is unhealthy

[ledermann]

Ursache ist hier, dass du das PostgreSQL-Image von 15 auf 16 aktualisiert hast - dies erfordert jedoch ein manuelles Backup/Restore der Datenbank. Das lohnt sich nicht und würde ich daher nicht empfehlen. Abhilfe: In der docker-compose.yml dafür sorgen, dass dort wieder dies steht:

image: postgres:15-alpine

Mehr dazu hier: solectrus/hosting#35

[Deanw1975]

Danke für die schnelle Antwort.
Da ich mir die docker-compose.yml zerlegt habe, hatte ich die neu geladen. Für neue Installationen wird das Image 16 genutzt. Bei alten die 15.

Habe die Datei angepasst und nun läuft es wieder.
Danke