Waiting for schema update (on latest commit)

[snhrdt]

Prior to placing the issue, please check following: (fill out each checkbox with a X once done)

• [X] I understand that not following below instructions might result in immediate closing and deletion of my issue.
• [X] I have understood that answers are voluntary and community-driven, and not commercial support.
• [X] I have verified that my issue has not been already answered in the past. I also checked previous issues.

---

Description of the bug: What kind of issue have you exactly come across?

My issue is: I just upgraded to the latest available state of mailcow-dockerized (latest commits as of Nov 2, 2019); my last update has been a while ago.

Now, after running docker-compose up -d, I see the following line over and over in the logs:

sogo-mailcow_1 | Waiting for schema update...

Reproduction of said bug: How exactly do you reproduce the bug?

1. UPgrade to latest commit of mailcow dockerized
2. Run docker-compose up -d
3. Look at output of docker-compose logs -f.

I have tried or I do... (fill out each checkbox with a X if applicable)

• [ ] In case of WebUI issue, I have tried clearing the browser cache and the issue persists.
• [x] I do run mailcow on a Synology, QNAP or any other sort of NAS.

System information

Further information (where applicable):

Question	Answer
My operating system	Ubuntu 18.04.02
Is Apparmor, SELinux or similar active?	No
Virtualization technlogy (KVM, VMware, Xen, etc)	none
Server/VM specifications (Memory, CPU Cores)	16GB, 8 cores
Docker Version (docker version)	18.09.6
Docker-Compose Version (docker-compose version)	1.21.0, build 5920eb0
Reverse proxy (custom solution)	Not sure what to answer here.

Further notes:

• Output of git diff origin/master, any other changes to the code? If so, please post them.

diff --git a/data/conf/rspamd/override.d/worker-controller.inc b/data/conf/rspamd/override.d/worker-controller.inc
index 4d4ffe6f..0e46dcf9 100644
--- a/data/conf/rspamd/override.d/worker-controller.inc
+++ b/data/conf/rspamd/override.d/worker-controller.inc
@@ -1,5 +1,9 @@
 bind_socket = "*:11334";
 count = 1;
+enable_password = "REDACTED";
+secure_ip = "192.168.0.0/16";
+secure_ip = "172.16.0.0/12";
+secure_ip = "10.0.0.0/8";
 secure_ip = "127.0.0.1";
 secure_ip = "::1";
 bind_socket = "/var/lib/rspamd/rspamd.sock mode=0666 owner=nobody";
diff --git a/docker-compose.yml b/docker-compose.yml
index 22c762be..02d0ecea 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -290,8 +290,8 @@ services:
         until ping rspamd -c1 > /dev/null; do sleep 1; done &&
         exec nginx -g 'daemon off;'"
       environment:
-        - HTTPS_PORT=${HTTPS_PORT:-443}
-        - HTTP_PORT=${HTTP_PORT:-80}
+        - HTTPS_PORT=${HTTPS_PORT:-10443}
+        - HTTP_PORT=${HTTP_PORT:-10080}
         - MAILCOW_HOSTNAME=${MAILCOW_HOSTNAME}
         - IPV4_NETWORK=${IPV4_NETWORK:-172.22.1}
         - TZ=${TZ}
@@ -304,8 +304,8 @@ services:
         - ./data/conf/rspamd/meta_exporter:/meta_exporter:ro
         - sogo-web-vol-1:/usr/lib/GNUstep/SOGo/
       ports:
-        - "${HTTPS_BIND:-0.0.0.0}:${HTTPS_PORT:-443}:${HTTPS_PORT:-443}"
-        - "${HTTP_BIND:-0.0.0.0}:${HTTP_PORT:-80}:${HTTP_PORT:-80}"
+        - "${HTTPS_BIND:-0.0.0.0}:${HTTPS_PORT:-10443}:${HTTPS_PORT:-10443}"
+        - "${HTTP_BIND:-0.0.0.0}:${HTTP_PORT:-10080}:${HTTP_PORT:-10080}"
       restart: always
       networks:
         mailcow-network:

• All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you: iptables -L -vn, ip6tables -L -vn, iptables -L -vn -t nat and ip6tables -L -vn -t nat

Not a firewall issue.

• Check docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254 (set the IP accordingly, if you changed the internal mailcow network) and docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @1.1.1.1 - output? Timeout?

