Can't get tomcat to start

[jholder]

Don't bump. It's annoying.

It looks like it's having trouble connecting to the mysql DB

com.zimbra.common.service.ServiceException: system failure: getting database connection

    at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:175)

    at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:289)

    at com.zimbra.cs.util.Config.init(Config.java:70)

    at com.zimbra.cs.util.Config.initConfig(Config.java:97)

    at com.zimbra.cs.util.Config.getString(Config.java:109)

    at com.zimbra.cs.db.Versions.checkDBVersion(Versions.java:85)

    at com.zimbra.cs.db.Versions.checkVersions(Versions.java:81)

    at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:96)

    at com.zimbra.soap.SoapServlet.init(SoapServlet.java:115)

    at javax.servlet.GenericServlet.init(GenericServlet.java:211)

    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)

    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)

    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915)

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4176)

    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)

It looks like that is being caused by

Caused by: java.sql.SQLException: Incorrect information in file: './zimbra/config.frm'

Have you had a power failure or something?

[smcgrath1111]

Sorry about the bump - I know it's annoying, but this has become a very desperate situation. I have a support ticket open and it has had no movement; this forum is my only hope.

I have verified that the mysql server is running ok, and I am able to connect to it using telnet.

'./zimbra/config.frm' -- This file does not exist, on the test server or the (running) production server. Should it? How/when is it created?

There is a file called '/opt/zimbra/config.12505' present; it appears that was generated when I ran the 4.5.6 installer.

This installation was copied off a correctly running (production) server. This production server does have capital letters in the LDAP information. (refer to Bug 22961 - zmldapenablereplica can fail on master if ldap_master_url is not lower case), and one of the things I have done to this copy is fix them to lowercase, before running the installer (the installer errors out if I don't). I'm not sure if that's relevant or not.

I appreciate your help very much
-Scott

[smcgrath1111]

This problem turned out to be due to a lack of memory in the machine (256 MB physical, and about 1GB of swap). MySQL was not starting properly, it was throwing an error during memory allocation.

Thanks for your help John!