Tomcat not starting

[Rick Baker]

I accidently changed some ssl ports. Now Tomcat will not start. See attatched.

Can I edit a file manually to fix this.



Sep 6, 2006 3:05:53 PM 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=7110 bindaddr=zimbra.guardnet.com ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Fatal error: terminating: PrivilegedServlet init failed
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java :359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at com.zimbra.cs.util.NetUtil.newBoundServerSocket(Ne tUtil.java:78)
at com.zimbra.cs.util.NetUtil.reserveServerSocket(Net Util.java:101)
at com.zimbra.cs.servlet.PrivilegedServlet.init(Privi legedServlet.java:99)
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)

[andreychek]

I accidently changed some ssl ports. Now Tomcat will not start. See attatched.

Fatal error: terminating: PrivilegedServlet init failed
java.net.BindException: Address already in use

Well, I don't really know how to solve this, but since no one else has replied, I'll toss out some ideas :-)

First off -- in general, changing the SSL port shouldn't prevent Tomcat from starting. But, do you happen to know what port it was changed to?

It looks like it's failing, because an address is already in use. Often, that's because parts of Zimbra are still running. After running /etc/init.d/zimbra stop, maybe you could also look through the 'ps aux' output and verify no processes belonging to zimbra are running.

With any luck, after killing any existing processes, starting Zimbra would proceed flawlessly ;-)
-Eric