Zimlets not working

[mclain]

I'm not sure if the upgrade effected them or what but none of our zimlets our working. I'm talking basic preinstalled zimlets. Date,url,etc. We are using 5.01. Any help would be appreciated. Thanks

[JoshuaPrismon]

Originally Posted by mclain

I'm not sure if the upgrade effected them or what but none of our zimlets our working. I'm talking basic preinstalled zimlets. Date,url,etc. We are using 5.01. Any help would be appreciated. Thanks

Are the zimlet's enabled in the console window?

[mclain]

Yes they are. Just some more information. I've tried uninstalling and reinstalling the zimlets to see if I could get them to work. Also, as browsers are concerned I've tried using IE7 and FireFox.

[jholder]

Things to look at:

When you deploy, look at mailbox.log for errors
install firebug
when a user logs in, look at mailbox.log for zimlet errors

[mclain]

This is from the mailbox.log after redeploying zimlet

mailbox - FileUploadServlet received Upload: { accountId=9c5f8473-f525-4d3a-bf93-0c9550c05fad, time=Fri Jan 25 06:39:34 EST 2008, uploadId=98e74ec4-8ce2-41c8-88b7-c49218dcba92:0ac06c3a-d3ed-474d-8c42-ca82698ebed3, com_zimbra_date.zip}
2008-01-25 06:39:34,990 INFO [Thread-623] [] zimlet - Deploying Zimlet com_zimbra_date in LDAP.
2008-01-25 06:39:34,991 WARN [Thread-623] [] misc - checkValue: no attribute info for: zimbraZimletServerIndexRegex
2008-01-25 06:39:34,991 WARN [Thread-623] [] misc - checkValue: no attribute info for: zimbraZimletHandlerClass
2008-01-25 06:39:34,996 INFO [Thread-623] [] zimlet - Installing Zimlet com_zimbra_date on this host.
2008-01-25 06:39:35,008 INFO [Thread-623] [] zimlet - Adding Zimlet com_zimbra_date to COS default
2008-01-25 06:39:35,016 INFO [Thread-623] [] zimlet - Enabling Zimlet com_zimbra_date
2008-01-25 06:39:35,021 INFO [Thread-623] [] zimlet - Skipping on zimbra.fstrf.org

[mclain]

Also saw this error in firebug

body><h2>HTTP ERROR: 500</h2><pre>INTERNAL_SERVER_ERROR</pre>

<p>RequestURI=/service/zimlet/res/Zimlets-nodev_all.css</p><h3>Caused by:</h3><pre>java.lang.NullPoi

nterException

at com.zimbra.cs.zimlet.ZimletFilter.doFilter(ZimletF ilter.java:108)

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)

[drb]

I noticed all zimlets had stopped working on my installation of 5.0.0_RC1

Troubleshooting (backtracking) showed that switching Zimbra to port 81 to coexist with apache was the reason. Switching back to port 80 restored zimlet function. Switching to port 81 stopped them again. Proven through two cycles of change (just to be sure!).

Note that this is not 5.0.1 -- it's 5.0.0_RC1. YMMV.

Cheers -- Ross

[drb]

Replying to my own post:

This is known bug 22434: Bug 22434 - All Zimlets break on non-standard http port
Port numbers are hard-coded in /opt/zimbra/jetty-6.1.5/etc/service.web.xml.in
Change from 80 or 443 stops Zimlets from working.

Fix is as given in Bugzilla

Cheers -- Ross

[mclain]

We are using 443 so that is not the issue. I noticed that the only zimlet that shows up is the local zimlet for all of our users even though all users have been given access to all.

[Ikemp]

my zimblets work with the exceptionn of Google Translator and wikipedia