Recently I have upgraded to 2025-02.
I have found there is no email for many hours. I have to restart the server.
I doubt if it was the IPv6 or any configuration issues.
Hence I have re-configured from scratch on another server.
The problem still exists.

I have found these tailing the postfix log:

postfix-mailcow-1  | Mar 24 22:06:14 69f8b52d9091 postfix/postscreen[2063]: CONNECT from [18.209.86.113]:20300 to [172.22.1.253]:25
postfix-mailcow-1  | Mar 24 22:06:14 69f8b52d9091 whitelist_forwardinghosts: Look up 18.209.86.113 on whitelist, result 200 DUNNO
postfix-mailcow-1  | Mar 24 22:06:14 69f8b52d9091 postfix/dnsblog[2077]: addr 18.209.86.113 listed by domain list.dnswl.org as 127.0.3.1
postfix-mailcow-1  | Mar 24 22:06:14 69f8b52d9091 postfix/dnsblog[2078]: addr 18.209.86.113 listed by domain hostkarma.junkemailfilter.com as 127.0.0.1
postfix-mailcow-1  | Mar 24 22:06:14 69f8b52d9091 postfix/dnsblog[2078]: addr 18.209.86.113 listed by domain hostkarma.junkemailfilter.com as 127.0.1.1
postfix-mailcow-1  | Mar 24 22:06:16 69f8b52d9091 postfix/postscreen[2063]: PASS OLD [18.209.86.113]:20300
postfix-mailcow-1  | Mar 24 22:06:16 69f8b52d9091 postfix/smtpd[2047]: connect from keeper-us-east-1d.mxtoolbox.com[18.209.86.113]
postfix-mailcow-1  | Mar 24 22:06:17 69f8b52d9091 postfix/smtpd[2047]: NOQUEUE: reject: RCPT from keeper-us-east-1d.mxtoolbox.com[18.209.86.113]: 454 4.7.1 <test@mxtoolboxsmtpdiag.com>: Relay access denied; from=<supertool@mxtoolboxsmtpdiag.com> to=<test@mxtoolboxsmtpdiag.com> proto=ESMTP helo=<keeper-us-east-1d.mxtoolbox.com>
postfix-mailcow-1  | Mar 24 22:06:18 69f8b52d9091 postfix/smtpd[2047]: disconnect from keeper-us-east-1d.mxtoolbox.com[18.209.86.113] ehlo=1 mail=1 rcpt=0/1 quit=1 commands=3/4
postfix-mailcow-1  | 2025-03-24 22:08:59,497 WARN received SIGTERM indicating exit request
postfix-mailcow-1  | 2025-03-24 22:08:59,532 INFO waiting for processes, postfix, syslog-ng to die
postfix-mailcow-1  | Mar 24 22:08:59 69f8b52d9091 syslog-ng[10]: syslog-ng shutting down; version='3.38.1'
postfix-mailcow-1  | 2025-03-24 22:08:59,723 INFO stopped: syslog-ng (exit status 0)
postfix-mailcow-1  | 2025-03-24 22:09:00,749 WARN stopped: postfix (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 364 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 367 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 368 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 371 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 1969 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 1973 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 2028 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 2039 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 2049 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 2061 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 2067 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,750 INFO reaped unknown pid 2085 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,751 INFO reaped unknown pid 2089 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,751 INFO reaped unknown pid 2092 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-24 22:09:00,751 WARN received SIGQUIT indicating exit request
postfix-mailcow-1  | 2025-03-24 22:09:00,754 WARN stopped: processes (terminated by SIGTERM)

I have no idea who had sent the SIGTERM.
Even if there is restart policy the container is stopped.

Thanks.

  • EETNyx

      Moolevel 50
    • Post #2

    Usually this is nothing to be worried about. Best guess is new or renewal certificate, so compare those SIGTERM times to logs in acme container, most likely you will see match,..

      Have something to say?

      Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

      ETNyx since that sigterm, the container has stopped for many hours, until my manual restart

        ETNyx I have not modified the default docker compose file. it has always restart policy.
        Grok says restart policy applies to accidential exit only. SIGTERM is an intentional one so it won’t restart.

          Sorry, I did read it in a wrong way,.. anyway you should search your logs,.. I know it’s hard, you need to correlate many services,… for example I can track similar event like you when acme-mailcow log
          Tue Mar 18 14:52:00 CET 2025 - Certificate successfully obtained` services are restarted including postfix
          multiple lines just like you
          2025-03-18 14:52:06,849 INFO reaped unknown pid 379 (terminated by SIGTERM)
          and than via dockerapi-mailcow container
          INFO: 172.22.1.9:54004 - "POST /containers/e5cbfb285de9bf50bb46f3ff13f4afe8a276ffd2f5aabbd29817bd907d0ef1dd/restart HTTP/1.1" 200 OK
          and next from postfix restart,…

          2025-03-18 14:52:09,264 INFO Set uid to user 0 succeeded
2025-03-18 14:52:10,272 INFO spawned: 'postfix' with pid 9
...

          unless you find something I do not think we will be able to help,..

            ETNyx okay i am keeping an eye on the containers now. thanks.

              Postfix has just died. I have found something might be related.

              postfix-mailcow-1  | Mar 25 21:19:30 69f8b52d9091 postfix/qmgr[367]: 46B0120061: from=<watchdog@invalid>, size=274, nrcpt=1 (queue active)
postfix-mailcow-1  | Mar 25 21:19:30 69f8b52d9091 postfix/qmgr[367]: 46B0120061: removed
postfix-mailcow-1  | Mar 25 21:19:39 69f8b52d9091 postfix/postscreen[430]: CONNECT from [18.209.86.113]:40094 to [172.22.1.253]:25
postfix-mailcow-1  | Mar 25 21:19:39 69f8b52d9091 whitelist_forwardinghosts: Look up 18.209.86.113 on whitelist, result 200 DUNNO
postfix-mailcow-1  | Mar 25 21:19:40 69f8b52d9091 postfix/dnsblog[447]: addr 18.209.86.113 listed by domain hostkarma.junkemailfilter.com as 127.0.1.1
postfix-mailcow-1  | Mar 25 21:19:40 69f8b52d9091 postfix/dnsblog[447]: addr 18.209.86.113 listed by domain hostkarma.junkemailfilter.com as 127.0.0.1
postfix-mailcow-1  | Mar 25 21:19:40 69f8b52d9091 postfix/dnsblog[437]: addr 18.209.86.113 listed by domain list.dnswl.org as 127.0.3.1
postfix-mailcow-1  | Mar 25 21:19:41 69f8b52d9091 postfix/postscreen[430]: PASS OLD [18.209.86.113]:40094
postfix-mailcow-1  | Mar 25 21:19:41 69f8b52d9091 postfix/smtpd[448]: connect from keeper-us-east-1d.mxtoolbox.com[18.209.86.113]
postfix-mailcow-1  | Mar 25 21:19:42 69f8b52d9091 postfix/smtpd[448]: NOQUEUE: reject: RCPT from keeper-us-east-1d.mxtoolbox.com[18.209.86.113]: 454 4.7.1 <test@mxtoolboxsmtpdiag.com>: Relay access denied; from=<supertool@mxtoolboxsmtpdiag.com> to=<test@mxtoolboxsmtpdiag.com> proto=ESMTP helo=<keeper-us-east-1d.mxtoolbox.com>
postfix-mailcow-1  | Mar 25 21:19:43 69f8b52d9091 postfix/smtpd[448]: disconnect from keeper-us-east-1d.mxtoolbox.com[18.209.86.113] ehlo=1 mail=1 rcpt=0/1 quit=1 commands=3/4
postfix-mailcow-1  | 2025-03-25 21:21:15,881 WARN received SIGTERM indicating exit request
postfix-mailcow-1  | 2025-03-25 21:21:15,913 INFO waiting for processes, postfix, syslog-ng to die
postfix-mailcow-1  | Mar 25 21:21:15 69f8b52d9091 syslog-ng[10]: syslog-ng shutting down; version='3.38.1'
postfix-mailcow-1  | 2025-03-25 21:21:16,092 INFO stopped: syslog-ng (exit status 0)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 WARN stopped: postfix (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 364 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 433 (exit status 0)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 365 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 367 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 368 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 369 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 372 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 375 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 376 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 417 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 422 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,141 INFO reaped unknown pid 425 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,143 INFO reaped unknown pid 430 (exit status 0)
postfix-mailcow-1  | 2025-03-25 21:21:17,143 INFO reaped unknown pid 431 (exit status 0)
postfix-mailcow-1  | 2025-03-25 21:21:17,144 INFO reaped unknown pid 432 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,145 INFO reaped unknown pid 437 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,146 INFO reaped unknown pid 438 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,146 INFO reaped unknown pid 439 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,147 INFO reaped unknown pid 440 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,147 INFO reaped unknown pid 441 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,148 INFO reaped unknown pid 442 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,148 INFO reaped unknown pid 443 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,148 INFO reaped unknown pid 444 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,148 INFO reaped unknown pid 445 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,149 INFO reaped unknown pid 446 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,150 INFO reaped unknown pid 447 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,150 INFO reaped unknown pid 448 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,151 INFO reaped unknown pid 451 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,151 INFO reaped unknown pid 454 (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,151 INFO reaped unknown pid 466 (exit status 0)
postfix-mailcow-1  | 2025-03-25 21:21:17,155 WARN stopped: processes (terminated by SIGTERM)
postfix-mailcow-1  | 2025-03-25 21:21:17,156 INFO reaped unknown pid 467 (exit status 1)
postfix-mailcow-1 exited with code 0
              # docker compose ps -a
NAME                                    IMAGE                            COMMAND                  SERVICE             CREATED        STATUS                      PORTS
mailcowdockerized-acme-mailcow-1        ghcr.io/mailcow/acme:1.91        "/sbin/tini -g -- /s…"   acme-mailcow        31 hours ago   Up 31 hours                 
mailcowdockerized-clamd-mailcow-1       ghcr.io/mailcow/clamd:1.70       "/sbin/tini -g -- /c…"   clamd-mailcow       31 hours ago   Up 31 hours (healthy)       
mailcowdockerized-dockerapi-mailcow-1   ghcr.io/mailcow/dockerapi:2.10   "/bin/sh /app/docker…"   dockerapi-mailcow   31 hours ago   Up 31 hours                 
mailcowdockerized-dovecot-mailcow-1     ghcr.io/mailcow/dovecot:2.31     "/docker-entrypoint.…"   dovecot-mailcow     31 hours ago   Up 30 hours                 0.0.0.0:110->110/tcp, [::]:110->110/tcp, 0.0.0.0:143->143/tcp, [::]:143->143/tcp, 0.0.0.0:993->993/tcp, [::]:993->993/tcp, 0.0.0.0:995->995/tcp, [::]:995->995/tcp, 0.0.0.0:4190->4190/tcp, [::]:4190->4190/tcp, 127.0.0.1:19991->12345/tcp
mailcowdockerized-memcached-mailcow-1   memcached:alpine                 "docker-entrypoint.s…"   memcached-mailcow   31 hours ago   Up 31 hours                 11211/tcp
mailcowdockerized-mysql-mailcow-1       mariadb:10.11                    "docker-entrypoint.s…"   mysql-mailcow       31 hours ago   Up 31 hours                 127.0.0.1:13306->3306/tcp
mailcowdockerized-netfilter-mailcow-1   ghcr.io/mailcow/netfilter:1.61   "/bin/sh -c /app/doc…"   netfilter-mailcow   31 hours ago   Up 13 hours                 
mailcowdockerized-nginx-mailcow-1       ghcr.io/mailcow/nginx:1.03       "/docker-entrypoint.…"   nginx-mailcow       31 hours ago   Up 31 hours                 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp
mailcowdockerized-ofelia-mailcow-1      mcuadros/ofelia:latest           "/usr/bin/ofelia dae…"   ofelia-mailcow      31 hours ago   Up 31 hours                 
mailcowdockerized-olefy-mailcow-1       ghcr.io/mailcow/olefy:1.13       "python3 -u /app/ole…"   olefy-mailcow       31 hours ago   Up 31 hours                 
mailcowdockerized-php-fpm-mailcow-1     ghcr.io/mailcow/phpfpm:1.92      "/docker-entrypoint.…"   php-fpm-mailcow     31 hours ago   Up 31 hours                 9000/tcp
mailcowdockerized-postfix-mailcow-1     ghcr.io/mailcow/postfix:1.80     "/docker-entrypoint.…"   postfix-mailcow     31 hours ago   Exited (0) 23 minutes ago   
mailcowdockerized-redis-mailcow-1       redis:7.4.2-alpine               "/bin/sh /redis-conf…"   redis-mailcow       31 hours ago   Up 31 hours                 127.0.0.1:7654->6379/tcp
mailcowdockerized-rspamd-mailcow-1      ghcr.io/mailcow/rspamd:2.0       "/docker-entrypoint.…"   rspamd-mailcow      31 hours ago   Up 31 hours                 
mailcowdockerized-sogo-mailcow-1        ghcr.io/mailcow/sogo:1.129       "/docker-entrypoint.…"   sogo-mailcow        31 hours ago   Up 31 hours                 
mailcowdockerized-unbound-mailcow-1     ghcr.io/mailcow/unbound:1.23     "/docker-entrypoint.…"   unbound-mailcow     31 hours ago   Up 31 hours (healthy)       53/tcp, 53/udp
mailcowdockerized-watchdog-mailcow-1    ghcr.io/mailcow/watchdog:2.06    "/watchdog.sh"           watchdog-mailcow    31 hours ago   Up 31 hours
              dockerapi-mailcow-1  | INFO:     172.22.1.6:53174 - "GET /containers/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     api call: container_post__exec__system__df, container_id: 722fc21505165b1d5e91d3849c2085366709352b43b081d456c14cd73b7987f5
dockerapi-mailcow-1  | INFO:     172.22.1.6:53180 - "POST /containers/722fc21505165b1d5e91d3849c2085366709352b43b081d456c14cd73b7987f5/exec HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.6:53188 - "GET /containers/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.6:53206 - "GET /host/stats HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:49386 - "GET /containers/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:49400 - "GET /containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     api call: container_post__restart, container_id: 69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e
dockerapi-mailcow-1  | ERROR:     error - container_post: 500 Server Error for http+docker://localhost/v1.48/containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/restart?t=10: Internal Server Error ("Cannot restart container 69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e: tried to kill container, but did not receive an exit event")
dockerapi-mailcow-1  | INFO:     172.22.1.12:49414 - "POST /containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/restart HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:34274 - "GET /containers/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:34290 - "GET /containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     api call: container_post__restart, container_id: 69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e
dockerapi-mailcow-1  | INFO:     172.22.1.12:34304 - "POST /containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/restart HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:44426 - "GET /containers/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:44434 - "GET /containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:59426 - "GET /containers/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:59438 - "GET /containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     api call: container_post__restart, container_id: 69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e
dockerapi-mailcow-1  | INFO:     172.22.1.12:59448 - "POST /containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/restart HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:33524 - "GET /containers/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     172.22.1.12:33530 - "GET /containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/json HTTP/1.1" 200 OK
dockerapi-mailcow-1  | INFO:     api call: container_post__restart, container_id: 69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e
dockerapi-mailcow-1  | INFO:     172.22.1.12:33532 - "POST /containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/restart HTTP/1.1" 200 OK
dockerapi-mailcow-1  | ERROR:     error - container_post: 500 Server Error for http+docker://localhost/v1.48/containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/restart?t=10: Internal Server Error ("Cannot restart container 69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e: tried to kill container, but did not receive an exit event")
dockerapi-mailcow-1  | INFO:     172.22.1.12:52624 - "GET /containers/json HTTP/1.1" 200 OK
              watchdog-mailcow-1  | Tue Mar 25 21:16:34 HKT 2025 Postfix health level: 100% (8/8), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:16:38 HKT 2025 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:16:47 HKT 2025 Dovecot health level: 100% (12/12), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:16:51 HKT 2025 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:16:56 HKT 2025 Redis health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:01 HKT 2025 Nginx health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:02 HKT 2025 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:02 HKT 2025 MySQL/MariaDB health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:07 HKT 2025 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:11 HKT 2025 Olefy health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:13 HKT 2025 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:14 HKT 2025 Postfix health level: 100% (8/8), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:19 HKT 2025 SOGo health level: 100% (3/3), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:21 HKT 2025 Rspamd health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:29 HKT 2025 PHP-FPM health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:35 HKT 2025 Dovecot health level: 100% (12/12), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:36 HKT 2025 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:38 HKT 2025 Mail queue health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:40 HKT 2025 Unbound health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:51 HKT 2025 Olefy health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:52 HKT 2025 PHP-FPM health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:54 HKT 2025 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:54 HKT 2025 MySQL/MariaDB health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:17:58 HKT 2025 Redis health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:01 HKT 2025 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:08 HKT 2025 Dovecot health level: 100% (12/12), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:08 HKT 2025 Rspamd health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:09 HKT 2025 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:10 HKT 2025 Nginx health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:23 HKT 2025 Postfix health level: 75% (6/8), health trend: -2
watchdog-mailcow-1  | Tue Mar 25 21:18:24 HKT 2025 SOGo health level: 100% (3/3), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:24 HKT 2025 Olefy health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:26 HKT 2025 MySQL/MariaDB health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:28 HKT 2025 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:29 HKT 2025 PHP-FPM health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:36 HKT 2025 Rspamd health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:36 HKT 2025 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:37 HKT 2025 Nginx health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:39 HKT 2025 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:43 HKT 2025 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:51 HKT 2025 Unbound health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:56 HKT 2025 Mail queue health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:18:58 HKT 2025 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:04 HKT 2025 Postfix health level: 50% (4/8), health trend: -2
watchdog-mailcow-1  | Tue Mar 25 21:19:07 HKT 2025 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:08 HKT 2025 MySQL/MariaDB health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:10 HKT 2025 SOGo health level: 100% (3/3), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:12 HKT 2025 Dovecot health level: 100% (12/12), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:12 HKT 2025 Redis health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:21 HKT 2025 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:28 HKT 2025 PHP-FPM health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:31 HKT 2025 Rspamd health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:33 HKT 2025 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:37 HKT 2025 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:40 HKT 2025 Olefy health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:44 HKT 2025 Nginx health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:47 HKT 2025 Dovecot health level: 100% (12/12), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:47 HKT 2025 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:48 HKT 2025 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:19:48 HKT 2025 Unbound health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:02 HKT 2025 MySQL/MariaDB health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:09 HKT 2025 PHP-FPM health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:09 HKT 2025 Mail queue health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:13 HKT 2025 Redis health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:21 HKT 2025 Nginx health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:22 HKT 2025 MySQL/MariaDB health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:23 HKT 2025 Primary certificate expiry check health level: 100% (7/7), health trend: 1
watchdog-mailcow-1  | Tue Mar 25 21:20:24 HKT 2025 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:26 HKT 2025 Postfix health level: 25% (2/8), health trend: -2
watchdog-mailcow-1  | Tue Mar 25 21:20:29 HKT 2025 Olefy health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:29 HKT 2025 SOGo health level: 100% (3/3), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:38 HKT 2025 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:38 HKT 2025 Dovecot health level: 100% (12/12), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:43 HKT 2025 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:44 HKT 2025 Unbound health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:44 HKT 2025 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:50 HKT 2025 Rspamd health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:58 HKT 2025 Dovecot health level: 100% (12/12), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:20:59 HKT 2025 Postfix health level: 0% (0/8), health trend: -2
watchdog-mailcow-1  | Tue Mar 25 21:21:00 HKT 2025 Postfix hit error limit
watchdog-mailcow-1  | SMTP OK - 0.164 sec. response time|time=0.164184s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.029 sec. response time|time=0.029281s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.225 sec. response time|time=0.224522s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.023 sec. response time|time=0.023008s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.212 sec. response time|time=0.212446s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.064 sec. response time|time=0.063629s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.224 sec. response time|time=0.223849s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.023 sec. response time|time=0.022754s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.333 sec. response time|time=0.333107s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.023 sec. response time|time=0.022729s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.548 sec. response time|time=0.548482s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.028 sec. response time|time=0.027928s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.102 sec. response time|time=0.102014s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.020 sec. response time|time=0.020036s;;;0.000000
watchdog-mailcow-1  | CRITICAL - Socket timeout
watchdog-mailcow-1  | SMTP OK - 0.101 sec. response time|time=0.100947s;;;0.000000
watchdog-mailcow-1  | CRITICAL - Socket timeout
watchdog-mailcow-1  | SMTP OK - 0.050 sec. response time|time=0.049916s;;;0.000000
watchdog-mailcow-1  | CRITICAL - Socket timeout
watchdog-mailcow-1  | SMTP OK - 0.072 sec. response time|time=0.072220s;;;0.000000
watchdog-mailcow-1  | CRITICAL - Socket timeout
watchdog-mailcow-1  | SMTP OK - 0.066 sec. response time|time=0.066307s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 2.764 sec. response time|time=2.764021s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.034 sec. response time|time=0.033901s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.220 sec. response time|time=0.219620s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.021 sec. response time|time=0.020874s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.522 sec. response time|time=0.522105s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.046 sec. response time|time=0.045717s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.570 sec. response time|time=0.570313s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.026 sec. response time|time=0.025993s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.274 sec. response time|time=0.274228s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.021 sec. response time|time=0.021013s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.546 sec. response time|time=0.546285s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.024 sec. response time|time=0.024130s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.232 sec. response time|time=0.231943s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.021 sec. response time|time=0.021115s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.383 sec. response time|time=0.382895s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.023 sec. response time|time=0.022670s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.796 sec. response time|time=0.795506s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.023 sec. response time|time=0.023328s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.285 sec. response time|time=0.284931s;;;0.000000
watchdog-mailcow-1  | SMTP OK - 0.023 sec. response time|time=0.023133s;;;0.000000
watchdog-mailcow-1  | CRITICAL - Socket timeout
watchdog-mailcow-1  | SMTP OK - 0.083 sec. response time|time=0.082901s;;;0.000000
watchdog-mailcow-1  | CRITICAL - Socket timeout
watchdog-mailcow-1  | SMTP OK - 0.049 sec. response time|time=0.048981s;;;0.000000
watchdog-mailcow-1  | CRITICAL - Socket timeout
watchdog-mailcow-1  | SMTP OK - 0.021 sec. response time|time=0.020865s;;;0.000000
watchdog-mailcow-1  | CRITICAL - Socket timeout
watchdog-mailcow-1  | SMTP OK - 0.344 sec. response time|time=0.343581s;;;0.000000
watchdog-mailcow-1  | Tue Mar 25 21:21:12 HKT 2025 Sending restart command to 69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e...
watchdog-mailcow-1  | {
watchdog-mailcow-1  |     "type": "danger",
watchdog-mailcow-1  |     "msg": "500 Server Error for http+docker://localhost/v1.48/containers/69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e/restart?t=10: Internal Server Error (\"Cannot restart container 69f8b52d90919acd5b8313fe8d3a035ed76a1dc647d625b48dd5bad3ae29d51e: tried to kill container, but did not receive an exit event\")"
watchdog-mailcow-1  | }Tue Mar 25 21:21:36 HKT 2025 Wait for restarted container to settle and continue watching...
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Postfix health level: 50% (4/8), health trend: -4
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Mail queue health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Nginx health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Olefy health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Redis health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 SOGo health level: 100% (3/3), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 PHP-FPM health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 MySQL/MariaDB health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Dovecot health level: 100% (12/12), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Rspamd health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:12 HKT 2025 Unbound health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:34 HKT 2025 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:35 HKT 2025 Dovecot health level: 100% (12/12), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:36 HKT 2025 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:41 HKT 2025 Mail queue health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:42 HKT 2025 SOGo health level: 100% (3/3), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:22:45 HKT 2025 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:23:03 HKT 2025 SOGo health level: 100% (3/3), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:23:06 HKT 2025 Mail queue health level: 100% (20/20), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:23:07 HKT 2025 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:23:07 HKT 2025 Nginx health level: 100% (5/5), health trend: 0
watchdog-mailcow-1  | Tue Mar 25 21:23:12 HKT 2025 Postfix health level: 0% (0/8), health trend: -4

              I have read the watchdog script. It trys to connect port 587 using container IP address. The connection should work given that the postfix container is up and running. But it failed to connect and hence sending a SIGTERM and restart the container. It is strange…

              No one is typing