Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators
Reload this Page problem with theme when migrating from 6.x to 7.1.1

Welcome to the Zimbra :: Forums!
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.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-22-2011, 12:15 AM
Senior Member
  
Posts: 68
Default problem with theme when migrating from 6.x to 7.1.1
I created a custom skin used on Zimbra Community 6.x. Today i migrated to 7.1.1 and i lost my custom skin. I deployed and when the user hit on login button, the screen freeze and not follow..

Checking log (mailbox.log) i saw this:
2011-06-22 02:11:54,580 ERROR [btpool0-16://serverzimbra.com/zimbra/] [] log - /zimbra/
java.lang.IllegalStateException: Committed
at org.mortbay.jetty.Response.resetBuffer(Response.ja va:1023)
at javax.servlet.ServletResponseWrapper.resetBuffer(S ervletResponseWrapper.java:202)
at org.mortbay.servlet.GzipFilter$GZIPResponseWrapper .resetBuffer(GzipFilter.java:310)
at org.mortbay.servlet.GzipFilter$GZIPResponseWrapper .sendError(GzipFilter.java:325)
at javax.servlet.http.HttpServletResponseWrapper.send Error(HttpServletResponseWrapper.java:128)
at org.mortbay.jetty.servlet.DefaultServlet.doGet(Def aultServlet.java:425)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:705)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.servlet.Dispatcher.include(Dispa tcher.java:195)
at org.apache.jasper.runtime.JspRuntimeLibrary.includ e(JspRuntimeLibrary.java:1013)
at org.apache.jsp.public_.launchZCS_jsp._jspService(l aunchZCS_jsp.java:365)
at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:389)
at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:486)
at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:380)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:64)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispa tcher.java:330)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispa tcher.java:126)
at org.apache.jasper.runtime.PageContextImpl.forward( PageContextImpl.java:783)
at org.apache.jsp.public_.login_jsp._jspx_meth_c_othe rwise_5(login_jsp.java:1887)
at org.apache.jsp.public_.login_jsp._jspx_meth_c_choo se_6(login_jsp.java:1633)
at org.apache.jsp.public_.login_jsp._jspx_meth_c_when _8(login_jsp.java:1605)
at org.apache.jsp.public_.login_jsp._jspx_meth_c_choo se_5(login_jsp.java:1572)
at org.apache.jsp.public_.login_jsp._jspx_meth_c_othe rwise_4(login_jsp.java:1435)
at org.apache.jsp.public_.login_jsp._jspx_meth_c_choo se_3(login_jsp.java:1224)
at org.apache.jsp.public_.login_jsp._jspx_meth_c_if_2 (login_jsp.java:1196)
at org.apache.jsp.public_.login_jsp._jspService(login _jsp.java:387)
at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:389)
at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:486)
at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:380)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:64)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispa tcher.java:330)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispa tcher.java:126)
at org.mortbay.jetty.servlet.DefaultServlet.doGet(Def aultServlet.java:500)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:705)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.webClient.filters.ForwardFilter.doFilte r(ForwardFilter.java:61)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:239)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
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:1157)
at com.zimbra.webClient.filters.CharEncodingFilter.do Filter(CharEncodingFilter.java:35)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.he aderComplete(HttpConnection.java:929)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)


Do i need create again my custom skin?
Reply With Quote
  #2 (permalink)  
Old 06-22-2011, 12:50 AM
Trained Alumni
  
Posts: 160
Default
Hi,

Any upgrades will remove customizations including themes. Best thing to do, before the upgrade, is to save the custom theme to another directory outside of /opt/zimbra. After the upgrade is completed, you should be able to put the custom theme back into zimbra with the 'zmskindeploy' command.

Regards
Reply With Quote
  #3 (permalink)  
Old 06-22-2011, 12:56 AM
Senior Member
  
Posts: 68
Default
I saved my custom skin and deployed again, but it appear to be some problems with the styles or some like that..
Reply With Quote
  #4 (permalink)  
Old 11-03-2011, 07:03 AM
Active Member
  
Posts: 45
Default
Hi!

I had the same problem and mine resolved to a missing file, which Zimbra couldn't load. You can check by turning up jetty's logging level to DEBUG by changing these lines

Code:
%%uncomment VAR:!zimbraLogToSyslog%%log4j.rootLogger=INFO,LOGFILE
%%uncomment VAR:zimbraLogToSyslog%%log4j.rootLogger=INFO,LOGFILE,SYSLOG
to

Code:
#%%uncomment VAR:!zimbraLogToSyslog%%log4j.rootLogger=INFO,LOGFILE
#%%uncomment VAR:zimbraLogToSyslog%%log4j.rootLogger=INFO,LOGFILE,SYSLOG
log4j.rootLogger=DEBUG,LOGFILE
and restarting mailboxd. After that check the position directly above the exception in mailboxd.log. In my case, Zimbra was trying to load something from my skin directory that wasn't there.

Don't forget to undo your logging configuration once done.

Kind regards
Dennis
Reply With Quote
  #5 (permalink)  
Old 02-14-2012, 07:54 AM
Starter Member
  
Posts: 1
Default Re:
Seems that 7.X requires that img/images.css.js and img/images.css be REQUIRED files in any skin folder, even if they are blank.
Reply With Quote
Reply

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.