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:
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
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.