SoGo gives a lot of PID timeouts

MadPatrick · November 14, 2024, 6:59pm

Hi,

Just a question about Sogo
It is running good, but i see a lot PID timeout errors in the log
Is this normal ? It look it holds the push mail sometimes for a short period

When i google this it gives me not much info
I tried to expand the workers but this gives no other result

2024-11-14T19:16:20+01:00 [1:sogo1:sogo-app] Nov 14 19:16:20 sogod [7]: [WARN] <0x0x55eb438b36e0[WOWatchDogChild]> pid 113 <mark>has been hanging in the same</mark> request for 6 minutes 
2024-11-14T19:16:28+01:00 [1:sogo1:sogo-app] Nov 14 19:16:28 sogod [7]: [WARN] <0x0x55eb438b39b0[WOWatchDogChild]> pid 119 <mark>has been hanging in the same</mark> request for 11 minutes 
2024-11-14T19:16:44+01:00 [1:sogo1:sogo-app] Nov 14 19:16:44 sogod [7]: [WARN] <0x0x55eb438d0010[WOWatchDogChild]> pid 120 <mark>has been hanging in the same</mark> request for 4 minutes 
2024-11-14T19:17:11+01:00 [1:sogo1:sogo-app] Nov 14 19:17:11 sogod [7]: [WARN] <0x0x55eb4389db20[WOWatchDogChild]> pid 105 <mark>has been hanging in the same</mark> request for 32 minutes 
2024-11-14T19:17:20+01:00 [1:sogo1:sogo-app] Nov 14 19:17:20 sogod [7]: [WARN] <0x0x55eb438b36e0[WOWatchDogChild]> pid 113 <mark>has been hanging in the same</mark> request for 7 minutes 2024-11-14T19:17:28+01:00 [1:sogo1:sogo-app] Nov 14 19:17:28 sogod [7]: [WARN] <0x0x55eb438b39b0[WOWatchDogChild]> pid 119 <mark>has been hanging in the same</mark> request for 12 minutes 
2024-11-14T19:17:44+01:00 [1:sogo1:sogo-app] Nov 14 19:17:44 sogod [7]: [WARN] <0x0x55eb438d0010[WOWatchDogChild]> pid 120 <mark>has been hanging in the same</mark> request for 5 minutes 
2024-11-14T19:18:11+01:00 [1:sogo1:sogo-app] Nov 14 19:18:11 sogod [7]: [WARN] <0x0x55eb4389db20[WOWatchDogChild]> pid 105 <mark>has been hanging in the same</mark> request for 33 minutes 
2024-11-14T19:18:20+01:00 [1:sogo1:sogo-app] Nov 14 19:18:20 sogod [7]: [WARN] <0x0x55eb438b5340[WOWatchDogChild]> pid 115 <mark>has been hanging in the same</mark> request for 1 minutes 
2024-11-14T19:18:20+01:00 [1:sogo1:sogo-app] Nov 14 19:18:20 sogod [7]: [WARN] <0x0x55eb438b36e0[WOWatchDogChild]> pid 113 <mark>has been hanging in the same</mark> request for 8 minutes 
2024-11-14T19:18:28+01:00 [1:sogo1:sogo-app] Nov 14 19:18:28 sogod [7]: [WARN] <0x0x55eb438b39b0[WOWatchDogChild]> pid 119 <mark>has been hanging in the same</mark> request for 13 minutes 
2024-11-14T19:19:11+01:00 [1:sogo1:sogo-app] Nov 14 19:19:11 sogod [7]: [WARN] <0x0x55eb4389db20[WOWatchDogChild]> pid 105 <mark>has been hanging in the same</mark> request for 34 minutes 
2024-11-14T19:19:20+01:00 [1:sogo1:sogo-app] Nov 14 19:19:20 sogod [7]: [WARN] <0x0x55eb438b5340[WOWatchDogChild]> pid 115 <mark>has been hanging in the same</mark> request for 2 minutes 
2024-11-14T19:19:20+01:00 [1:sogo1:sogo-app] Nov 14 19:19:20 sogod [7]: [WARN] <0x0x55eb438b36e0[WOWatchDogChild]> pid 113 <mark>has been hanging in the same</mark> request for 9 minutes

stephdl · November 19, 2024, 9:12pm

I think it is a normal log messages. Activsync has released the pid

You have some messages more important to track. It could come from a lack of workers

github.com/mailcow/mailcow-dockerized

No child available to handle incoming request!

opened 05:12PM - 05 Feb 19 UTC

closed 09:39PM - 13 Apr 19 UTC

PiCTaTe

Hi, My logs are constantly with bellow error. > sogo-mailcow_1 | Feb… 4 18:15:31 05e81f192545 sogod [11]: [WARN] <0x0x557253cc7640[WOWatchDogChild]> pid 455 has been hanging in the same request for 6 minutes > sogo-mailcow_1 | Feb 4 18:15:31 05e81f192545 sogod [11]: [WARN] <0x0x557253c672c0[WOWatchDogChild]> pid 52 has been hanging in the same request for 8 minutes > sogo-mailcow_1 | Feb 4 18:15:41 05e81f192545 sogod [11]: [WARN] <0x0x557253c5b1c0[WOWatchDogChild]> pid 448 has been hanging in the same request for 13 minutes > sogo-mailcow_1 | Feb 4 18:15:41 05e81f192545 sogod [11]: [WARN] <0x0x557253e0a630[WOWatchDogChild]> pid 72 has been hanging in the same request for 13 minutes After some time, sogo locks with bellow error: > sogo-mailcow_1 | Feb 5 11:38:30 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:30 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:30 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:31 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! > sogo-mailcow_1 | Feb 5 11:38:32 05e81f192545 sogod [11]: [ERROR] <0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request! I have 280 mailboxes. My configuration: WOWorkersCount = "50"; SxVMemLimit = 384; SOGoMaximumPingInterval = 3540; SOGoInternalSyncInterval = 45; SOGoMaximumSyncInterval = 60;

MadPatrick · November 19, 2024, 9:21pm

I’ve seen this post and tried it.
Did not make any difference

MadPatrick · February 10, 2025, 1:25pm

Hi

I made a ticket on the Sogo platform 0006088: WOWatchDogChild pid has been hanging - SOGo | BTS

What is the best way to enable debug mode on Sogo?

SOGoDebugRequests = YES;

MadPatrick · February 11, 2025, 6:41pm

I noticed that in the SOGo.conf the timeout=360 and i saw that it is advised to set this to timeout=3600
Has this been set to 360 with a reason ?

How can i change this to survice an update ?

stephdl · February 12, 2025, 5:30pm

which timeout

github.com/NethServer/ns8-sogo

imageroot/bin/expand-configuration

b2d5457a8


      
              "sogointernalsyncinterval": os.environ['SOGOINTERNALSYNCINTERVAL'],
              "sogomaximumpinginterval": os.environ['SOGOMAXIMUMPINGINTERVAL'],
              "sogomaximumsyncinterval": os.environ['SOGOMAXIMUMSYNCINTERVAL'],
              "sogomaximumsyncresponsesize": os.environ['SOGOMAXIMUMSYNCRESPONSESIZE'],
              "sogomaximumsyncwindowsize": os.environ['SOGOMAXIMUMSYNCWINDOWSIZE'],
              "sentfolder": os.environ['SENTFOLDER'],
              "sessionduration": os.environ['SESSIONDURATION'],
              "sxvmemlimit": os.environ['SXVMEMLIMIT'],
              "timezone": os.environ['TIMEZONE'],
              "trashfolder": os.environ['TRASHFOLDER'],
              "wowatchdogrequesttimeout": os.environ['WOWATCHDOGREQUESTTIMEOUT']
          }
          # test if sogo.conf.local exists
          if os.path.exists("templates/sogo.conf.local"):
              template = jenv_custom.get_template('sogo.conf.local')
          else:
              template = jenv.get_template('sogo.conf')
          output = template.render(properties)
          with open("config/sogo.conf","w") as f:
              f.write(output)