Not a networking issue.

General logs:

• Please take a look at the official documentation.

[amorfo77]

Hi, Maybe is related with #2970 , or with #2934

[snhrdt]

Yes, with very high probability. I tried running the upgrade manually, as described in https://github.com/mailcow/mailcow-dockerized/issues/2970#issuecomment-534171870 but the problem persists.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[iamarya2k24]

Recently upgraded mailcow and I faced the same issue. Had to log in to MySQL and manually update the version, and it fixed the issue. I am facing another issue where my mailcow landing page is blank. When I go to example.com, I expect to get a login page, but I get a blank page instead.

Logs

mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:09:48 IST 2023 ACME health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:09:51 IST 2023 SOGo health level: 100% (3/3), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:09:55 IST 2023 Postfix health level: 100% (8/8), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:09:57 IST 2023 Nginx health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:01 IST 2023 Mail queue health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:02 IST 2023 Fail2ban health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:07 IST 2023 Olefy health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:09 IST 2023 PHP-FPM health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:11 IST 2023 Ratelimit health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:16 IST 2023 ACME health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:18 IST 2023 MySQL/MariaDB health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:22 IST 2023 Nginx health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:26 IST 2023 Dovecot health level: 75% (9/12), health trend: 1
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:41 IST 2023 Rspamd health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:42 IST 2023 Olefy health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:43 IST 2023 Redis health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:45 IST 2023 Unbound health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:45 IST 2023 PHP-FPM health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:46 IST 2023 Dovecot replication health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:51 IST 2023 MySQL/MariaDB health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:51 IST 2023 ACME health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:56 IST 2023 SOGo health level: 100% (3/3), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:10:59 IST 2023 Postfix health level: 100% (8/8), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:09 IST 2023 Fail2ban health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:12 IST 2023 Ratelimit health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:16 IST 2023 PHP-FPM health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:18 IST 2023 Mail queue health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:21 IST 2023 Dovecot replication health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:31 IST 2023 Nginx health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:32 IST 2023 Dovecot health level: 83% (10/12), health trend: 1
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:35 IST 2023 Unbound health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:36 IST 2023 ACME health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:39 IST 2023 Postfix health level: 100% (8/8), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:44 IST 2023 MySQL/MariaDB health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:51 IST 2023 Olefy health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:52 IST 2023 Redis health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:52 IST 2023 Fail2ban health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:55 IST 2023 Nginx health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:11:55 IST 2023 PHP-FPM health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:01 IST 2023 Rspamd health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:02 IST 2023 Mail queue health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:06 IST 2023 Dovecot replication health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:10 IST 2023 SOGo health level: 100% (3/3), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:13 IST 2023 Redis health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:15 IST 2023 Ratelimit health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:20 IST 2023 MySQL/MariaDB health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:21 IST 2023 Unbound health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:22 IST 2023 Olefy health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:23 IST 2023 Rspamd health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:23 IST 2023 Nginx health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:28 IST 2023 PHP-FPM health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:31 IST 2023 Fail2ban health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:37 IST 2023 ACME health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:43 IST 2023 Dovecot replication health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:44 IST 2023 Redis health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:47 IST 2023 Dovecot health level: 92% (11/12), health trend: 1
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:50 IST 2023 Mail queue health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:12:58 IST 2023 Postfix health level: 100% (8/8), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:05 IST 2023 Unbound health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:05 IST 2023 MySQL/MariaDB health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:07 IST 2023 Fail2ban health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:09 IST 2023 Rspamd health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:09 IST 2023 SOGo health level: 100% (3/3), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:11 IST 2023 Olefy health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:13 IST 2023 ACME health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:16 IST 2023 Ratelimit health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:18 IST 2023 Dovecot health level: 100% (12/12), health trend: 1
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:20 IST 2023 Redis health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:29 IST 2023 Postfix health level: 100% (8/8), health trend: 0
mailcowdockerized-watchdog-mailcow-1   | Sun Feb 19 23:13:31 IST 2023 Fail2ban health level: 100% (1/1), health trend: 0

EDIT

I managed to fix it. I looked at logs for SELinux and found out that it was not set up properly. First, I set it to permissive and then, I reinstalled container-selinux package and re-enabled SELinux which fixed the issue.