1

Topic: SOGo 3.0.1

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

Hi,

short request - I saw that sogo is right now at version 3.0.1 (http://sogo.nu/download.html). is it possible to upgrade with my installed iredmail 0.9.3?

Best,
arne

----

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

2

Re: SOGo 3.0.1

You can change the URL of SOGo apt repo, then run 'apt-get update && apt-get upgrade' to upgrade to SOGo v3. Reference:
http://sogo.nu/download.html#/v3

By the way, it might be a good idea to read its mailing list archive to understand how good/bad v3 is.
http://sogo.nu/support/index.html

3

Re: SOGo 3.0.1

Thanks!

In SOGo v3 is nice interface!

in case for CentOS 7

vi /etc/yum.repos.d/sogo.repo

change to

[SOGo]
name=Inverse SOGo Repository
baseurl=http://inverse.ca/rhel-v3/7/$basearch
enabled=1
gpgcheck=0

4

Re: SOGo 3.0.1

Works great. Thank you.

5

Re: SOGo 3.0.1

Did anyone have few screenshot from SOGo 3.x whith iredmail?

6

Re: SOGo 3.0.1

Almotzo wrote:

Did anyone have few screenshot from SOGo 3.x whith iredmail?

SOGo team offers online demo here (bottom of the page):
http://sogo.nu/

7 (edited by Almotzo 2016-02-23 14:52:23)

Re: SOGo 3.0.1

Oh, yesterday night the Demo don't work.
It's looks very nice.

It's the Support from SOGo 3.0.1 Outlook better?

8

Re: SOGo 3.0.1

I just upgraded and at first glance all works good, activesync, setings, etc.

9

Re: SOGo 3.0.1

Almotzo wrote:

It's the Support from SOGo 3.0.1 Outlook better?

It shares the same backend as SOGo 2.x, so i guess no additional improvements in this part.

10

Re: SOGo 3.0.1

Found one issue - for one user I am unable to set reverse chronological sorting - right now its set to oldest on top and I'd like to sat it to newest messages on top.

Other users - everything is fine.
I removed the account and re-created it, copied messages back - still no good.

Where does sogo3 save sorting preferences?

11

Re: SOGo 3.0.1

andrzej wrote:

Where does sogo3 save sorting preferences?

Dear andrzej,

I suggest that posting SOGo "bug" in its mailing list, so that you can get support from developers:
http://sogo.nu/support/index.html#/community

12

Re: SOGo 3.0.1

Dear all,

Next iRedMail release (0.9.5) will switch to SOGo v3. smile

13

Re: SOGo 3.0.1

ZhangHuangbin wrote:

Dear all,

Next iRedMail release (0.9.5) will switch to SOGo v3. smile

Yeaaah!
When the release iRM? smile

14

Re: SOGo 3.0.1

Hi kysil,

If you just want to switch to SOGo v3, please try this:
http://www.iredmail.org/docs/upgrade.ir … v3-from-v2

WARNING: The upgrade tutorial is still a draft, please do not apply other steps.

15

Re: SOGo 3.0.1

Hi ZhangHuangbin,
I want to switch to iRedMail 0.9.5 smile

16

Re: SOGo 3.0.1

ZhangHuangbin wrote:

Hi kysil,

If you just want to switch to SOGo v3, please try this:
http://www.iredmail.org/docs/upgrade.ir … v3-from-v2

WARNING: The upgrade tutorial is still a draft, please do not apply other steps.

There is a typo in the SOGO upgrade docs:

On RHEL/CentOS, please open file /etc/yum.repos.d/sogo.conf....

Should be:

 /etc/yum.repos.d/sogo.repo

17 (edited by dsp3 2016-03-26 04:55:25)

Re: SOGo 3.0.1

Did the URL for SOGo change with the v3 update? Using the following:

https://mail.domain.com/SOGo/so/

Gives 502 Bad Gateway

18

Re: SOGo 3.0.1

Steps for reverting back to v2 from v3? What is the baseurl for v2 on Centos?
Thanks

19

Re: SOGo 3.0.1

dsp3 wrote:
https://mail.domain.com/SOGo/so/

Gives 502 Bad Gateway

Try access: https://<server>/SOGo/ (no '/so/').

*) Also, did you restart SOGo service?
*) Did you restore sogo.conf?
*) If it doesn't work, please backup /etc/sogo/sogo.conf, then remove both "sope*" and "sogo*", then reinstall them.

20

Re: SOGo 3.0.1

ZhangHuangbin wrote:
dsp3 wrote:
https://mail.domain.com/SOGo/so/

Gives 502 Bad Gateway

Try access: https://<server>/SOGo/ (no '/so/').

*) Also, did you restart SOGo service?
*) Did you restore sogo.conf?
*) If it doesn't work, please backup /etc/sogo/sogo.conf, then remove both "sope*" and "sogo*", then reinstall them.

1. Changed /etc/yum.repos.d/sogo.repo to:

baseurl=http://inverse.ca/rhel-v3/$releasever/$basearch/

2. Removed Sogo and sope using:

yum remove sogo* sope*

3. Did yum update followed by yum clean all
4. Yum install sogo has the following output:

Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : sope49-xml-4.9-20160305_1664.el7.1.x86_64                   1/10 
  Installing : sope49-core-4.9-20160305_1664.el7.1.x86_64                  2/10 
  Installing : sope49-ldap-4.9-20160305_1664.el7.1.x86_64                  3/10 
  Installing : sope49-mime-4.9-20160305_1664.el7.1.x86_64                  4/10 
  Installing : sope49-appserver-4.9-20160305_1664.el7.1.x86_64             5/10 
  Installing : sope49-gdl1-4.9-20160305_1664.el7.1.x86_64                  6/10 
  Installing : sope49-gdl1-contentstore-3.0.2-1.el7.centos.x86_64          7/10 
  Installing : sope49-sbjson-2.3.1-20160305_1664.el7.1.x86_64              8/10 
  Installing : sope49-cards-3.0.2-1.el7.centos.x86_64                      9/10 
  Installing : sogo-3.0.2-1.el7.centos.x86_64                             10/10 
Created symlink from /etc/systemd/system/multi-user.target.wants/sogod.service to /usr/lib/systemd/system/sogod.service.
warning: %post(sogo-3.0.2-1.el7.centos.x86_64) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package sogo-3.0.2-1.el7.centos.x86_64
  Verifying  : sope49-ldap-4.9-20160305_1664.el7.1.x86_64                  1/10 
  Verifying  : sope49-xml-4.9-20160305_1664.el7.1.x86_64                   2/10 
  Verifying  : sogo-3.0.2-1.el7.centos.x86_64                              3/10 
  Verifying  : sope49-mime-4.9-20160305_1664.el7.1.x86_64                  4/10 
  Verifying  : sope49-cards-3.0.2-1.el7.centos.x86_64                      5/10 
  Verifying  : sope49-core-4.9-20160305_1664.el7.1.x86_64                  6/10 
  Verifying  : sope49-gdl1-contentstore-3.0.2-1.el7.centos.x86_64          7/10 
  Verifying  : sope49-gdl1-4.9-20160305_1664.el7.1.x86_64                  8/10 
  Verifying  : sope49-appserver-4.9-20160305_1664.el7.1.x86_64             9/10 
  Verifying  : sope49-sbjson-2.3.1-20160305_1664.el7.1.x86_64             10/10 

Installed:
  sogo.x86_64 0:3.0.2-1.el7.centos

Dependency Installed:
  sope49-appserver.x86_64 0:4.9-20160305_1664.el7.1                             
  sope49-cards.x86_64 0:3.0.2-1.el7.centos                                      
  sope49-core.x86_64 0:4.9-20160305_1664.el7.1                                  
  sope49-gdl1.x86_64 0:4.9-20160305_1664.el7.1                                  
  sope49-gdl1-contentstore.x86_64 0:3.0.2-1.el7.centos                          
  sope49-ldap.x86_64 0:4.9-20160305_1664.el7.1                                  
  sope49-mime.x86_64 0:4.9-20160305_1664.el7.1                                  
  sope49-sbjson.x86_64 0:2.3.1-20160305_1664.el7.1                              
  sope49-xml.x86_64 0:4.9-20160305_1664.el7.1                                   

Complete!

5. Restored sogo.conf.bak

cp /etc/sogo/sogo.conf.bak /etc/sogo/sogo.conf

6. Checked status of sogod

systemctl status sogod

Which shows error:

-- Unit session-4919676.scope has begun starting up.
Mar 26 08:19:01 mail CROND[10691]: (sogo) CMD (/usr/sbin/sogo-tool expire-sessio
Mar 26 08:19:39 mail systemd[1]: sogod.service start operation timed out. Termin
Mar 26 08:19:39 mail systemd[1]: Failed to start SOGo is a groupware server.
-- Subject: Unit sogod.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sogod.service has failed.
-- 
-- The result is failed.
Mar 26 08:19:39 mail systemd[1]: Unit sogod.service entered failed state.
Mar 26 08:19:39 mail systemd[1]: sogod.service failed.

7. Reboot to see if that helps to start sogod correctly. Nothing.
8. Running 'top' I see multiple "sogo-ealarms-no" eating all my cpu
9. Removed Sogo and Sope.

21

Re: SOGo 3.0.1

If it doesn't work, please do check sogo log file to extract related log. "doesn't work then remove it" is not the way to get it back.

Do you have package sope49-sdl1-mysql installed?

22 (edited by dsp3 2016-03-26 16:56:18)

Re: SOGo 3.0.1

"doesn't work then remove it"

It was the only way to kill the spawning processes which were eating the cpu on the server.

Nothing in sogo.log of significance.
I will check to see sope49-sdl1-mysql gets installed.
Thanks

Edit*
sope49-gdl1-mysql is installed. Installing Sogo gives same error:

Installing : sogo-3.0.2-1.el7.centos.x86_64                                                                                                           1/1 
Created symlink from /etc/systemd/system/multi-user.target.wants/sogod.service to /usr/lib/systemd/system/sogod.service.
warning: %post(sogo-3.0.2-1.el7.centos.x86_64) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package sogo-3.0.2-1.el7.centos.x86_64

and

 systemctl status sogod
● sogod.service - SOGo is a groupware server
   Loaded: loaded (/usr/lib/systemd/system/sogod.service; enabled; vendor preset: disabled)
   Active: failed (Result: timeout) since Sat 2016-03-26 09:49:04 EET; 20s ago
  Process: 2937 ExecStart=/usr/sbin/sogod -WOWorkersCount ${PREFORK} -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log (code=killed, signal=TERM)

Mar 26 09:47:34 mail systemd[1]: Starting SOGo is a groupware server...
Mar 26 09:49:04 mail systemd[1]: sogod.service start operation timed out. Terminating.
Mar 26 09:49:05 mail systemd[1]: Failed to start SOGo is a groupware server.
Mar 26 09:49:05 mail systemd[1]: Unit sogod.service entered failed state.
Mar 26 09:49:05 mail systemd[1]: sogod.service failed.

Edit 2**
There are lots of messages to postmaster with:

/bin/sh: /usr/sbin/sogo-tool: No such file or directory
/bin/sh: /usr/sbin/sogo-ealarms-notify: No such file or directory

Seems yum doesn't install these dependencies: sogo-ealarms-notify sogo-tool sogo-activesync. Can I follow the following guide to get back to V2? http://www.iredmail.org/docs/sogo-centos-6-mysql.html

23

Re: SOGo 3.0.1

Try:

*) reinstall packages: sogo sope49-gdl1-mysql sogo-activesync sogo-ealarms-notify sogo-tool.
*) restore sogo.conf.
*) restart SOGo service.

24

Re: SOGo 3.0.1

ZhangHuangbin wrote:

Try:

*) reinstall packages: sogo sope49-gdl1-mysql sogo-activesync sogo-ealarms-notify sogo-tool.
*) restore sogo.conf.
*) restart SOGo service.

Thanks Zhang. I have tried this. Unfortunately sogod will not start with 3.0.2 (Active: failed Result: timeout) . sogo-tool and sogo-ealarms do start, but they spawn multiple processes and take over the cpu until eventually the server becomes unresponsive and I have to kill the processes.

25

Re: SOGo 3.0.1

Cannot start sogod, no any log in /var/log/sogo/sogo.log?