I had similar problems:
- Upgrading worked fine...well, it seems to be fine
- After a reboot of the machine, we also had permission problems
- Mails were deferred and the slapd could not resolve correctly, lmtp was on the wrong IP-adress...
Weird things happened...searching the forum, i came to the conclusion, that there is a Debian KERNEL bug, which changes the permissions in some 'zimbra' owned folders, if you make a '/etc/init.d/zimbra stop' as root.
Check:
========
- redo.log
- and look in /opt/zimbra/index/
=> if all permissions are: 'zimbra:zimbra'
If NOT:
- stop zimbra
- and make: /opt/zimbra/libexec/zmfixperms as root !
Check also /opt/zimbra/log/zimbra.log, if there are any exceptions !
Actually i upgraded Debian Sarge to Kernel 2.6.17-2-686 (from backports), because i had to enable HIGHMEM support (but this was a personal problem). I recognized, that with a newer kernel Zimbra performs much better.
The bug should be
Quote:
|
"fixed in debian's linux-source-2.6.17-8~bpo.1"
|
Read:
=====
mystery solved: unclean shutdown causes redo.log to be owned by root:root Zimbra error when sending messages
Maybe this was a little help ;-)
/harry