dovecot-mailcow-1 | Feb 3 08:33:20 0f3a76f0bc16 syslog-ng[161]: REDIS server error during connection; driver='d_redis_ui_log#0', error='Operation timed out', time_reopen='60' also seeing this on the main screen: Connection to Redis failed. The following error was reported: Operation timed out also seeing errors like this. [code] postfix-mailcow-1 | Feb 3 08:39:32 a22ca9808e87 syslog-ng[9]: Error processing log message: 504 Gateway Time-out postfix-mailcow-1 | nginx/1.25.3 postfix-mailcow-1 | postfix-mailcow-1 | postfix-mailcow-1 | MTP helo=>@ @ @ @< postfix-mailcow-1 | [/code]

Did you look at the logs of the redis container?

I haven't had any issues on this system so how do I get to the logs without the web screen to look at? I see there is someone else having this issue also. This person seems to have the same issue: https://community.mailcow.email/d/209-connection-to-redis-failed/6

That's a very old thread you linked above :) https://docs.mailcow.email/troubleshooting/debug-logs/

How much of the log do you want. It won't let me post all of it. Here is some of it . I will post more in further replys. [code] [demo@mail mailcow-dockerized]$ sudo docker-compose logs $redis olefy-mailcow-1 | olefy INFO olefy listen address: ['0.0.0.0'] (type: ) olefy-mailcow-1 | olefy INFO olefy listen port: 10055 olefy-mailcow-1 | olefy INFO olefy tmp dir: /tmp olefy-mailcow-1 | olefy INFO olefy python path: /usr/bin/python3 olefy-mailcow-1 | olefy INFO olefy olvba path: /usr/bin/olevba olefy-mailcow-1 | olefy INFO olefy log level: 20 olefy-mailcow-1 | olefy INFO olefy min file length: 500 olefy-mailcow-1 | olefy INFO olefy delete tmp file: 1 olefy-mailcow-1 | olefy INFO olefy delete tmp file when failed: 1 olefy-mailcow-1 | olefy INFO serving on ('0.0.0.0', 10055) redis-mailcow-1 | 1:C 03 Feb 2024 08:48:40.547 # WARNING Memory overcommit must be enabled! Without it, a background 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/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. redis-mailcow-1 | 1:C 03 Feb 2024 08:48:40.547 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo redis-mailcow-1 | 1:C 03 Feb 2024 08:48:40.547 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started redis-mailcow-1 | 1:C 03 Feb 2024 08:48:40.547 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.548 * monotonic clock: POSIX clock_gettime redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.551 * Running mode=standalone, port=6379. redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.552 * Server initialized redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.553 * Loading RDB produced by version 7.2.4 redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.553 * RDB age 48 seconds redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.553 * RDB memory usage when created 38.02 Mb redis-mailcow-1 | 1:M 03 Feb 2024 08:48:41.081 * Done loading RDB, keys loaded: 202769, keys expired: 768. redis-mailcow-1 | 1:M 03 Feb 2024 08:48:41.084 * DB loaded from disk: 0.531 seconds redis-mailcow-1 | 1:M 03 Feb 2024 08:48:41.084 * Ready to accept connections tcp postfix-mailcow-1 | 2024-02-03 08:49:14,360 INFO Set uid to user 0 succeeded postfix-mailcow-1 | 2024-02-03 08:49:14,361 INFO supervisord started with pid 1 postfix-mailcow-1 | 2024-02-03 08:49:15,365 INFO spawned: 'processes' with pid 7 postfix-mailcow-1 | 2024-02-03 08:49:15,368 INFO spawned: 'postfix' with pid 8 postfix-mailcow-1 | 2024-02-03 08:49:15,369 INFO spawned: 'syslog-ng' with pid 9 postfix-mailcow-1 | Uptime: 34 Threads: 7 Questions: 246 Slow queries: 0 Opens: 39 Open tables: 30 Queries per second avg: 7.235 postfix-mailcow-1 | Feb 3 08:49:15 625434fc0fda syslog-ng[9]: syslog-ng starting up; version='3.28.1' postfix-mailcow-1 | Checking if ASN for your IP is listed for Spamhaus Bad ASN List... postfix-mailcow-1 | 2024-02-03 08:49:16,664 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) postfix-mailcow-1 | 2024-02-03 08:49:16,664 INFO success: postfix entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) postfix-mailcow-1 | 2024-02-03 08:49:16,665 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) postfix-mailcow-1 | The AS of your IP is NOT listed as a banned AS from Spamhaus! postfix-mailcow-1 | Using the open Spamhaus blocklists. postfix-mailcow-1 | chown: cannot access '/usr/share/man/man1/mailq.1.gz': No such file or directory postfix-mailcow-1 | Feb 3 08:49:19 625434fc0fda postfix/postfix-script[375]: starting the Postfix mail system postfix-mailcow-1 | Feb 3 08:49:19 625434fc0fda postfix/master[377]: daemon started -- version 3.5.23, configuration /opt/postfix/conf postfix-mailcow-1 | Feb 3 08:49:15 625434fc0fda syslog-ng[9]: REDIS server error during connection; driver='d_redis_ui_log#0', error='Connection timed out', time_reopen='60' postfix-mailcow-1 | Feb 3 08:49:15 625434fc0fda syslog-ng[9]: REDIS server error during connection; driver='d_redis_f2b_channel#0', error='Connection timed out', time_reopen='60' postfix-mailcow-1 | Feb 3 08:49:26 625434fc0fda postfix/postscreen[383]: cache proxy:btree:/var/lib/postfix/postscreen_cache full cleanup: retained=0 dropped=0 entries postfix-mailcow-1 | Feb 3 08:49:26 625434fc0fda postfix/postscreen[383]: CONNECT from [178.251.229.9]:47546 to [172.22.1.253]:25 postfix-mailcow-1 | Feb 3 08:49:26 625434fc0fda whitelist_forwardinghosts: Look up 178.251.229.9 on whitelist, result postfix-mailcow-1 | Feb 3 08:49:26 625434fc0fda syslog-ng[9]: Error processing log message: 502 Bad Gateway postfix-mailcow-1 | postfix-mailcow-1 | 502 Bad Gateway postfix-mailcow-1 | nginx/1.25.3 postfix-mailcow-1 | postfix-mailcow-1 | postfix-mailcow-1 | >@ @ @ @ @ @< postfix-mailcow-1 | postfix-mailcow-1 | Feb 3 08:49:26 625434fc0fda postfix/postscreen[383]: warning: read TCP map reply from 127.0.0.1:10027: malformed reply: _ 502 Bad Gateway_ _ 502 Bad Gateway@ @ @ @ @ @< postfix-mailcow-1 | postfix-mailcow-1 | Feb 3 08:56:56 625434fc0fda postfix/postscreen[424]: warning: read TCP map reply from 127.0.0.1:10027: malformed reply: _ 502 Bad Gateway_ _ 502 Bad Gateway@ @ @ @ @< postfix-mailcow-1 | postfix-mailcow-1 | Feb 3 08:58:47 625434fc0fda postfix/postscreen[455]: PREGREET 11 after 0.13 from [193.222.96.141]:53772: EHLO User\r\n postfix-mailcow-1 | Feb 3 08:58:47 625434fc0fda postfix/dnsblog[466]: addr 193.222.96.141 listed by domain bl.mailspike.net as 127.0.0.2 postfix-mailcow-1 | Feb 3 08:58:47 625434fc0fda postfix/dnsblog[469]: addr 193.222.96.141 listed by domain zen.spamhaus.org as 127.0.0.4 postfix-mailcow-1 | Feb 3 08:58:47 625434fc0fda postfix/dnsblog[469]: addr 193.222.96.141 listed by domain zen.spamhaus.org as 127.0.0.2 postfix-mailcow-1 | Feb 3 08:58:47 625434fc0fda postfix/dnsblog[469]: addr 193.222.96.141 listed by domain zen.spamhaus.org as 127.0.0.9 postfix-mailcow-1 | Feb 3 08:58:47 625434fc0fda postfix/dnsblog[469]: addr 193.222.96.141 listed by domain zen.spamhaus.org as 127.0.0.3 postfix-mailcow-1 | Feb 3 08:58:48 625434fc0fda postfix/postscreen[455]: CONNECT from [178.251.229.9]:39204 to [172.22.1.253]:25 postfix-mailcow-1 | Feb 3 08:58:48 625434fc0fda whitelist_forwardinghosts: Look up 178.251.229.9 on whitelist, result postfix-mailcow-1 | Feb 3 08:58:48 625434fc0fda syslog-ng[9]: Error processing log message: 502 Bad Gateway postfix-mailcow-1 | postfix-mailcow-1 | 502 Bad Gateway postfix-mailcow-1 | nginx/1.25.3 postfix-mailcow-1 | postfix-mailcow-1 | postfix-mailcow-1 | >@ @ @ @ @ @ daily.cld database is up-to-date (version: 27174, sigs: 2052115, f-level: 90, builder: raynman) clamd-mailcow-1 | Sat Feb 3 13:49:15 2024 -> main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) clamd-mailcow-1 | Sat Feb 3 13:49:15 2024 -> bytecode.cvd database is up-to-date (version: 334, sigs: 91, f-level: 90, builder: anvilleg) clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: Global time limit set to 120000 milliseconds. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: Global size limit set to 52428800 bytes. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: File size limit set to 26214400 bytes. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: Recursion level limit set to 5. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: Files limit set to 200. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: MaxEmbeddedPE limit set to 41943040 bytes. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: MaxHTMLNormalize limit set to 41943040 bytes. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: MaxHTMLNoTags limit set to 8388608 bytes. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: MaxScriptNormalize limit set to 20971520 bytes. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: MaxZipTypeRcg limit set to 1048576 bytes. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: MaxPartitions limit set to 50. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: MaxIconsPE limit set to 100. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: MaxRecHWP3 limit set to 16. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: PCREMatchLimit limit set to 100000. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: PCRERecMatchLimit limit set to 2000. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Limits: PCREMaxFileSize limit set to 104857600. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Archive support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> AlertExceedsMax heuristic detection disabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Heuristic alerts enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Portable Executable support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> ELF support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Mail files support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> OLE2 support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> PDF support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> SWF support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> HTML support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> XMLDOCS support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> HWP3 support enabled. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Heuristic: precedence enabled clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Self checking every 3600 seconds. clamd-mailcow-1 | Sat Feb 3 13:49:41 2024 -> Set stacksize to 1048576 clamd-mailcow-1 | receiving incremental file list clamd-mailcow-1 | ./ clamd-mailcow-1 | blurl.ndb clamd-mailcow-1 | phishtank.ndb clamd-mailcow-1 | clamd-mailcow-1 | sent 2,646 bytes received 5,230 bytes 3,150.40 bytes/sec clamd-mailcow-1 | total size is 17,908,699 speedup is 2,273.83 clamd-mailcow-1 | RELOADING clamd-mailcow-1 | Sat Feb 3 13:59:23 2024 -> Reading databases from /var/lib/clamav clamd-mailcow-1 | Sat Feb 3 13:59:50 2024 -> Database correctly reloaded (8834378 signatures) clamd-mailcow-1 | Sat Feb 3 13:59:50 2024 -> Database reload completed. clamd-mailcow-1 | Sat Feb 3 13:59:50 2024 -> Activating the newly loaded database... [/code] [code] nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: using the "epoll" event method nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: nginx/1.25.3 nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: built by gcc 12.2.1 20220924 (Alpine 12.2.1_git20220924-r10) nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: OS: Linux 6.6.15-1-lts nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1073741816:1073741816 nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: start worker processes nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: start worker process 23 nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: start worker process 24 nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: start cache manager process 25 nginx-mailcow-1 | 2024/02/03 08:48:43 [notice] 1#1: start cache loader process 26 nginx-mailcow-1 | 2024/02/03 08:49:26 [error] 24#24: *1 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::11, server: _, request: "GET /forwardinghosts.php?host=178.251.229.9 HTTP/1.1", upstream: "fastcgi://172.22.1.7:9001", host: "nginx:8081" nginx-mailcow-1 | 2024/02/03 08:49:26 [error] 24#24: *1 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::11, server: _, request: "GET /forwardinghosts.php?host=178.251.229.9 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::b]:9001", host: "nginx:8081" nginx-mailcow-1 | fd4d:6169:6c63:6f77::11 - - [03/Feb/2024:08:49:26 -0500] "GET /forwardinghosts.php?host=178.251.229.9 HTTP/1.1" 502 157 "-" "curl/7.74.0" nginx-mailcow-1 | 2024/02/03 08:49:33 [error] 24#24: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://172.22.1.7:9002", host: "www.dccathome.com" nginx-mailcow-1 | 2024/02/03 08:49:33 [error] 24#24: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::b]:9002", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:33 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:35 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:35 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 2024/02/03 08:49:36 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:36 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:37 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:37 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:38 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:38 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:39 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:39 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:40 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:40 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 2024/02/03 08:49:43 [notice] 26#26: http file cache: /tmp 0.000M, bsize: 4096 nginx-mailcow-1 | 2024/02/03 08:49:44 [notice] 1#1: signal 17 (SIGCHLD) received from 26 nginx-mailcow-1 | 2024/02/03 08:49:44 [notice] 1#1: cache loader process 26 exited with code 0 nginx-mailcow-1 | 2024/02/03 08:49:44 [notice] 1#1: signal 29 (SIGIO) received nginx-mailcow-1 | 2024/02/03 08:49:44 [error] 24#24: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::b]:9002", host: "www.dccathome.com" nginx-mailcow-1 | 2024/02/03 08:49:44 [error] 24#24: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://172.22.1.7:9002", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:44 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:53 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:53 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:54 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:54 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:54 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:54 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 2024/02/03 08:49:54 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:54 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:54 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:54 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 47.200.48.82 - - [03/Feb/2024:08:49:54 -0500] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0" nginx-mailcow-1 | 2024/02/03 08:49:54 [error] 24#24: *4 no live upstreams while connecting to upstream, client: 47.200.48.82, server: mail.dccathome.com, request: "GET / HTTP/1.1", upstream: "fastcgi://phpfpm", host: "www.dccathome.com" nginx-mailcow-1 | fd4d:6169:6c63:6f77::11 - - [03/Feb/2024:08:56:56 -0500] "GET /forwardinghosts.php?host=178.251.229.9 HTTP/1.1" 502 157 "-" "curl/7.74.0" nginx-mailcow-1 | 2024/02/03 08:56:56 [error] 23#23: *10 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::11, server: _, request: "GET /forwardinghosts.php?host=178.251.229.9 HTTP/1.1", upstream: "fastcgi://172.22.1.7:9001", host: "nginx:8081" nginx-mailcow-1 | 2024/02/03 08:56:56 [error] 23#23: *10 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::11, server: _, request: "GET /forwardinghosts.php?host=178.251.229.9 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::b]:9001", host: "nginx:8081" nginx-mailcow-1 | 2024/02/03 08:58:47 [error] 24#24: *26 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::11, server: _, request: "GET /forwardinghosts.php?host=193.222.96.141 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::b]:9001", host: "nginx:8081" nginx-mailcow-1 | fd4d:6169:6c63:6f77::11 - - [03/Feb/2024:08:58:47 -0500] "GET /forwardinghosts.php?host=193.222.96.141 HTTP/1.1" 502 157 "-" "curl/7.74.0" nginx-mailcow-1 | 2024/02/03 08:58:47 [error] 24#24: *26 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::11, server: _, request: "GET /forwardinghosts.php?host=193.222.96.141 HTTP/1.1", upstream: "fastcgi://172.22.1.7:9001", host: "nginx:8081" nginx-mailcow-1 | fd4d:6169:6c63:6f77::11 - - [03/Feb/2024:08:58:48 -0500] "GET /forwardinghosts.php?host=178.251.229.9 HTTP/1.1" 502 157 "-" "curl/7.74.0" nginx-mailcow-1 | 2024/02/03 08:58:48 [error] 24#24: *29 no live upstreams while connecting to upstream, client: fd4d:6169:6c63:6f77::11, server: _, request: "GET /forwardinghosts.php?host=178.251.229.9 HTTP/1.1", upstream: "fastcgi://phpfpm", host: "nginx:8081" [/code]

