Watchdog ALERT: sogo-mailcow - timeouts

AllgaeuerBraunvie

I’m getting a lot of timeouts with Sogo recently since Sunday. I did an upate already, but it did not help. How can i debug this to get the failure go away…

HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.001964s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.003 second response time |time=0.002536s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.002012s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.004 second response time |time=0.003691s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.001989s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.021 second response time |time=0.020956s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.001973s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.002074s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.002098s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.002105s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.002108s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.001940s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.003 second response time |time=0.003252s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.020 second response time |time=0.019718s;;;0.000000 size=2700B;;;0 CRITICAL - Socket timeout CRITICAL - Socket timeout HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.031 second response time |time=0.030756s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.020 second response time |time=0.019686s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.003 second response time |time=0.003059s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.001934s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.001928s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.003 second response time |time=0.003294s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.017 second response time |time=0.017094s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.003 second response time |time=0.003099s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.014 second response time |time=0.014490s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.003 second response time |time=0.003108s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.003 second response time |time=0.002613s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.179 second response time |time=0.179400s;;;0.000000 size=2700B;;;0 CRITICAL - Socket timeout HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 9.786 second response time |time=9.786002s;;;0.000000 size=2700B;;;0 CRITICAL - Socket timeout HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.036 second response time |time=0.036490s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.035 second response time |time=0.035005s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.015 second response time |time=0.015486s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.002066s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.002357s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.002 second response time |time=0.002011s;;;0.000000 size=2700B;;;0 HTTP OK: HTTP/1.1 200 OK - 2700 bytes in 0.003 second response time The watchdog is sending a lot of emails - every 15 minutes.

n1sni

Hopefully you got through this. In my experience, this usually means that WOWorkersCount is too low. You can tell by running this from /opt/mailcow-dockerized:

docker logs -n 10000 mailcowdockerized_sogo-mailcow_1 | grep -i “no child”

if that does come back with error, please do the following assuming you have the memory for it:
open this file:
/opt/mailcow-dockerized/data/conf/sogo/sogo.conf

adjust:
WOWorkersCount = “20”;

to: (or replace 20 with the number of simultaneous connections present - note, you need 1 for each activesync connection)
WOWorkersCount = “100”;

then,
cd /opt/mailcow-dockerized
sudo docker-compose restart sogo-mailcow