==== 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:
====A few weeks ago I upgraded my iRedmail Centos 6.8/Apache/LDAP/Sogo to the latest build 0.9.5-1.  I was quite a few releases behind. All went well.

Today I proceeded to upgrade Sogo client from v2 to v3. Followed the doc http://www.iredmail.org/docs/upgrade.sogo.2.to.3.html.

Sogod would not start afterwards.  Did the sope* reinstall and again restored my sogo.conf for /httpd/conf.d and /syscofig/sogo.

Turns out problem was with file permissions on sogo log  (  /var/log/sogo)

Here's what it was:
#ls -l
-rw-r--r--. 1 496 496  823868 Nov 22 07:56 sogo.log
-rw-r--r--  1 496 496  141244 Nov 22 04:10 sogo.log-20161121.gz
-rw-r--r--  1 496 496 3257300 Nov 22 04:10 sogo.log-20161122

cat /etc/passwd shows:
sogo:x:493:493:SOGo daemon:/var/lib/sogo:/sbin/nologin

I don't even see a 496:496 user/group listed..

Proceeded to chown 493:493 *.* in the /var/log/sogo/

Now /var/log/sogo shows:
#ls -l
-rw-r--r--. 1 sogo sogo  823868 Nov 22 07:56 sogo.log
-rw-r--r--  1 sogo sogo  141244 Nov 22 04:10 sogo.log-20161121.gz
-rw-r--r--  1 sogo sogo 3257300 Nov 22 04:10 sogo.log-20161122

#service sogod restart

Sogo running. I can access mail through new v3 sogo interface.

Nice!