Well, can you see any problems in the logs?

This is at the beginning of the log [code] redis-mailcow-1 | 1:C 03 Feb 2024 08:48:40.547 # WARNING Memory overcommit must be enabled! Without it, a background 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/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. redis-mailcow-1 | 1:C 03 Feb 2024 08:48:40.547 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo redis-mailcow-1 | 1:C 03 Feb 2024 08:48:40.547 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started redis-mailcow-1 | 1:C 03 Feb 2024 08:48:40.547 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.548 * monotonic clock: POSIX clock_gettime redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.551 * Running mode=standalone, port=6379. redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.552 * Server initialized redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.553 * Loading RDB produced by version 7.2.4 redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.553 * RDB age 48 seconds redis-mailcow-1 | 1:M 03 Feb 2024 08:48:40.553 * RDB memory usage when created 38.02 Mb redis-mailcow-1 | 1:M 03 Feb 2024 08:48:41.081 * Done loading RDB, keys loaded: 202769, keys expired: 768. redis-mailcow-1 | 1:M 03 Feb 2024 08:48:41.084 * DB loaded from disk: 0.531 seconds redis-mailcow-1 | 1:M 03 Feb 2024 08:48:41.084 * Ready to accept connections tcp postfix-mailcow-1 | 2024-02-03 08:49:14,360 INFO Set uid to user 0 succeeded postfix-mailcow-1 | 2024-02-03 08:49:14,361 INFO supervisord started with pid 1 postfix-mailcow-1 | 2024-02-03 08:49:15,365 INFO spawned: 'processes' with pid 7 postfix-mailcow-1 | 2024-02-03 08:49:15,368 INFO spawned: 'postfix' with pid 8 postfix-mailcow-1 | 2024-02-03 08:49:15,369 INFO spawned: 'syslog-ng' with pid 9 postfix-mailcow-1 | Uptime: 34 Threads: 7 Questions: 246 Slow queries: 0 Opens: 39 Open tables: 30 Queries per second avg: 7.235 postfix-mailcow-1 | Feb 3 08:49:15 625434fc0fda syslog-ng[9]: syslog-ng starting up; version='3.28.1' postfix-mailcow-1 | Checking if ASN for your IP is listed for Spamhaus Bad ASN List... postfix-mailcow-1 | 2024-02-03 08:49:16,664 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) postfix-mailcow-1 | 2024-02-03 08:49:16,664 INFO success: postfix entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) postfix-mailcow-1 | 2024-02-03 08:49:16,665 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) postfix-mailcow-1 | The AS of your IP is NOT listed as a banned AS from Spamhaus! postfix-mailcow-1 | Using the open Spamhaus blocklists. postfix-mailcow-1 | chown: cannot access '/usr/share/man/man1/mailq.1.gz': No such file or directory postfix-mailcow-1 | Feb 3 08:49:19 625434fc0fda postfix/postfix-script[375]: starting the Postfix mail system postfix-mailcow-1 | Feb 3 08:49:19 625434fc0fda postfix/master[377]: daemon started -- version 3.5.23, configuration /opt/postfix/conf postfix-mailcow-1 | Feb 3 08:49:15 625434fc0fda syslog-ng[9]: REDIS server error during connection; driver='d_redis_ui_log#0', error='Connection timed out', time_reopen='60' postfix-mailcow-1 | Feb 3 08:49:15 625434fc0fda syslog-ng[9]: REDIS server error during connection; driver='d_redis_f2b_channel#0', error='Connection timed out', time_reopen='60' postfix-mailcow-1 | Feb 3 08:49:26 625434fc0fda postfix/postscreen[383]: cache proxy:btree:/var/lib/postfix/postscreen_cache full cleanup: retained=0 dropped=0 entries postfix-mailcow-1 | Feb 3 08:49:26 625434fc0fda postfix/postscreen[383]: CONNECT from [178.251.229.9]:47546 to [172.22.1.253]:25 postfix-mailcow-1 | Feb 3 08:49:26 625434fc0fda whitelist_forwardinghosts: Look up 178.251.229.9 on whitelist, result postfix-mailcow-1 | Feb 3 08:49:26 625434fc0fda syslog-ng[9]: Error processing log message: 502 Bad Gateway [/code]

Just pull the logs of the redis container, not all of the logs And did you try restarting Mailcow?

yes I have restarted . How do I format the command to just get redis? [code] [root@mail mailcow-dockerized]# docker compose logs --tail=300 redis-mailcow redis-mailcow-1 | 1:C 03 Feb 2024 09:42:21.849 # WARNING Memory overcommit must be enabled! Without it, a background 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/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. redis-mailcow-1 | 1:C 03 Feb 2024 09:42:21.857 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo redis-mailcow-1 | 1:C 03 Feb 2024 09:42:21.858 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started redis-mailcow-1 | 1:C 03 Feb 2024 09:42:21.858 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf redis-mailcow-1 | 1:M 03 Feb 2024 09:42:21.858 * monotonic clock: POSIX clock_gettime redis-mailcow-1 | 1:M 03 Feb 2024 09:42:21.859 * Running mode=standalone, port=6379. redis-mailcow-1 | 1:M 03 Feb 2024 09:42:21.859 * Server initialized redis-mailcow-1 | 1:M 03 Feb 2024 09:42:21.860 * Loading RDB produced by version 7.2.4 redis-mailcow-1 | 1:M 03 Feb 2024 09:42:21.860 * RDB age 47 seconds redis-mailcow-1 | 1:M 03 Feb 2024 09:42:21.860 * RDB memory usage when created 37.91 Mb redis-mailcow-1 | 1:M 03 Feb 2024 09:42:22.502 * Done loading RDB, keys loaded: 202763, keys expired: 2. redis-mailcow-1 | 1:M 03 Feb 2024 09:42:22.503 * DB loaded from disk: 0.644 seconds redis-mailcow-1 | 1:M 03 Feb 2024 09:42:22.503 * Ready to accept connections tcp [/code]

