I upgrade Zimbra 5.0.2 to 5.0.4 and I get Internal Server Error when my clients use Web Client HTML Version. Why this error and how I can fix this?...
Regards...
Omar
I upgrade Zimbra 5.0.2 to 5.0.4 and I get Internal Server Error when my clients use Web Client HTML Version. Why this error and how I can fix this?...
Regards...
Omar
su - zimbra
zmmailboxdctl stop
rm -rf /opt/zimbra/jetty/work/*
zmmailboxdctl start
tail -f /opt/zimbra/log/mailbox.log
tail -f /opt/zimbra/log/zmmailboxd.out
Visit the HTML client again & attach the dump errors to this thread.
-Mike Morse (MCode151)
ZCS-to-ZCS Migrations & Moves | Admin Tools & Tidbits » ZimbraBlog.com | ZimbraCommunity.com
Mike,
We are seeing this too now.
Here is the mailbox.log output FWIW. We'll try cleaning out the jetty work directory and then repost, but thought you might want to see this log file in the interim.
All the best,
Mark
2008-04-14 13:48:42,585 WARN [btpool0-527] [] log - Nested in org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP:
java.io.FileNotFoundException: no such file: /opt/zimbra/jetty-6.1.5/work/zimbra/jsp/org/apache/jsp/tag/web/message/displayMessage_tag.class
at org.apache.jasper.compiler.SmapUtil$SDEInstaller.(SmapUtil.java:242)
at org.apache.jasper.compiler.SmapUtil$SDEInstaller.i nstall(SmapUtil.java:214)
at org.apache.jasper.compiler.SmapUtil.installSmap(Sm apUtil.java:142)
at org.apache.jasper.compiler.Compiler.generateClass( Compiler.java:359)
at org.apache.jasper.compiler.Compiler.compile(Compil er.java:400)
at org.apache.jasper.JspCompilationContext.compile(Js pCompilationContext.java:592)
at org.apache.jasper.servlet.JspServletWrapper.loadTa gFile(JspServletWrapper.java:245)
at org.apache.jasper.compiler.TagFileProcessor.loadTa gFile(TagFileProcessor.java:667)
at org.apache.jasper.compiler.TagFileProcessor.access $000(TagFileProcessor.java:72)
at org.apache.jasper.compiler.TagFileProcessor$TagFil eLoaderVisitor.visit(TagFileProcessor.java:723)
at org.apache.jasper.compiler.Node$CustomTag.accept(N ode.java:1482)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.j ava:2257)
at org.apache.jasper.compiler.Node$Visitor.visitBody( Node.java:2307)
at org.apache.jasper.compiler.TagFileProcessor$TagFil eLoaderVisitor.visit(TagFileProcessor.java:727)
at org.apache.jasper.compiler.Node$CustomTag.accept(N ode.java:1482)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.j ava:2257)
at org.apache.jasper.compiler.Node$Visitor.visitBody( Node.java:2307)
at org.apache.jasper.compiler.Node$Visitor.visit(Node .java:2313)
at org.apache.jasper.compiler.Node$Root.accept(Node.j ava:481)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.j ava:2257)
at org.apache.jasper.compiler.TagFileProcessor.loadTa gFiles(TagFileProcessor.java:741)
at org.apache.jasper.compiler.Compiler.generateJava(C ompiler.java:207)
at org.apache.jasper.compiler.Compiler.compile(Compil er.java:398)
at org.apache.jasper.JspCompilationContext.compile(Js pCompilationContext.java:592)
at org.apache.jasper.servlet.JspServletWrapper.loadTa gFile(JspServletWrapper.java:245)
at org.apache.jasper.compiler.TagFileProcessor.loadTa gFile(TagFileProcessor.java:667)
at org.apache.jasper.compiler.TagFileProcessor.access $000(TagFileProcessor.java:72)
at org.apache.jasper.compiler.TagFileProcessor$TagFil eLoaderVisitor.visit(TagFileProcessor.java:723)
at org.apache.jasper.compiler.Node$CustomTag.accept(N ode.java:1482)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.j ava:2257)
at org.apache.jasper.compiler.Node$Visitor.visitBody( Node.java:2307)
at org.apache.jasper.compiler.TagFileProcessor$TagFil eLoaderVisitor.visit(TagFileProcessor.java:727)
at org.apache.jasper.compiler.Node$CustomTag.accept(N ode.java:1482)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.j ava:2257)
at org.apache.jasper.compiler.Node$Visitor.visitBody( Node.java:2307)
at org.apache.jasper.compiler.TagFileProcessor$TagFil eLoaderVisitor.visit(TagFileProcessor.java:727)
at org.apache.jasper.compiler.Node$CustomTag.accept(N ode.java:1482)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.j ava:2257)
at org.apache.jasper.compiler.Node$Visitor.visitBody( Node.java:2307)
at org.apache.jasper.compiler.Node$Visitor.visit(Node .java:2313)
at org.apache.jasper.compiler.Node$Root.accept(Node.j ava:481)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.j ava:2257)
at org.apache.jasper.compiler.TagFileProcessor.loadTa gFiles(TagFileProcessor.java:741)
at org.apache.jasper.compiler.Compiler.generateJava(C ompiler.java:207)
at org.apache.jasper.compiler.Compiler.compile(Compil er.java:398)
at org.apache.jasper.JspCompilationContext.compile(Js pCompilationContext.java:592)
at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:344)
at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:477)
at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:371)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:50)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:283)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.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(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.he aderComplete(HttpConnection.java:830)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
2008-04-14 13:48:42,585 WARN [btpool0-527] [] log - /zimbra/h/search: java.io.FileNotFoundException: no such file: /opt/zimbra/jetty-6.1.5/work/zimbra/jsp/org/apache/jsp/tag/web/message/displayMessage_tag.class
___________________________________
L. Mark Stone, Managing Member
"Uptime. All the time."®
Ten Years In Business! 2003 - 2013!
477 Congress Street, Suite 812 | Portland, ME 04101 | (207) 772-5678
proactive maintenance and monitoring | technology consulting
Zimbra groupware | cloud hosting | business continuity
Maine's only managed services and cloud hosting provider with a
SOC 2 Type II audit covering Security, Availability and Confidentiality
Mike,
After performing your steps above, we still get Internal Server Error when trying to use the HTML client.
zmmailboxd.out on restart shows:
CompilerOracle: exclude com/zimbra/cs/session/SessionMap.putAndPrune
0 INFO [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
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 reserving server socket port=7025 bindaddr=null ssl=false
2850 INFO [main] log - Setting umask=027
2853 INFO [main] log - Setting GID=1000
2853 INFO [main] log - Setting UID=1003
2854 INFO [main] log - jetty-6.1.5
3156 INFO [main] log - No Transaction manager found - if your webapp requires one, please configure one.
Zimbra server process is running as uid=1003 euid=1003 gid=1000 egid=1000
And mailbox.log output is attached.
Suggestions?
___________________________________
L. Mark Stone, Managing Member
"Uptime. All the time."®
Ten Years In Business! 2003 - 2013!
477 Congress Street, Suite 812 | Portland, ME 04101 | (207) 772-5678
proactive maintenance and monitoring | technology consulting
Zimbra groupware | cloud hosting | business continuity
Maine's only managed services and cloud hosting provider with a
SOC 2 Type II audit covering Security, Availability and Confidentiality
I can confirm the same error and error message in the log. I also get the I.S. error when browsing using my iPod Touch (using the Mobile view). I also upgraded from 5.0.2 -> 5.0.4 recently.
Update: I shut down the server, deleted most of the log files (I had a ton of them), and restarted. I also had deleted everything out of /jetty/work/ earlier. For right now, the HTML client appears to be working. However, when I go to the Calender section of the mobile version, I still get the Internal Server error.
This may not be related, the Mobile version is not currently showing the folder hierarchy properly - it is a flat list instead. The built in Mail.app on the iPod is also giving weird "cannot connect" errors, even though it works about 50% of the time, so this is quite frustrating, as you can guess. (I probably should put these complaints in a different thread.)
Last edited by OverZealous; 04-16-2008 at 05:01 PM. Reason: Providing more information
- Phil DeJarnett
There are currently 1 users browsing this thread. (0 members and 1 guests)