Welcome, if you would like to post a comment please register.
We also encourage you to explore all things Zimbra with our team and members of the community.
Today I restarted the zimbra services with zmcontrol stop and then start. Everything seems to start ok, but the the admin console and webmail never come up. I see several httpd processes running but nothing listenting on 443 or 7071. The only logs I've have noticed that I think might be related are below.
several of these in /var/log/zimbra.log
Feb 2 14:57:07 postal perdition[9412]: Fatal error establishing SSL connection to client
Feb 2 14:57:07 postal perdition[9413]: Fatal error establishing SSL connection to client
Feb 2 14:57:07 postal perdition[9414]: Fatal error establishing SSL connection to client
Feb 2 14:57:07 postal perdition[9415]: Fatal error establishing SSL connection to client
I enabled documents for one of my domains.
Tomcat is the only thing that shows as not running, but it doesn't show any errors when i start and stop it.
Host postal.insourcedsecurity.com
antispam Running
antivirus Running
imapproxy Running
ldap Running
logger Running
mailbox Stopped
tomcat is not running
mta Running
snmp Running
spell Running
zimbra server reserving server socket port=110 bindaddr=null ssl=false
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:111)
at com.zimbra.cs.util.NetUtil.bindServerSocket(NetUti l.java:134)
at com.zimbra.cs.util.NetUtil.bindTcpServerSocket(Net Util.java:63)
at com.zimbra.cs.servlet.PrivilegedServlet.init(Privi legedServlet.java:94)
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)
You have a POP server already running on your system. Most likely this is a runaway Zimbra process. Check the forums for how to detect and kill running Zimbra tomcat processes (a search for "ps kill" will probably work).
to make sure that it is the problem, if it is then run the command again and stop perdition. When you've done that do a tomcat start and remove the option in the Zimbra Admin UI.