Restarted the server It now shows this in the log. Will let it run for a while and see if it stays stable. Not sure what is going on though. [code] [root@mail mailcow-dockerized]# docker compose logs --tail=300 redis-mailcow redis-mailcow-1 | 1:C 03 Feb 2024 09:48:43.171 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo redis-mailcow-1 | 1:C 03 Feb 2024 09:48:43.173 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started redis-mailcow-1 | 1:C 03 Feb 2024 09:48:43.173 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf redis-mailcow-1 | 1:M 03 Feb 2024 09:48:43.173 * monotonic clock: POSIX clock_gettime redis-mailcow-1 | 1:M 03 Feb 2024 09:48:43.174 * Running mode=standalone, port=6379. redis-mailcow-1 | 1:M 03 Feb 2024 09:48:43.174 * Server initialized redis-mailcow-1 | 1:M 03 Feb 2024 09:48:43.174 * Loading RDB produced by version 7.2.4 redis-mailcow-1 | 1:M 03 Feb 2024 09:48:43.174 * RDB age 36 seconds redis-mailcow-1 | 1:M 03 Feb 2024 09:48:43.174 * RDB memory usage when created 37.91 Mb redis-mailcow-1 | 1:M 03 Feb 2024 09:48:43.706 * Done loading RDB, keys loaded: 202763, keys expired: 0. redis-mailcow-1 | 1:M 03 Feb 2024 09:48:43.707 * DB loaded from disk: 0.533 seconds redis-mailcow-1 | 1:M 03 Feb 2024 09:48:43.707 * Ready to accept connections tcp redis-mailcow-1 | 1:signal-handler (1706972253) Received SIGTERM scheduling shutdown... redis-mailcow-1 | 1:M 03 Feb 2024 09:57:34.013 * User requested shutdown... redis-mailcow-1 | 1:M 03 Feb 2024 09:57:34.013 * Saving the final RDB snapshot before exiting. redis-mailcow-1 | 1:M 03 Feb 2024 09:57:35.403 * DB saved on disk redis-mailcow-1 | 1:M 03 Feb 2024 09:57:35.403 # Redis is now ready to exit, bye bye... redis-mailcow-1 | 1:C 03 Feb 2024 09:59:37.919 # WARNING Memory overcommit must be enabled! Without it, a background 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/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. redis-mailcow-1 | 1:C 03 Feb 2024 09:59:37.920 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo redis-mailcow-1 | 1:C 03 Feb 2024 09:59:37.920 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started redis-mailcow-1 | 1:C 03 Feb 2024 09:59:37.920 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf redis-mailcow-1 | 1:M 03 Feb 2024 09:59:37.921 * monotonic clock: POSIX clock_gettime redis-mailcow-1 | 1:M 03 Feb 2024 09:59:38.429 * Running mode=standalone, port=6379. redis-mailcow-1 | 1:M 03 Feb 2024 09:59:38.429 * Server initialized redis-mailcow-1 | 1:M 03 Feb 2024 09:59:38.551 * Loading RDB produced by version 7.2.4 redis-mailcow-1 | 1:M 03 Feb 2024 09:59:38.551 * RDB age 124 seconds redis-mailcow-1 | 1:M 03 Feb 2024 09:59:38.551 * RDB memory usage when created 37.93 Mb redis-mailcow-1 | 1:M 03 Feb 2024 09:59:45.549 * Done loading RDB, keys loaded: 202763, keys expired: 0. redis-mailcow-1 | 1:M 03 Feb 2024 09:59:45.549 * DB loaded from disk: 7.119 seconds redis-mailcow-1 | 1:M 03 Feb 2024 09:59:45.549 * Ready to accept connections tcp redis-mailcow-1 | 1:M 03 Feb 2024 10:04:38.068 * 100 changes in 300 seconds. Saving... redis-mailcow-1 | 1:M 03 Feb 2024 10:04:38.071 * Background saving started by pid 20 redis-mailcow-1 | 20:C 03 Feb 2024 10:04:38.436 * DB saved on disk redis-mailcow-1 | 20:C 03 Feb 2024 10:04:38.438 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB redis-mailcow-1 | 1:M 03 Feb 2024 10:04:38.472 * Background saving terminated with success redis-mailcow-1 | 1:M 03 Feb 2024 10:09:39.079 * 100 changes in 300 seconds. Saving... redis-mailcow-1 | 1:M 03 Feb 2024 10:09:39.081 * Background saving started by pid 21 redis-mailcow-1 | 21:C 03 Feb 2024 10:09:39.414 * DB saved on disk redis-mailcow-1 | 21:C 03 Feb 2024 10:09:39.416 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB redis-mailcow-1 | 1:M 03 Feb 2024 10:09:39.482 * Background saving terminated with success [/code] Didn't take long . Just saw this error and mailcow web page stopped responding. [code] postfix-mailcow-1 | Feb 3 10:14:30 2bb078433cad postfix/submission/smtpd[488]: Anonymous TLS connection established from unknown[91.215.85.17]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 postfix-mailcow-1 | Feb 3 10:14:30 2bb078433cad postfix/submission/smtpd[488]: discarding EHLO keywords: CHUNKING postfix-mailcow-1 | Feb 3 10:14:33 2bb078433cad postfix/submission/smtpd[488]: warning: unknown[91.215.85.17]: SASL PLAIN authentication failed: (reason unavailable), sasl_username=support@dccathome.com postfix-mailcow-1 | Feb 3 10:14:33 2bb078433cad postfix/submission/smtpd[488]: disconnect from unknown[91.215.85.17] ehlo=2 starttls=1 auth=0/1 quit=1 unknown=0/1 commands=4/6 postfix-mailcow-1 | Feb 3 10:15:12 2bb078433cad postfix/postscreen[492]: CONNECT from [193.222.96.141]:59808 to [172.22.1.253]:25 postfix-mailcow-1 | Feb 3 10:15:21 2bb078433cad postfix/postscreen[492]: fatal: watchdog timeout postfix-mailcow-1 | Feb 3 10:15:22 2bb078433cad postfix/master[379]: warning: process /usr/lib/postfix/sbin/postscreen pid 492 exit status 1 postfix-mailcow-1 | Feb 3 10:15:22 2bb078433cad postfix/master[379]: warning: /usr/lib/postfix/sbin/postscreen: bad command startup -- throttling [/code] Back to this error on the webpage Connection to Redis failed. The following error was reported: Operation timed out

