Could not connect to Redis at redis:6379: Connection refused

RRossi · May 13, 2022

Hi, ich habe auf einem Hetzner Cloudserver eine Mailcow-Installation, die soweit gut läuft. Allerdings stürzt der Cloudserver immer mal wieder ab und muss dann durch einen harten Reset wiederbelebt werden. In den Logs habe ich ein Problem mit der Redis-Datenbank festgestellt. Hier ein Auszug aus dem ACME-Mailcow-Log:

2022-05-11T21:23:50.633572139Z Waiting for Redis...
2022-05-11T21:23:52.649958730Z Wed May 11 21:23:52 UTC 2022 - SKIP_LETS_ENCRYPT=y, skipping Let's Encrypt...
2022-05-13T06:13:41.065969198Z Fri May 13 06:13:41 UTC 2022 - SKIP_LETS_ENCRYPT=y, skipping Let's Encrypt...
2022-05-13T15:47:30.579748408Z **Could not connect to Redis at redis:6379: Connection refused**
2022-05-13T15:47:30.580625522Z Waiting for Redis...
2022-05-13T15:47:32.588607527Z Fri May 13 15:47:32 UTC 2022 - SKIP_LETS_ENCRYPT=y, skipping Let's Encrypt...
2022-05-13T15:53:24.382985752Z Fri May 13 15:53:24 UTC 2022 - SKIP_LETS_ENCRYPT=y, skipping Let's Encrypt...

Und hier noch einen Auszug aus dem Redis-Container-Log:

133:C 13 May 2022 15:40:33.085 * RDB: 0 MB of memory used by copy-on-write
1:M 13 May 2022 15:40:33.119 * Background saving terminated with success
1:M 13 May 2022 15:45:34.015 * 100 changes in 300 seconds. Saving...
1:M 13 May 2022 15:45:34.016 * Background saving started by pid 134
134:C 13 May 2022 15:45:34.089 * DB saved on disk
134:C 13 May 2022 15:45:34.090 * RDB: 0 MB of memory used by copy-on-write
1:M 13 May 2022 15:45:34.117 * Background saving terminated with success
1:C 13 May 2022 15:47:30.895 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 13 May 2022 15:47:30.895 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 13 May 2022 15:47:30.895 # **Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf**
1:M 13 May 2022 15:47:30.896 * monotonic clock: POSIX clock_gettime
1:M 13 May 2022 15:47:30.903 * Running mode=standalone, port=6379.
1:M 13 May 2022 15:47:30.904 # Server initialized
1:M 13 May 2022 15:47:30.904 # **WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.**
1:M 13 May 2022 15:47:30.909 * Loading RDB produced by version 6.2.6
1:M 13 May 2022 15:47:30.913 * RDB age 116 seconds
1:M 13 May 2022 15:47:30.914 * RDB memory usage when created 11.12 Mb
1:M 13 May 2022 15:47:31.042 # Done loading RDB, keys loaded: 15677, keys expired: 0.
1:M 13 May 2022 15:47:31.042 * DB loaded from disk: 0.137 seconds
1:M 13 May 2022 15:47:31.042 * Ready to accept connections
1:M 13 May 2022 15:52:31.095 * 100 changes in 300 seconds. Saving...
1:M 13 May 2022 15:52:31.096 * Background saving started by pid 14
14:C 13 May 2022 15:52:31.172 * DB saved on disk
14:C 13 May 2022 15:52:31.173 * RDB: 0 MB of memory used by copy-on-write

Jemand eine Idee?

RRossi · May 16, 2022

Habe vor 2 Tagen das Update-Script ausgeführt, und seitdem läuft wieder alles. Logs sind sauber. Während des Update-Vorgangs ist noch ein verwaister Container aufgetaucht:
WARNING: Found orphan containers (mailcowdockerized_ipv6nat-mailcow_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.
Der scheint aber beim Updaten gelöscht worden zu sein, mit docker -ps tauscht er jedenfalls nicht mehr auf.