Hi
I have little problem with SOGo Webmailer... I cannot start/call the web-gui anymore. When ever I try to open the webpage I do get a 502 Bad Gateway. I am not sure since when this happens.
I tried with restarting the complete server. I tried with updating the server (with restart), I tried with updating also mailcow docker containers (and restart :-) ). But nothing helps me out.
So, telling the truth, I am not a very familiar with docker :)
Everything else seems to work fine.
My server is a root vServer (enough RAM, CPU/Cores, HDD)
OS is Ubuntu 18.04 LTE
mailcow-dockerized images before the update:
All I can see in the SOGo logs is something like this...
root@lxsrv04:/opt/mailcow-dockerized# docker-compose logs --tail=1000 sogo-mailcow
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
Attaching to mailcowdockerized_sogo-mailcow_1
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
...
...
...
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
sogo-mailcow_1 | Sep 13 21:17:01 25c680017a99 CRON[23328]: pam_unix(cron:session): session opened for user root by (uid=0)
sogo-mailcow_1 | Sep 13 21:17:01 25c680017a99 CRON[23329]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
sogo-mailcow_1 | Sep 13 21:17:01 25c680017a99 CRON[23328]: pam_unix(cron:session): session closed for user root
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
sogo-mailcow_1 | ERROR 1359 (HY000) at line 2: Trigger already exists
sogo-mailcow_1 | Will retry to setup SOGo password update trigger in 3s
root@lxsrv04:/opt/mailcow-dockerized#
Hi I have little problem with SOGo Webmailer... I cannot start/call the web-gui anymore. When ever I try to open the webpage I do get a 502 Bad Gateway. I am not sure since when this happens.
I tried with restarting the complete server. I tried with updating the server (with restart), I tried with updating also mailcow docker containers (and restart :-) ). But nothing helps me out.
So, telling the truth, I am not a very familiar with docker :)
Everything else seems to work fine.
My server is a root vServer (enough RAM, CPU/Cores, HDD) OS is Ubuntu 18.04 LTE mailcow-dockerized images before the update:
mailcow-dockerized after the container update
All I can see in the SOGo logs is something like this...
Anyone any ideas? Thanks in advance! Markus