Servlet SoapServlet is currently unavailable? How do I fix this? mailbox.log

[nfear24]

I'm in desperate need of some help. All my mailbox.log files are showing thousands of lines of this:

2007-03-28 00:31:44,449 INFO [http-81-Processor99] [] [SoapServlet] - Servlet SoapServlet is currently unavailable
2007-03-28 00:31:49,594 INFO [http-81-Processor93] [] [SoapServlet] - Servlet SoapServlet is currently unavailable
2007-03-28 00:31:54,457 INFO [http-81-Processor92] [] [SoapServlet] - Servlet SoapServlet is currently unavailable
2007-03-28 00:31:59,462 INFO [http-81-Processor88] [] [SoapServlet] - Servlet SoapServlet is currently unavailable

So Now I cant login to my email or admin page. Does anyone have any guidance or help?

Thanks Nick

[jholder]

er,
There's gonna be more in the log than just the unavailable line.

Look for some java backtrace code, and more specifically the "Caused By:" Line.

If you can't find it, then take a look at the catalina.out log to see what's in there.

[nfear24]

I have found this. Does this help my cause any on how I can fix this. At the very bottom there is a caused by:

2007-03-29 09:15:43,995 FATAL [main] [] soap - Unable to start servlet
com.zimbra.common.service.ServiceException: system failure: Could not bind to port=7025 bindaddr=tickus.com ssl=false useChannels=false
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:175)
at com.zimbra.cs.util.NetUtil.getServerSocket(NetUtil .java:83)
at com.zimbra.cs.util.NetUtil.getTcpServerSocket(NetU til.java:51)
at com.zimbra.cs.lmtpserver.LmtpServer.startupLmtpSer ver(LmtpServer.java:195)
at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:144)
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.net.BindException: Cannot assign requested address

my problems all seem to have started when I screwed this line up:

zmprov md domain.com zimbraMailCatchAllAddress @domain.com zimbraMailCatchAllCanonicalAddress @mail.domain.com

anyway to undo commands?

[jholder]

Well, It can't bind to 7075 because somethings already running on it.
If you're convinced nothing is running on 7075, then do a zmcontrol stop, and telnet localhost 7075
or
telnet hostname.domain.com 7075

If you get in, then then you've got something other than Zimbra running on that port, and need to stop it before going any further.

[jholder]

Try:
zmprov md domain.com -zimbraMailCatchAllAddress @domain.com -zimbraMailCatchAllCanonicalAddress @mail.domain.com

[nfear24]

Originally Posted by jholder

Well, It can't bind to 7075 because somethings already running on it.
If you're convinced nothing is running on 7075, then do a zmcontrol stop, and telnet localhost 7075
or
telnet hostname.domain.com 7075

If you get in, then then you've got something other than Zimbra running on that port, and need to stop it before going any further.

jholder: I just tried to telnet to 7025 and connection is refused and I also used netstat to make sure nothing was running on that port and nothing is there.


If I try to run the zmprov command I get this:

zimbra@mail:/home/nick$ zmprov md tickus.com -zimbraMailCatchAllAddress @tickus.com -zimbraMailCatchAllCanonicalAddress @mail.tickus.com

ERROR: zclient.IO_ERROR (invoke unable to parse response: <html><head><title>Apache Tomcat/5.5.15 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 404 - Servlet AdminServlet is not available</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Servlet AdminServlet is not available</u></p><p><b>description</b> <u>The requested resource (Servlet AdminServlet is not available) is not available.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/5.5.15</h3></body></html>, server: localhost) (cause: com.zimbra.soap.SoapParseException unable to parse response: <html><head><title>Apache Tomcat/5.5.15 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 404 - Servlet AdminServlet is not available</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Servlet AdminServlet is not available</u></p><p><b>description</b> <u>The requested resource (Servlet AdminServlet is not available) is not available.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/5.5.15</h3></body></html>)


Nick

[dkarp]

Whoops! He meant 7025, not 7075.

[nfear24]

Originally Posted by dkarp

Whoops! He meant 7025, not 7075.

Ya I actually noticed that and there is nothing else binding to that port either: 7025. I'm really stuck on this problem and have yet to find anyone else with this exact problem or solution.

Nick

[nfear24]

Originally Posted by dkarp

Whoops! He meant 7025, not 7075.

I do not understand why zimbra cant bind to port 7025 when nothing is using that port and I cant telnet to that port either. I continue to get this error:

system failure: Could not bind to port=7025

Man Im pulling my hair out on this one.

Thanks Nick

[jholder]

Make sure you have a backup, and try rerunning the ./zmsetup.pl script.