Quote:
Originally Posted by rwc101010  The main issue I encountered was a failure of Tomcat (and all services that run on it) shortly after Zimbra startup (Tomcat starts, but fail shortly after - resulting logs are inconclusive). |
That sounds like a log permissions issue. Have you checked to see if they're actually being written to? If they arn't, then check the permissions. You should be able to fix this by:
su -root
chown -R zimbra:zimbra /opt/zimbra
cd /opt/zimbra/libexec
./zmfixperms
Quote:
|
Upon digging into what logs were generated, and following some of the threads in the forum, I came across a number of possible fixes . . . which led to even more errors which indicated an inconsistent failure to communicate with the LDAP server.
|
There are several kinds of communication failures. The only time that I would say that you might have a serious issue, is if the error code is 80, with an internal error. Most others are recoverable.
Quote:
|
At the point of writing the post, I had given up on recovering the install, so started down the path of recovering the data. I'll reinstall the recovered server and post my recovery steps and the resulting logs. I would love to recover the install and all the data intact of course, but am prepared for less.
|
Don't ever give up until you give us a shot at it.
Let's see some logs.
-john