this one can be adjusted by an environment variable

MadPatrick · February 12, 2025, 5:46pm

Hi Stephane

I mean this setting in SOGo.conf

ProxyPass /Microsoft-Server-ActiveSync \
 http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync \
 retry=60 connectiontimeout=5 timeout=3600

Don’t confuse sogo.conf with SOGo.conf.
Strange to have both the (almost) same names in the same directory

See also other posts on this forum with the setting : timeout=3600

stephdl · February 12, 2025, 6:33pm

github.com/NethServer/nethserver-sogo

root/etc/e-smith/templates/etc/httpd/conf.d/zzz_SOGo.conf/10base

master


      
          
          EOF
                }
             
                if ((($sogod{'ActiveSync'} || 'disabled') eq 'enabled') && (($webtop{'ActiveSync'} || 'disabled') eq 'disabled')){
                   $OUT .= <<EOF
          
          # Sogo ActiveSync is enabled
          
          <Location /Microsoft-Server-ActiveSync>
              ProxyPass http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync retry=60 connectiontimeout=5 timeout=3600
          </Location>
          
          EOF
                }
          
          
              $OUT .= <<EO_SOGO_CONF
          
          <Location /SOGo>
              ProxyPass http://127.0.0.1:20000/SOGo retry=0

seems a typo of me, we used 3600 with NS7

stephdl · February 12, 2025, 6:34pm

but the documentation of sSOGo states on 360

https://www.sogo.nu/files/docs/SOGoInstallationGuide.html#_microsoft_enterprise_activesync

stephdl · February 12, 2025, 6:35pm

https://www.sogo.nu/files/docs/SOGoInstallationGuide.html#_microsoft_enterprise_activesync_tuning

The above line sets a timeout for up to 360 seconds, or 6 minutes. If you want to let EAS clients keep their HTTP connections open for up to an hour, you must change the timeout parameter and set it to 3600.

stephdl · February 12, 2025, 6:36pm

change it locally in the tempalet and check what it occurs

github.com/NethServer/ns8-sogo

imageroot/templates/SOGo.conf

b2d5457a8


      
          # Redirect / to /SOGo
          RedirectMatch ^/$ https://{{domain}}/SOGo
          
          {% if active_sync %}
          # Enable to use Microsoft ActiveSync support
          # Note that you MUST have many sogod workers to use ActiveSync.
          # See the SOGo Installation and Configuration guide for more details.
          #
          ProxyPass /Microsoft-Server-ActiveSync \
           http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync \
           retry=60 connectiontimeout=5 timeout=360
          {% endif %}
          
          ProxyPass /SOGo http://127.0.0.1:20000/SOGo retry=0 nocanon
          
          <Proxy http://127.0.0.1:20000/SOGo>
          ## Adjust the following to your configuration
          ## and make sure to enable the headers module
            <IfModule headers_module>
              RequestHeader set "x-webobjects-server-port" "443"
              SetEnvIf Host (.*) HTTP_HOST=$1

stephdl · February 12, 2025, 7:04pm

we set the directive to

SOGOINTERNALSYNCINTERVAL=30
SOGOMAXIMUMPINGINTERVAL=3540
SOGOMAXIMUMSYNCINTERVAL=3540

I think it is safe to push to 3600

MadPatrick · February 12, 2025, 8:21pm

I had changed yesterday timeout=3600 and WOWatchDogRequestTimeout = 60 in the template and i experienced today an improvement.

stephdl · February 13, 2025, 6:20am

I have released a version with 3600 s of timeout in the reverse proxy