For this update I didn't make a backup. Is there a way I can go back to previous version? Can I undo what the update did manually? Does this have to do with the problem: [code] redis-mailcow-1 | 1:C 03 Feb 2024 10:29:21.702 # WARNING Memory overcommit must be enabled! Without it, a background 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/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. redis-mailcow-1 | 1:C 03 Feb 2024 10:29:21.702 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo redis-mailcow-1 | 1:C 03 Feb 2024 10:29:21.702 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started redis-mailcow-1 | 1:C 03 Feb 2024 10:29:21.702 # Warning: no config file specified, using the default config. In order to specify a c [/code]

redis error since update to 2024-01d

maybl8

Let me correct this.
After restart and running that command with or without the - I actually get this

[demo@mail mailcow-dockerized]$ sudo docker-compose logs --tail=200  netfilter-mailcow
[sudo] password for demo:
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Traceback (most recent call last):
netfilter-mailcow-1  |   File "/app/main.py", line 410, in <module>
netfilter-mailcow-1  |     clear()
netfilter-mailcow-1  |   File "/app/main.py", line 222, in clear
netfilter-mailcow-1  |     tables.clearIPv6Table()
netfilter-mailcow-1  |   File "/app/modules/IPTables.py", line 72, in clearIPv6Table
netfilter-mailcow-1  |     self.clearTable(iptc.Table6(iptc.Table6.FILTER))
netfilter-mailcow-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 589, in __new__
netfilter-mailcow-1  |     obj._init(name, autocommit)
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip6tc.py", line 606, in _init
netfilter-mailcow-1  |     self.refresh()
netfilter-mailcow-1  |   File "/usr/lib/python3.11/site-packages/iptc/ip4tc.py", line 1634, in refresh
netfilter-mailcow-1  |     raise IPTCError("can't initialize %s: %s" % (self.name,
netfilter-mailcow-1  | iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you need to insmod?)'

DocFraggle

maybl8 that’s correct, the “old” docker-compose version is incompatible with the latest docker compose values.
You have to use

sudo docker compose logs -f --tail=200 netfilter-mailcow

As I said WITHOUT the ‘-’ 🙂

EDIT: no, wait, what exactly did you do before the restart? What’s the value of your DOCKER_COMPOSE_VERSION variable?

maybl8

DOCKER_COMPOSE_VERSION=native

Well I thought I knew what was triggering the issue but now I am not sure.

What my process to monitor my machine is.
Start the server.
Open the web page for mailcow.
Open another desktop
Open monitor windows for postfix , dovecot, netfilter and now redis but that is new.
To see netfilter I have to run a script to reset netfilter first or I get the screen with all the code in it.
which does this:

[demo@mail mailcow-dockerized]$ sudo ./netfilter.sh
[sudo] password for demo:
insmod /lib/modules/6.6.16-1-lts/kernel/net/ipv6/netfilter/ip6_tables.ko.zst
insmod /lib/modules/6.6.16-1-lts/kernel/net/ipv6/netfilter/ip6table_filter.ko.zst
[+] Restarting 1/1
 ✔ Container mailcowdockerized-netfilter-mailcow-1  Started                                                                                                  0.8s

This is what is in the script:

#!/bin/bash

sudo modprobe -v ip6table_filter
sudo modprobe -v iptable_filter
sudo docker-compose restart netfilter-mailcow

Running that now causes the issue.
The web page errors out with the redis error.
Postfix seems to still be working at the moment but I expect it to fail at some point with a timeout error.
Sorry for the runaround on this . I am trying to systematically test it.
I now have to restart to get the web page back.
I hope this helps.

postfix just crashed

postfix-mailcow-1  | Feb  6 12:08:31 2bb078433cad postfix/master[378]: warning: process /usr/lib/postfix/sbin/postscreen pid 974 exit status 1
postfix-mailcow-1  | Feb  6 12:08:31 2bb078433cad postfix/master[378]: warning: /usr/lib/postfix/sbin/postscreen: bad command startup -- throttling
postfix-mailcow-1  | Feb  6 12:05:21 2bb078433cad syslog-ng[9]: REDIS server error, suspending; driver='d_redis_f2b_channel#0', command='PUBLISH "F2B_CHANNEL" "warning: hostname apzg-0720c-035.stretchoid.com does not resolve to address 192.241.208.64"', error='Connection reset by peer', time_reopen='60'
postfix-mailcow-1  | Feb  6 12:05:21 2bb078433cad syslog-ng[9]: Error occurred while trying to send a message, trying again; driver='d_redis_f2b_channel#0', location='/etc/syslog-ng/syslog-ng.conf:27:3', worker_index='0', retries='1', time_reopen='60', batch_size='1'
postfix-mailcow-1  | Feb  6 12:05:21 2bb078433cad syslog-ng[9]: REDIS server error, suspending; driver='d_redis_ui_log#0', command='LPUSH "POSTFIX_MAILLOG" "{\"time\":\"1707239121\",\"program\":\"postfix/submission/smtpd\",\"priority\":\"warning\",\"message\":\"warning: hostname apzg-0720c-035.stretchoid.com does not resolve to address 192.241.208.64\"}\n"', error='Connection reset by peer', time_reopen='60'
postfix-mailcow-1  | Feb  6 12:05:21 2bb078433cad syslog-ng[9]: Error occurred while trying to send a message, trying again; driver='d_redis_ui_log#0', location='/etc/syslog-ng/syslog-ng.conf:19:3', worker_index='0', retries='1', time_reopen='60', batch_size='1'
postfix-mailcow-1  | Feb  6 12:09:25 2bb078433cad postfix/submission/smtpd[982]: connect from unknown[91.215.85.17]
postfix-mailcow-1  | Feb  6 12:09:26 2bb078433cad postfix/submission/smtpd[982]: discarding EHLO keywords: CHUNKING
postfix-mailcow-1  | Feb  6 12:09:26 2bb078433cad postfix/submission/smtpd[982]: Anonymous TLS connection established from unknown[91.215.85.17]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
postfix-mailcow-1  | Feb  6 12:09:26 2bb078433cad postfix/submission/smtpd[982]: discarding EHLO keywords: CHUNKING
postfix-mailcow-1  | Feb  6 12:09:29 2bb078433cad postfix/submission/smtpd[982]: warning: unknown[91.215.85.17]: SASL PLAIN authentication failed: (reason unavailable), sasl_username=administracion@dccathome.com
postfix-mailcow-1  | Feb  6 12:09:29 2bb078433cad postfix/submission/smtpd[982]: disconnect from unknown[91.215.85.17] ehlo=2 starttls=1 auth=0/1 quit=1 unknown=0/1 commands=4/6
postfix-mailcow-1  | Feb  6 12:09:51 2bb078433cad syslog-ng[9]: REDIS server error during connection; driver='d_redis_ui_log#0', error='Connection timed out', time_reopen='60'
postfix-mailcow-1  | Feb  6 12:09:51 2bb078433cad syslog-ng[9]: REDIS server error during connection; driver='d_redis_f2b_channel#0', error='Connection timed out', time_reopen='60'
postfix-mailcow-1  | Feb  6 12:10:21 2bb078433cad whitelist_forwardinghosts: Look up 193.222.96.141 on whitelist, result <html>
postfix-mailcow-1  | Feb  6 12:10:21 2bb078433cad syslog-ng[9]: Error processing log message: <head><title>504 Gateway Time-out</title></head>
postfix-mailcow-1  | <body>
postfix-mailcow-1  | <center><h1>504 Gateway Time-out</h1></center>
postfix-mailcow-1  | <hr><center>nginx/1.25.3</center>
postfix-mailcow-1  | </body>
postfix-mailcow-1  | </html>
postfix-mailcow-1  | submission/smtpd[959]: improper command pipelining after CONNECT from unknown[192.241.208.64]: EHLO apzg-0720c-035\r\n>@<
postfix-mailcow-1  | <head><title>504 Gateway Time-out</title></head>
postfix-mailcow-1  | Feb  6 12:10:21 2bb078433cad syslog-ng[9]: Error processing log message: <body>
postfix-mailcow-1  | <center><h1>504 Gateway Time-out</h1></center>
postfix-mailcow-1  | <hr><center>nginx/1.25.3</center>
postfix-mailcow-1  | </body>
postfix-mailcow-1  | </html>
postfix-mailcow-1  | submission/smtpd[959]: improper command pipelining after CONNECT from unknown[192.241.208.64]: EHLO apzg-0720c-035\r\n>@<
postfix-mailcow-1  | <body>
postfix-mailcow-1  | Feb  6 12:10:21 2bb078433cad syslog-ng[9]: Error processing log message: <center><h1>504 Gateway Time-out</h1></center>
postfix-mailcow-1  | <hr><center>nginx/1.25.3</center>
postfix-mailcow-1  | </body>
postfix-mailcow-1  | </html>
postfix-mailcow-1  | submission/smtpd[959]: improper command pipelining after CONNECT from unknown[192.241.208.64]: EHLO apzg-0720c-035\r\n>@<
postfix-mailcow-1  | <center><h1>504 Gateway Time-out</h1></center>
postfix-mailcow-1  | Feb  6 12:10:21 2bb078433cad syslog-ng[9]: Error processing log message: <hr><center>nginx/1.25.3</center>
postfix-mailcow-1  | </body>
postfix-mailcow-1  | </html>
postfix-mailcow-1  | submission/smtpd[959]: improper command pipelining after CONNECT from unknown[192.241.208.64]: EHLO apzg-0720c-035\r\n>@<
postfix-mailcow-1  | <hr><center>nginx/1.25.3</center>
postfix-mailcow-1  | Feb  6 12:10:21 2bb078433cad syslog-ng[9]: Error processing log message: </body>
postfix-mailcow-1  | </html>
postfix-mailcow-1  | submission/smtpd[959]: improper command pipelining after CONNECT from unknown[192.241.208.64]: EHLO apzg-0720c-035\r\n>@<
postfix-mailcow-1  | </body>
postfix-mailcow-1  | Feb  6 12:10:21 2bb078433cad syslog-ng[9]: Error processing log message: </html>
postfix-mailcow-1  | submission/smtpd[959]: improper command pipelining after CONNECT from unknown[192.241.208.64]: EHLO apzg-0720c-035\r\n>@<
postfix-mailcow-1  | </html>

DocFraggle

You are still using “docker-compose” instead of “docker compose”!
If I wasn’t clear enough before:

“docker-compose” is the old standalone version which doesn’t work with the latest changes in some of the containers.

“docker compose” uses the native version. So change your script to:

#!/bin/bash

sudo modprobe -v ip6table_filter
sudo modprobe -v iptable_filter
sudo docker compose restart netfilter-mailcow

and give it a try (even if I still don’t understand why that is because in your case…)

maybl8

I changed it and still the same issue.

DocFraggle

Did you try restarting everything?

docker compose down
docker compose up -d

maybl8

I ran the ./netfilter script.
Which crashed the webpage and postfix.
Ran the docker compose down and up
This is what shows on the web page and postfix

What is happening?
Please do not stop the stack while we are initializing the database or do other preparations.

What is happening? - Nginx cannot connect to an upstream server or other services are not ready yet.
This is fine if mailcow was just installed or updated and can take a few minutes to complete.
Please check the logs or contact support if the error persists.

Quick debugging
Check Nginx and PHP logs:

docker compose logs --tail=200 php-fpm-mailcow nginx-mailcow
Make sure your SQL credentials in mailcow.conf (a link to .env) do fit your initialized SQL volume. If you see an access denied, you might have the wrong mailcow.conf:

source mailcow.conf ; docker compose exec mysql-mailcow mysql -u${DBUSER} -p${DBPASS} ${DBNAME}
In case of a previous failed installation, create a backup of your existing data, followed by removing all volumes and starting over (NEVER do this with a production system, it will remove ALL data):

BACKUP_LOCATION=/tmp/ ./helper-scripts/backup_and_restore.sh backup all
docker compose down --volumes ; docker compose up -d
Make sure your timezone is correct. Use "America/New_York" for example, do not use spaces. Check here for a list.


Click to learn more about getting support.

[demo@mail mailcow-dockerized]$ sudo docker compose logs -f --tail=200 postfix-mailcow
postfix-mailcow-1  | 2024-02-06 13:06:58,718 INFO Set uid to user 0 succeeded
postfix-mailcow-1  | 2024-02-06 13:06:58,719 INFO supervisord started with pid 1
postfix-mailcow-1  | 2024-02-06 13:06:59,724 INFO spawned: 'processes' with pid 8
postfix-mailcow-1  | 2024-02-06 13:06:59,728 INFO spawned: 'postfix' with pid 9
postfix-mailcow-1  | 2024-02-06 13:06:59,732 INFO spawned: 'syslog-ng' with pid 10
postfix-mailcow-1  | Uptime: 37  Threads: 7  Questions: 246  Slow queries: 0  Opens: 40  Open tables: 31  Queries per second avg: 6.648
postfix-mailcow-1  | Feb  6 13:06:59 e4b420c1ecc5 syslog-ng[10]: syslog-ng starting up; version='3.28.1'
postfix-mailcow-1  | Checking if ASN for your IP is listed for Spamhaus Bad ASN List...
postfix-mailcow-1  | 2024-02-06 13:07:01,049 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1  | 2024-02-06 13:07:01,049 INFO success: postfix entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1  | 2024-02-06 13:07:01,049 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1  | The AS of your IP is NOT listed as a banned AS from Spamhaus!
postfix-mailcow-1  | Using the open Spamhaus blocklists.
postfix-mailcow-1  | chown: cannot access '/usr/share/man/man1/mailq.1.gz': No such file or directory
postfix-mailcow-1  | Feb  6 13:07:04 e4b420c1ecc5 postfix/postfix-script[376]: starting the Postfix mail system
postfix-mailcow-1  | Feb  6 13:07:04 e4b420c1ecc5 postfix/master[378]: daemon started -- version 3.5.23, configuration /opt/postfix/conf
postfix-mailcow-1  | Feb  6 13:06:59 e4b420c1ecc5 syslog-ng[10]: REDIS server error during connection; driver='d_redis_f2b_channel#0', error='Connection timed out', time_reopen='60'
postfix-mailcow-1  | Feb  6 13:06:59 e4b420c1ecc5 syslog-ng[10]: REDIS server error during connection; driver='d_redis_ui_log#0', error='Connection timed out', time_reopen='60'
postfix-mailcow-1  | Feb  6 13:08:09 e4b420c1ecc5 syslog-ng[10]: REDIS server error during connection; driver='d_redis_f2b_channel#0', error='Connection timed out', time_reopen='60'
postfix-mailcow-1  | Feb  6 13:08:09 e4b420c1ecc5 syslog-ng[10]: REDIS server error during connection; driver='d_redis_ui_log#0', error='Connection timed out', time_reopen='60'
postfix-mailcow-1  | Feb  6 13:09:19 e4b420c1ecc5 syslog-ng[10]: REDIS server error during connection; driver='d_redis_ui_log#0', error='Connection timed out', time_reopen='60'
postfix-mailcow-1  | Feb  6 13:09:19 e4b420c1ecc5 syslog-ng[10]: REDIS server error during connection; driver='d_redis_f2b_channel#0', error='Connection timed out', time_reopen='60'
[code]



Thanks for sticking with me on this.
I really appreciate it.

DocFraggle

Did you wait until all containers were completely shut down before starting them up again?

maybl8

yes
I’ll try it again and post results

[demo@mail mailcow-dockerized]$ sudo docker compose down
[sudo] password for demo:
[+] Running 18/18
[+] Running 18/19cowdockerized-rspamd-mailcow-1     Removed                                                                                                     3.5s
[+] Running 18/19cowdockerized-rspamd-mailcow-1     Removed                                                                                                     3.5s
[+] Running 19/19cowdockerized-rspamd-mailcow-1     Removed                                                                                                     3.5s
 ✔ Container mailcowdockerized-rspamd-mailcow-1     Removed                                                                                                     3.5s
 ✔ Container mailcowdockerized-solr-mailcow-1       Removed                                                                                                     2.7s
 ✔ Container mailcowdockerized-watchdog-mailcow-1   Removed                                                                                                     2.2s
 ✔ Container mailcowdockerized-olefy-mailcow-1      Removed                                                                                                    11.2s
 ✔ Container mailcowdockerized-dockerapi-mailcow-1  Removed                                                                                                     4.1s
 ✔ Container mailcowdockerized-clamd-mailcow-1      Removed                                                                                                     1.4s
 ✔ Container mailcowdockerized-memcached-mailcow-1  Removed                                                                                                     3.2s
 ✔ Container mailcowdockerized-ofelia-mailcow-1     Removed                                                                                                    11.5s
 ✔ Container mailcowdockerized-postfix-mailcow-1    Removed                                                                                                     2.9s
 ✔ Container mailcowdockerized-acme-mailcow-1       Removed                                                                                                     1.9s
 ✔ Container mailcowdockerized-nginx-mailcow-1      Removed                                                                                                    10.9s
 ✔ Container mailcowdockerized-dovecot-mailcow-1    Removed                                                                                                     7.8s
 ✔ Container mailcowdockerized-php-fpm-mailcow-1    Removed                                                                                                     0.7s
 ✔ Container mailcowdockerized-sogo-mailcow-1       Removed                                                                                                    10.9s
 ✔ Container mailcowdockerized-redis-mailcow-1      Removed                                                                                                     1.3s
 ✔ Container mailcowdockerized-mysql-mailcow-1      Removed                                                                                                     1.2s
 ✔ Container mailcowdockerized-netfilter-mailcow-1  Removed                                                                                                     0.8s
 ✔ Container mailcowdockerized-unbound-mailcow-1    Removed                                                                                                     1.1s
 ✔ Network mailcowdockerized_mailcow-network        Removed                                                                                                     0.2s

I can’t get the up results pasted in here.
It just spins and nothing shows up.

Still have the issue after doing this.

DocFraggle

You can try to run the update.sh script again… if that still doesn’t help stop all containers, reboot the server and try again.

Very strange…

maybl8

Ran update.sh again.
Didn’t reboot yet.

Got this when I ran the netfilter log

[demo@mail mailcow-dockerized]$ sudo docker compose logs --tail=200  netfilter-mailcow
[sudo] password for demo:
netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Initializing mailcow netfilter chain
netfilter-mailcow-1  | Setting MAILCOW isolation
netfilter-mailcow-1  | Error 113 connecting to 172.22.1.249:6379. Host is unreachable. - trying again in 3 seconds
netfilter-mailcow-1  | Watching Redis channel F2B_CHANNEL

Different error but seems to be running.

maybl8

Everything is working fine right now.
I am going to mark this solved.
I am going to install this update 2024-01e.

« Previous Page