2018-04-04 12:41:27 -05:00
|
|
|
# Upgrade SOGo from v3 to v4
|
|
|
|
|
|
|
|
[TOC]
|
|
|
|
|
|
|
|
SOGo v4 was released on Mar 7, 2018 by the SOGo team (<https://sogo.nu>), it
|
|
|
|
will become the main branch with most active development.
|
|
|
|
If you're satisfied with SOGo v3, you're free to stick to it.
|
|
|
|
|
|
|
|
## Upgrade SOGo On RHEL/CentOS
|
|
|
|
|
|
|
|
* Backup config files first:
|
|
|
|
|
|
|
|
```
|
|
|
|
mkdir -p /root/sogo-backup/{sogo,sysconfig}
|
|
|
|
cp /etc/sogo/* /root/sogo-backup/sogo/
|
|
|
|
cp /etc/sysconfig/sogo /root/sogo-backup/sysconfig/
|
|
|
|
```
|
|
|
|
|
|
|
|
* Backup its SQL database:
|
|
|
|
|
|
|
|
```
|
|
|
|
bash /var/vmail/backup/backup_sogo.sh
|
|
|
|
```
|
|
|
|
|
|
|
|
* Open file `/etc/yum.repos.d/sogo.repo`, change the version number in
|
|
|
|
`baseurl=` line from `3` to `4`:
|
|
|
|
|
|
|
|
```
|
|
|
|
baseurl=https://packages.inverse.ca/SOGo/nightly/4/rhel/$releasever/$basearch/
|
|
|
|
```
|
|
|
|
|
2018-04-05 10:43:34 -05:00
|
|
|
* SOGo relies on the GNUstep packages provided by SOGo team, and must not use
|
|
|
|
the packages from EPEL repo. Please open file `/etc/yum.repos.d/epel.repo`,
|
|
|
|
make sure you have line like below:
|
|
|
|
|
|
|
|
```
|
|
|
|
exclude=gnustep*
|
|
|
|
```
|
|
|
|
|
2018-04-04 12:41:27 -05:00
|
|
|
* Upgrade SOGo packages:
|
|
|
|
|
|
|
|
```
|
|
|
|
yum clean all
|
2018-06-01 02:18:07 -05:00
|
|
|
yum update 'sogo*' 'sope*'
|
2018-04-04 12:41:27 -05:00
|
|
|
```
|
|
|
|
|
|
|
|
* Run the script shipped in SOGo-4.x to update SQL structure:
|
|
|
|
* For LDAP and MySQL/MariaDB backends:
|
|
|
|
|
|
|
|
```
|
|
|
|
bash /usr/share/doc/sogo-4.*/sql-update-3.2.10_to_4.0.0-mysql.sh
|
|
|
|
```
|
|
|
|
|
|
|
|
* For PostgreSQL backend:
|
|
|
|
|
|
|
|
```bash /usr/share/doc/sogo-4.*/sql-update-3.2.10_to_4.0.0.sh```
|
|
|
|
|
2018-09-12 03:58:20 -05:00
|
|
|
* Restart SOGo and memcached services:
|
2018-04-04 12:41:27 -05:00
|
|
|
|
|
|
|
```
|
2018-09-12 03:58:20 -05:00
|
|
|
service memcached restart
|
2018-04-04 12:41:27 -05:00
|
|
|
service sogod restart
|
|
|
|
```
|
|
|
|
|
|
|
|
## Upgrade SOGo On Debian/Ubuntu
|
|
|
|
|
|
|
|
* Backup config files first:
|
|
|
|
|
|
|
|
```
|
|
|
|
mkdir -p /root/sogo-backup/{sogo,default}
|
|
|
|
cp /etc/sogo/* /root/sogo-backup/sogo/
|
|
|
|
cp /etc/default/sogo /root/sogo-backup/default/
|
|
|
|
```
|
|
|
|
|
|
|
|
* Backup its SQL database:
|
|
|
|
|
|
|
|
```
|
|
|
|
bash /var/vmail/backup/backup_sogo.sh
|
|
|
|
```
|
|
|
|
|
2018-04-11 04:35:47 -05:00
|
|
|
* Open file `/etc/apt/sources.list` or `/etc/apt/sources.list.d/sogo-nightly.list`,
|
|
|
|
change the version number `3` to `4`, like below:
|
2018-04-04 12:41:27 -05:00
|
|
|
|
|
|
|
```
|
|
|
|
# Debian
|
|
|
|
https://packages.inverse.ca/SOGo/nightly/4/debian ...
|
|
|
|
|
|
|
|
# Ubuntu
|
|
|
|
https://packages.inverse.ca/SOGo/nightly/4/ubuntu ...
|
|
|
|
```
|
|
|
|
|
|
|
|
* Upgrade SOGo packages:
|
|
|
|
|
|
|
|
```
|
|
|
|
apt-get update
|
|
|
|
apt-get install --only-upgrade sogo sogo-activesync
|
|
|
|
```
|
|
|
|
|
|
|
|
* Run the script shipped in SOGo-4.x to update SQL structure:
|
|
|
|
* For LDAP and MySQL/MariaDB backends:
|
|
|
|
|
|
|
|
```
|
|
|
|
bash /usr/share/doc/sogo/sql-update-3.2.10_to_4.0.0-mysql.sh
|
|
|
|
```
|
|
|
|
|
|
|
|
* For PostgreSQL backend:
|
|
|
|
|
|
|
|
```bash /usr/share/doc/sogo/sql-update-3.2.10_to_4.0.0.sh```
|
|
|
|
|
2018-09-12 03:58:20 -05:00
|
|
|
* Restart SOGo and memcached services:
|
2018-04-04 12:41:27 -05:00
|
|
|
|
|
|
|
```
|
2018-09-12 03:58:20 -05:00
|
|
|
service memcached restart
|
2018-04-04 12:41:27 -05:00
|
|
|
service sogo restart
|
|
|
|
```
|
|
|
|
|
|
|
|
## Upgrade SOGo On FreeBSD
|
|
|
|
|
|
|
|
FreeBSD ports tree still ships SOGo-3, so no SQL structure change after you
|
|
|
|
update ports `www/sogo3` and `www/sogo3-activesync`.
|
|
|
|
|
|
|
|
## Upgrade SOGo On OpenBSD
|
|
|
|
|
|
|
|
OpenBSD 6.3 still ships SOGo-3, so no SQL structure change after you update
|
|
|
|
sogo/sope packages with `pkg_add` command.
|
|
|
|
|
|
|
|
## Troubleshooting
|
|
|
|
|
|
|
|
If SOGo doesn't work as expected, please check its log file
|
|
|
|
`/var/log/sogo/sogo.log`. If you don't understand what the error message means,
|
|
|
|
please extract related error message and post to our online support forum:
|
|
|
|
<https://forum.iredmail.org/>.
|