1 (edited by tyllee 2016-04-12 14:29:02)

Topic: 504 Gateway Time-out SOGO

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

Sogo is unresponsive. When I try to access https://server/sogo i get
"504 Gateway Time-out"
And EAS clients can not connect either.

I've tryed restarting sogo
service sogo restart

# service sogo status
● sogo.service - LSB: SOGo server
   Loaded: loaded (/etc/init.d/sogo)
   Active: active (running) since Tue 2016-04-12 08:01:23 CEST; 21s ago
  Process: 13149 ExecStop=/etc/init.d/sogo stop (code=exited, status=0/SUCCESS)
  Process: 13214 ExecStart=/etc/init.d/sogo start (code=exited, status=0/SUCCESS)

Last change in sogo.log:
Apr 12 02:04:34 sogod [12964]: <0x0x7fa0950c9180[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...
Apr 12 02:04:34 sogod [12313]: <0x0x7fa094edaa90[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...
Apr 12 02:04:34 sogod [13055]: <0x0x7fa095285510[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...

# system reboot

Sogo is running again and EAS can connect.

sogo.log
Apr 12 02:10:12 sogod [1161]: <0x0x7f9d28d18b70[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...
Apr 12 02:10:19 sogod [1170]: [WARN] <0x0x7f9d291065a0[SOGoWebDAVAclManager]> entry '{DAV:}write' already exists in DAV permissions table
Apr 12 02:10:19 sogod [1170]: [WARN] <0x0x7f9d291065a0[SOGoWebDAVAclManager]> entry '{DAV:}write-properties' already exists in DAV permissions table
Apr 12 02:10:19 sogod [1170]: [WARN] <0x0x7f9d291065a0[SOGoWebDAVAclManager]> entry '{DAV:}write-content' already exists in DAV permissions table
Apr 12 02:10:19 sogod [1170]: <0x0x7f9d28e7e0d0[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...
Apr 12 02:10:22 sogod [1162]: <0x0x7f9d2913b690[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping...

# date
Tue Apr 12 08:11:02 CEST 2016

What instance did I miss rebooting?
And I can't understand the timestamp in sogo.log.

After reboot, sogo behaves very slow.

UPDATE:
And is now unresponsive once more

----

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

2

Re: 504 Gateway Time-out SOGO

The URL is case sensitive, it's '/SOGo', not '/sogo'. Did you type incorrect url?

3 (edited by tyllee 2016-04-12 15:07:18)

Re: 504 Gateway Time-out SOGO

ZhangHuangbin wrote:

The URL is case sensitive, it's '/SOGo', not '/sogo'. Did you type incorrect url?

I'm typing /sogo, and always been typing sogo, I'm redirected to /SOGo.

I removed the EAS account from my iphone and readded it. And now I can access sogo again and it's working on EAS clients. Strange.

When I type https://server/sogo I get sogo login.

Do you have any clue about the time stamp in the log?

4

Re: 504 Gateway Time-out SOGO

tyllee wrote:

Do you have any clue about the time stamp in the log?

Do you have correct time zone in /etc/sogo/sogo.conf?

SOGoTimeZone = 

5

Re: 504 Gateway Time-out SOGO

ZhangHuangbin wrote:
tyllee wrote:

Do you have any clue about the time stamp in the log?

Do you have correct time zone in /etc/sogo/sogo.conf?

SOGoTimeZone = 

Thank you!

Yes of course. May be put this in the iredmail installer script?

EAS with sogo, is working for the moment and now I get a better trace in the logs smile

6

Re: 504 Gateway Time-out SOGO

tyllee wrote:

Yes of course. May be put this in the iredmail installer script?

Sorry, no plan to show a dialog page for time zone setting.