You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
... I have understood that answers are voluntary and community-driven, and not commercial support.
... I have verified that my issue has not been already answered in the past. I also checked previous issues.
Description
Hello,
I have just updated my mailcow to the most recent version and it won't start back up. I can only reach the what is happening page.
If I revert the php-fpm image to 1.87 it starts working again. I can also replicate this in a test VM if you want. I have seen similar issues reported already but no fix worked until now.
Logs:
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
rspamd-mailcow-1 | Waiting for PHP on port 9001...
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id... trying again
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 4190: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 24: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000094s;;;0.000000
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 993: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 143: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 10001: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 4190: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 24: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000105s;;;0.000000
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 993: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 143: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 10001: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 4190: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 24: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000093s;;;0.000000
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 993: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 143: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 10001: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 4190: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 24: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000055s;;;0.000000
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 993: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 143: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 10001: Connection refused
watchdog-mailcow-1 | connect to address 10.10.60.250 and port 4190: Connection refused
watchdog-mailcow-1 | Mon Dec 16 21:46:45 WET 2024 Olefy health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Mon Dec 16 21:46:45 WET 2024 Dovecot health level: 17% (2/12), health trend: -10
watchdog-mailcow-1 | Mon Dec 16 21:46:52 WET 2024 Fail2ban health level: 100% (1/1), health trend: 0
### Steps to reproduce:
```plain text
1 - Update/Start a mailcow instance
2 - Only "What is Happening" page is reachable
3 - php container gets "stuck" trying to get mysql container id
But can i maybe get access to your testvm to analyse what is causing this? I said 20000x times that i nowhere can reproduce this issue so it would be nice if i can hop on a server and see if i finally get a valid reason why it is happening.
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Ubuntu 24.04
Server/VM specifications:
7GB RAM / 4 Cores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
Proxmox/KVM
Docker version:
27.3.1
docker-compose version or docker compose version:
v2.29.7
mailcow version:
2024-11b
Reverse proxy:
Traefik
Logs of git diff:
Logs of iptables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: