1

Topic: Sogo 504 Gateway Timeout

==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
======== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.6
- Linux/BSD distribution name and version: Ubuntu
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
====

SoGo is keep showing 504 Gateway Timeout and at times  it shows 502 Gateway timeout as in screenshot attached.

Please help

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Sogo 504 Gateway Timeout

Is SOGo service actually running?

3

Re: Sogo 504 Gateway Timeout

ZhangHuangbin wrote:

Is SOGo service actually running?

Yes,

Also, I can send and receive email via mail clients, i.e. outlook, thunderbird, etc.

But via web, using SOGo, it works at times and Gateway timeout most times.

4

Re: Sogo 504 Gateway Timeout

dkuyebox wrote:

But via web, using SOGo, it works at times and Gateway timeout most times.

Please check SOGo log file, probably no spare sogo processes to handle new requests.

5

Re: Sogo 504 Gateway Timeout

ZhangHuangbin wrote:
dkuyebox wrote:

But via web, using SOGo, it works at times and Gateway timeout most times.

Please check SOGo log file, probably no spare sogo processes to handle new requests.

This is my SOGo log

Mar 01 06:11:33 sogod [22125]: [WARN] <0x0x56198b7f6760[WOWatchDogChild]> pid 22126 has been hanging in the same request for 6 minutes
Mar 01 06:11:33 sogod [22125]: [WARN] <0x0x56198b7f78e0[WOWatchDogChild]> pid 22134 has been hanging in the same request for 3 minutes
Mar 01 06:11:34 sogod [22125]: [ERROR] <0x0x56198b4e4700[WOWatchDog]> No child available to handle incoming request!
Mar 01 06:11:35 sogod [22130]: <0x0x56198bdb1280[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...
Mar 01 06:11:35 sogod [22134]: <0x0x56198d22a870[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...
Mar 01 06:11:35 sogod [22126]: <0x0x56198c7b0990[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...
Mar 01 06:11:36 sogod [22125]: [ERROR] <0x0x56198b4e4700[WOWatchDog]> No child available to handle incoming request!
Mar 01 06:11:37 sogod [22125]: [ERROR] <0x0x56198b4e4700[WOWatchDog]> No child available to handle incoming request!
Mar 01 06:11:38 sogod [22131]: <0x0x56198c2b0ae0[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...
Mar 01 06:11:39 sogod [22125]: [WARN] <0x0x56198b7f7ab0[WOWatchDogChild]> pid 22135 has been hanging in the same request for 6 minutes
Mar 01 06:11:39 sogod [22125]: [ERROR] <0x0x56198b4e4700[WOWatchDog]> No child available to handle incoming request!

6

Re: Sogo 504 Gateway Timeout

dkuyebox wrote:

Mar 01 06:11:34 sogod [22125]: [ERROR] <0x0x56198b4e4700[WOWatchDog]> No child available to handle incoming request!

See this? Increase preforked sogo processes in /etc/default/sogo please.