Upgraded to 5.0.9 from 4.5.10 - Now web client does not work ?

Ask questions about your setup or get help installing ZCS server (ZD section below).
lchrist
Posts: 24
Joined: Fri Sep 12, 2014 10:23 pm

Upgraded to 5.0.9 from 4.5.10 - Now web client does not work ?

Postby lchrist » Wed Oct 01, 2008 5:09 pm

Hi all,
I just upgraded to 5.0.9 (10.4 OS X platform) a couple of hours ago, and for some reason the web client does not work anymore. Restarted services and even rebooted the system, but it still does not work.
I'm getting the "usual" "A network service error has occurred (zclient/io)" for both firefox 3 and for Apple Safari. Tried all "versions" (ajax, default, HTML).
Admin pages work, and external imap clients work without any problems.
when looking at the /opt/zimbra/log/mailbox.log i get the following error:
[QUOTE]2008-10-01 23:52:38,195 INFO [btpool0-10] [ip=127.0.0.1;] soap - GetDomainInfoRequest

2008-10-01 23:52:49,432 WARN [btpool0-1] [] webclient - local exception

com.zimbra.cs.zclient.ZClientException: invoke unable to parse response:



404 Not Found



Not Found



The requested URL /service/soap was not found on this server.



Additionally, a 404 Not Found

error was encountered while trying to use an ErrorDocument to handle the request.




Apache/1.3.41 Server at localhost Port 16080



ExceptionId:btpool0-1:1222897969432:8c319a07d3eb1222

Code:zclient.IO_ERROR

at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZClientException.java:47)

at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:530)

at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:520)

at com.zimbra.cs.zclient.ZMailbox.authByPassword(ZMailbox.java:465)

at com.zimbra.cs.zclient.ZMailbox.(ZMailbox.java:375)

at com.zimbra.cs.zclient.ZMailbox.getMailbox(ZMailbox.java:324)

at com.zimbra.cs.taglib.tag.LoginTag.doTag(LoginTag.java:123)

at org.apache.jsp.public_.login_jsp._jspService(login_jsp.java:277)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820)

at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)

at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:477)

at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:371)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820)

at com.zimbra.webClient.servlet.JspServlet.service(JspServlet.java:50)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)

at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:268)

at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)

at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:465)

at org.mortbay.jetty.servlet.DefaultServlet.doPost(DefaultServlet.java:496)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)

at com.zimbra.webClient.filters.SetHeaderFilter.doFilter(SetHeaderFilter.java:283)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)

at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)

at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)

at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)

at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)

at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:350)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)

at org.mortbay.jetty.Server.handle(Server.java:313)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)

at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)

at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)

at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)

Caused by: com.zimbra.common.soap.SoapParseException: unable to parse response:



404 Not Found



Not Found



The requested URL /service/soap was not found on this server.



Additionally, a 404 Not Found

error was encountered while trying to use an ErrorDocument to handle the request.




Apache/1.3.41 Server at localhost Port 16080



at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:216)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:251)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:297)

at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:526)

... 50 more

[/QUOTE]

But have no idea what might be wrong !
Any pointers ??
Thanks in advance,
Lasse,


dwmtractor
Outstanding Member
Outstanding Member
Posts: 993
Joined: Fri Sep 12, 2014 10:41 pm

Upgraded to 5.0.9 from 4.5.10 - Now web client does not work ?

Postby dwmtractor » Thu Oct 02, 2008 11:07 am

Have you tried logging in from a different computer (on your LAN)? You might find that you need to either (1) clear your browser cache, or (2) delete and re-import the SSL certificate for the page to show, since changes that happen during upgrade sometimes make a browser think it's seeing a hacked page. Unfortunately, browsers often give you a 404 rather than the honest answer that it thinks the server is hacked. . .
lchrist
Posts: 24
Joined: Fri Sep 12, 2014 10:23 pm

Upgraded to 5.0.9 from 4.5.10 - Now web client does not work ?

Postby lchrist » Thu Oct 02, 2008 11:23 am

This is from the mailbox log. So it is definitely Zimbra who's giving me the error.
14319KevinH
Ambassador
Ambassador
Posts: 4558
Joined: Fri Sep 12, 2014 9:52 pm

Upgraded to 5.0.9 from 4.5.10 - Now web client does not work ?

Postby 14319KevinH » Tue Oct 14, 2008 12:02 am

looks like you've got some custom port setting to port 16080. You should verify you've got it set right or go back to the defaults to make it work again.

Return to “Installation and Upgrade”

Who is online

Users browsing this forum: No registered users and 5 guests