Closed ghost closed 10 months ago
Try restarting the complete stack
Hello @DerLinkman,
Thanks for your suggestion. I opened the bug report after restarting the server itself. As far as I know, all the stack is properly restarted as well at reboot, no?
Hi!
Theoretically it should but with restart I mean down and up the stack.
I think this "issue" is produced by the docker api which is registering all containers on boot.
Okay, you were right. A simple sudo systemctl reboot
isn't enough to restart the stack properly.
After doing the following:
$ cd /opt/mailcow-dockerized/
/opt/mailcow-dockerized$ sudo docker-compose down
[+] Running 19/19
⠿ Container mailcowdockerized-clamd-mailcow-1 Removed 0.3s
⠿ Container mailcowdockerized-olefy-mailcow-1 Removed 10.2s
⠿ Container mailcowdockerized-ofelia-mailcow-1 Removed 0.6s
⠿ Container mailcowdockerized-rspamd-mailcow-1 Removed 1.5s
⠿ Container mailcowdockerized-dockerapi-mailcow-1 Removed 1.4s
⠿ Container mailcowdockerized-netfilter-mailcow-1 Removed 1.2s
⠿ Container mailcowdockerized-solr-mailcow-1 Removed 1.2s
⠿ Container mailcowdockerized-memcached-mailcow-1 Removed 1.3s
⠿ Container mailcowdockerized-watchdog-mailcow-1 Removed 0.6s
⠿ Container mailcowdockerized-acme-mailcow-1 Removed 0.3s
⠿ Container mailcowdockerized-nginx-mailcow-1 Removed 0.9s
⠿ Container mailcowdockerized-postfix-mailcow-1 Removed 2.4s
⠿ Container mailcowdockerized-dovecot-mailcow-1 Removed 2.3s
⠿ Container mailcowdockerized-php-fpm-mailcow-1 Removed 0.3s
⠿ Container mailcowdockerized-sogo-mailcow-1 Removed 10.3s
⠿ Container mailcowdockerized-redis-mailcow-1 Removed 0.5s
⠿ Container mailcowdockerized-mysql-mailcow-1 Removed 0.6s
⠿ Container mailcowdockerized-unbound-mailcow-1 Removed 0.2s
⠿ Network mailcowdockerized_mailcow-network Removed 0.2s
/opt/mailcow-dockerized$ sudo docker-compose up -d
[+] Running 19/19
⠿ Network mailcowdockerized_mailcow-network Created 0.1s
⠿ Container mailcowdockerized-solr-mailcow-1 Started 1.7s
⠿ Container mailcowdockerized-memcached-mailcow-1 Started 2.2s
⠿ Container mailcowdockerized-unbound-mailcow-1 Healthy 31.7s
⠿ Container mailcowdockerized-dockerapi-mailcow-1 Started 2.1s
⠿ Container mailcowdockerized-redis-mailcow-1 Started 2.5s
⠿ Container mailcowdockerized-olefy-mailcow-1 Started 1.8s
⠿ Container mailcowdockerized-sogo-mailcow-1 Started 1.6s
⠿ Container mailcowdockerized-php-fpm-mailcow-1 Started 3.1s
⠿ Container mailcowdockerized-mysql-mailcow-1 Started 2.7s
⠿ Container mailcowdockerized-clamd-mailcow-1 Started 32.2s
⠿ Container mailcowdockerized-nginx-mailcow-1 Started 4.5s
⠿ Container mailcowdockerized-postfix-mailcow-1 Started 32.2s
⠿ Container mailcowdockerized-dovecot-mailcow-1 Started 4.6s
⠿ Container mailcowdockerized-acme-mailcow-1 Started 31.9s
⠿ Container mailcowdockerized-rspamd-mailcow-1 Started 5.8s
⠿ Container mailcowdockerized-netfilter-mailcow-1 Started 32.3s
⠿ Container mailcowdockerized-ofelia-mailcow-1 Started 5.6s
⠿ Container mailcowdockerized-watchdog-mailcow-1 Started 32.5s
It shows up as expected on the web interface:
Thanks a lot for your help! 🙏🏻
Contribution guidelines
I've found a bug and checked that ...
Description
Hello,
For some time I tried disabling Clamd container on my Mailcow instances. I wanted to study the virtual memory usage and do some benchmarks.
Today, I enabled it again by modifying
mailcow.conf
, switching fromSKIP_CLAMD=y
toSKIP_CLAMD=n
:The container seems to be running just fine:
However, it doesn't show up on the
/debug
web interface page:Logs:
Steps to reproduce:
/debug
web interfaceWhich branch are you using?
master
Operating System:
Debian 11
Server/VM specifications:
8GiB, 2 cores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
KVM
Docker version:
24.0.7
docker-compose version or docker compose version:
2.9.0
mailcow version:
2023-12a
Reverse proxy:
Not any
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: