Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Tomcat starts and then stops

  1. #1
    Join Date
    Dec 2006
    Posts
    8
    Rep Power
    8

    Unhappy Tomcat starts and then stops

    Greetings,
    I am evaluating Zimbra for possible implementation.
    I am running Fedora Core 6, and had a couple of snags during the installation, but got past those.
    The issue now is, I can start all the services, but then the mailbox stops with the message "Tomcat is not running"
    I've looked all through the forums for this issue, and found several references to this, but none appear to apply to me. (I don't even have a redo.log but the parent folder is owned by the zimbra user).
    I followed some of the troubleshooting steps and determined (by running sh -x /opt/zimbra/bin/tomcat start) that tomcat does start. I can verify the process is running, but it dies after a few seconds. I see no indication in catalina.out of why this is happening.
    Here's the text from catalina.out:
    Dec 8, 2006 7:22:35 AM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-80
    Dec 8, 2006 7:22:35 AM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-7071
    Dec 8, 2006 7:22:35 AM org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 935 ms
    Dec 8, 2006 7:22:35 AM org.apache.catalina.core.StandardService start
    INFO: Starting service Catalina
    Dec 8, 2006 7:22:35 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/5.5.15
    Dec 8, 2006 7:22:35 AM org.apache.catalina.core.StandardHost start
    INFO: XML validation disabled
    Dec 8, 2006 7:22:36 AM org.apache.catalina.startup.HostConfig deployDescriptor
    WARNING: A docBase /opt/zimbra/apache-tomcat-5.5.15/webapps/zimbra inside the host appBase has been specified, and will be ignored
    log4j:WARN No appenders could be found for logger (org.apache.catalina.session.ManagerBase).
    log4j:WARN Please initialize the log4j system properly.
    Zimbra server reserving server socket port=110 bindaddr=null ssl=false
    Zimbra server reserving server socket port=995 bindaddr=null ssl=true
    Zimbra server reserving server socket port=143 bindaddr=null ssl=false
    Zimbra server reserving server socket port=993 bindaddr=null ssl=true
    Zimbra server process is running as root, changing to user=zimbra uid=501 gid=501
    Zimbra server process, after change, is running with uid=501 euid=501 gid=501 egid=501
    Dec 8, 2006 7:22:42 AM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-80
    Dec 8, 2006 7:22:43 AM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-7071
    Dec 8, 2006 7:22:43 AM org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 896 ms
    Dec 8, 2006 7:22:43 AM org.apache.catalina.core.StandardService start
    INFO: Starting service Catalina
    Dec 8, 2006 7:22:43 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/5.5.15
    Dec 8, 2006 7:22:43 AM org.apache.catalina.core.StandardHost start
    INFO: XML validation disabled
    Dec 8, 2006 7:22:43 AM org.apache.catalina.startup.HostConfig deployDescriptor
    WARNING: A docBase /opt/zimbra/apache-tomcat-5.5.15/webapps/zimbra inside the host appBase has been specified, and will be ignored
    log4j:WARN No appenders could be found for logger (org.apache.catalina.session.ManagerBase).
    log4j:WARN Please initialize the log4j system properly.
    Zimbra server reserving server socket port=110 bindaddr=null ssl=false
    Zimbra server reserving server socket port=995 bindaddr=null ssl=true
    Zimbra server reserving server socket port=143 bindaddr=null ssl=false
    Zimbra server reserving server socket port=993 bindaddr=null ssl=true
    Zimbra server process is running as root, changing to user=zimbra uid=501 gid=501
    Zimbra server process, after change, is running with uid=501 euid=501 gid=501 egid=501
    It may be worth mentioning that I'm getting a exception message in the zimbra.log file. here's the partial content:
    2006-12-08 08:14:11,894 INFO [main] [] soap - Servlet SoapServlet starting up
    2006-12-08 08:14:11,920 INFO [main] [] soap - Adding service AccountService to SoapServlet
    2006-12-08 08:14:11,998 INFO [main] [] soap - Adding service MailService to SoapServlet
    2006-12-08 08:14:12,117 INFO [main] [] soap - Adding service IMService to SoapServlet
    2006-12-08 08:14:12,123 INFO [main] [] misc - version=4.0.4_GA_457.FC5 release=20061115174033 builddate=20061115-1740 buildhost=wolfowitz.liquidsys.com
    2006-12-08 08:14:12,124 INFO [main] [] misc - LANG environment is set to: en_US.UTF-8
    2006-12-08 08:14:12,169 INFO [main] [] DbPool - Setting mysql connector property: maxActive=16
    2006-12-08 08:14:16,430 FATAL [main] [] system - Config initialization failed
    com.zimbra.cs.service.ServiceException: system failure: getting database connection
    at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
    at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 295)
    at com.zimbra.cs.util.Config.init(Config.java:70)
    at com.zimbra.cs.util.Config.initConfig(Config.java:9 7)
    at com.zimbra.cs.util.Config.getString(Config.java:10 9)
    at com.zimbra.cs.db.Versions.checkDBVersion(Versions. java:85)
    at com.zimbra.cs.db.Versions.checkVersions(Versions.j ava:81)
    at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:91)
    at com.zimbra.soap.SoapServlet.init(SoapServlet.java: 115)
    at javax.servlet.GenericServlet.init(GenericServlet.j ava:211)
    at org.apache.catalina.core.StandardWrapper.loadServl et(StandardWrapper.java:1105)
    at org.apache.catalina.core.StandardWrapper.load(Stan dardWrapper.java:932)
    at org.apache.catalina.core.StandardContext.loadOnSta rtup(StandardContext.java:3915)
    at org.apache.catalina.core.StandardContext.start(Sta ndardContext.java:4176)
    at org.apache.catalina.core.ContainerBase.addChildInt ernal(ContainerBase.java:759)
    at org.apache.catalina.core.ContainerBase.addChild(Co ntainerBase.java:739)
    at org.apache.catalina.core.StandardHost.addChild(Sta ndardHost.java:524)
    at org.apache.catalina.startup.HostConfig.deployDirec tory(HostConfig.java:910)
    at org.apache.catalina.startup.HostConfig.deployDirec tories(HostConfig.java:873)
    at org.apache.catalina.startup.HostConfig.deployApps( HostConfig.java:474)
    at org.apache.catalina.startup.HostConfig.start(HostC onfig.java:1118)
    at org.apache.catalina.startup.HostConfig.lifecycleEv ent(HostConfig.java:310)
    at org.apache.catalina.util.LifecycleSupport.fireLife cycleEvent(LifecycleSupport.java:119)
    at org.apache.catalina.core.ContainerBase.start(Conta inerBase.java:1020)
    at org.apache.catalina.core.StandardHost.start(Standa rdHost.java:718)
    at org.apache.catalina.core.ContainerBase.start(Conta inerBase.java:1012)
    at org.apache.catalina.core.StandardEngine.start(Stan dardEngine.java:442)
    at org.apache.catalina.core.StandardService.start(Sta ndardService.java:450)
    at org.apache.catalina.core.StandardServer.start(Stan dardServer.java:700)
    at org.apache.catalina.startup.Catalina.start(Catalin a.java:551)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.catalina.startup.Bootstrap.start(Bootst rap.java:275)
    at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:406)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.zimbra.cs.launcher.TomcatLauncher.start(Tomcat Launcher.java:52)
    at com.zimbra.cs.launcher.TomcatLauncher.main(TomcatL auncher.java:74)
    Caused by: java.sql.SQLException: Server connection failure during transaction. Due to underlying exception: 'java.net.SocketException: java.net.ConnectException: Connection refused'.
    Can anyone shed some light on this?
    Thank you,

    Jorge Henriquez
    Support Systems Analyst, Sr.
    The Biodesign Institute
    Arizona State University.

  2. #2
    Join Date
    Nov 2006
    Posts
    177
    Rep Power
    8

    Default

    You may have verified this already but have you verified that mysql is up and running? If not your real issue may be somewhere else.

  3. #3
    Join Date
    Dec 2006
    Posts
    8
    Rep Power
    8

    Default

    Thanks for the tip.

    I have verified mysql to be running.
    It may be worth mentioning also, that I have completly uninstalled / reinstalled the application several times with the same result.

    Jorge.

  4. #4
    Join Date
    Nov 2006
    Posts
    177
    Rep Power
    8

    Default

    1) I assume you have yet to get Zimbra running ?
    2) I assume you have run into the same problem each time?

    Check the following:

    1) Make sure the system/distribution does not have another version of httpd, tomcat, or mysql running. Typically mysqld will startup early in the boot process and I believe zimbra starts afterward. Mysql will silently fail but zimbra will still probably comeup.

    2) If you are sure that the correct mysql and services are running then I would wipe/copy all the logs off somewhere and do a fresh restart of zimbra. Then investigate every logfile. I bet you will see an error somewhere else as well.

  5. #5
    Join Date
    Dec 2006
    Posts
    8
    Rep Power
    8

    Default

    Thanks,
    I tried your suggestion(s).

    I ensured there were no servers running prior to installation.

    All of the logs appear to be blank or have non-relevant information, with the exception of the information already provided.

    Jorge.

  6. #6
    Join Date
    Dec 2006
    Posts
    8
    Rep Power
    8

    Default Additional Information:

    Running zmprov returns the following error:
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    Not sure if it's relevant.

    Jorge.

  7. #7
    Join Date
    Nov 2006
    Posts
    177
    Rep Power
    8

    Default

    Any chance there are policies in iptables that could be affecting MySQL?

    Can you connect to MySQL from a command line client?

  8. #8
    Join Date
    Dec 2006
    Posts
    8
    Rep Power
    8

    Default

    I can connect to MySQL,
    Here's the command results:
    [zimbra@rufus log]$ mysqladmin status
    Uptime: 7169 Threads: 1 Questions: 63 Slow queries: 0 Opens: 11 Flush tables: 1 Open tables: 5 Queries per second avg: 0.009
    [zimbra@rufus log]$
    I have disabled both firewall ans selinux.

  9. #9
    Join Date
    Dec 2006
    Posts
    8
    Rep Power
    8

    Default

    The issue has been resolved.
    I had a typo in my /etc/host file.

    My apologies, and thank you for your suggestions.

    At least I can get to the login screen now.

  10. #10
    Join Date
    Nov 2006
    Posts
    177
    Rep Power
    8

    Default

    I am curious as to what type would cause that? Did you have something like this example.

    real ip = 192.168.10.1

    in DNS
    A (address record) zimbra.mydomain.com 192.168.10.1

    in /etc/hosts

    192.168.10.2 zimbra.mydomain.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •