Quote:
Originally Posted by math  How do I ensure that peridition doesnt startup next reboot? |
I'd like to know this too. I think the implication was to go to the admin console and disable imap/pop3 but that doesn't see to have fixed it for me, every time I stop and restart zimbra I get the problem described in the original post. This started as a result of a power failure, unclean shutdown last night.
As a second point, I'd actually like to use imap/pop3 to access my mail server but I never managed to get that working with Zimbra.
So now my startup sequence consists of (following a reboot, or zmcontrol start)
su - zimbra
zmperditionctl stop
tomcat restart
then all is good. It took me about 4 hours to track this down, googling for reasons that tomcat was failing didn't help and I finally went digging and found the logfile catalina.out under /opt/zimbra/apache-tomcat-5.5.15/logs and the stacktrace similar to the one in the OP which I then googled for to get here. Adding "tomcat/JVM exited twice" to help other posters google their way.