Page 5 of 6

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Fri Oct 02, 2009 8:08 pm
by dave_kempe
OK,

logged into admin console.

Click zimlets, click com_zimbra_social

Click undeploy, click yes on are you sure?

Click out of zimlets, and back in and com_zimbra_social is not in the list of zimlets anymore

run zmprov fc zimlet as zimbra on the server

Click deploy in admin console.

browse to downloaded version from the gallery.

Tick flush zimlet cache

Click deploy

mailbox log says this:

009-10-03 10:58:56,366 INFO [Thread-62855] [] zimlet - Installing Zimlet com_zimbra_social on this host.

2009-10-03 10:58:56,378 INFO [Thread-62855] [] zimlet - Upgrading Zimlet com_zimbra_social to 2.1.4

2009-10-03 10:58:56,507 INFO [Thread-62855] [] zimlet - Installing Zimlet config for com_zimbra_social

2009-10-03 10:58:56,635 INFO [Thread-62855] [] zimlet - Adding Zimlet com_zimbra_social to COS default

2009-10-03 10:58:56,725 INFO [Thread-62855] [] zimlet - Enabling Zimlet com_zimbra_social

2009-10-03 10:58:56,808 INFO [Thread-62855] [] zimlet - Skipping on subserve.sol1.net
I log back into my accounts, the social tab loads a little after logging in,

clicking on it generates the 403 error again.
I try and add my facebook account again, go through the steps successfully: facebook says "You may now close this window and return to the application."

I click OK, on the facebook account window, and nothing happens.

I click OK again, and the window closes, goes back to the list of accounts and the facebook account is not added.

Clicking refresh accounts doesn't work.

I know this zimlet works, as on the same server I can create a fresh account and it works no problems.

Other old accounts on the same domain have exactly the same problem. New accounts on the same domain with the same class of service have the problem. New domains don't seem to have the problem.
OK, I just narrowed it down. The particular class of service is the problem. Any ideas why one class of service would give errors and the others wouldn't?

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Fri Oct 02, 2009 10:46 pm
by rrao
[quote user="dave_kempe"]

OK, I just narrowed it down. The particular class of service is the problem. Any ideas why one class of service would give errors and the others wouldn't?[/QUOTE]

for both COSes, run,

 zmprov gc  | grep zimbraZimletAvailableZimlets 

and see if they both match. I think you don't have few domains listed on it.


For all the missing domains, add each one of them using:

 zmprov mc  +zimbraProxyAllowedDomains  

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Sat Oct 03, 2009 7:29 am
by jurg
[QUOTE]you've right,
im using german language, and after switching to usa english, the social tab appeared - and i get the first task reminder. It never was displayed when german language was in use.[/QUOTE]
This appears to be my problem too. The social tab appears when I switch to English.

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Mon Oct 05, 2009 10:25 am
by xander2k
Now i have the same problem as described first.
I made a new Facebook account and add it to zimbra social. In both windows will success displayed but the account never appears in the list.

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Tue Oct 06, 2009 5:25 am
by xander2k
On a zimbra account that have not used the old social zimlet that doesn't worked, the new zimlet works fine without Error 403. Only on the one who has tested the old one, the new one makes an Java IO Error:
[QUOTE]org.mortbay.io.RuntimeIOException: java.io.IOException: Closed

at org.mortbay.io.UncheckedPrintWriter.write(UncheckedPrintWriter.java:183)

at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:181)

at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:237)

at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:173)

at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:124)

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

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

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:389)

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

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

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:66)

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

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

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:765)

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

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

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

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

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

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:502)

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

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

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

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

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

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

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

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:765)

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

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(HandlerWrapper.java:152)

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

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

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

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

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

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

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

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

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

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

Caused by: java.io.IOException: Closed

at org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:629)

at org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:579)

at java.io.ByteArrayOutputStream.writeTo(ByteArrayOutputStream.java:109)

at org.mortbay.jetty.AbstractGenerator$OutputWriter.write(AbstractGenerator.java:903)

at org.mortbay.io.UncheckedPrintWriter.write(UncheckedPrintWriter.java:174)

... 49 more

[/QUOTE]

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Tue Oct 06, 2009 6:45 am
by xander2k
with a new COS it works, but the socialize button in the email tab to post emails can't be disabled and in the most emails the button not work and the sozial tab doesn't work anymore (no updates in and out possible). A Browser refresh is needed.

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Sun Oct 11, 2009 6:45 pm
by 354phingers
Tried the tips listed, and the social tab does not show up in normal mode, and my language is english.
So i added the ?dev=1 flag on, and then the social tab shows up.
But when I click on any of the digg links on the left, I get a yellow alert box stating:


digg error:
http error 403
problem accessing /service proxy. Reason:
forbidden


So do I need proxy module installed?
Thoughts?
powered by Jetty://

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Mon Oct 12, 2009 4:36 am
by xander2k
Try to create a new COS and take a new User with this COS to test the social tab.

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Mon Oct 12, 2009 7:17 am
by 354phingers
I tried creating a brand new COS, and a new user, logged in as that user, and no social tab.
I tried disabling all the zimlets except the social one, and still nothing, unless I enable debugging.
Any other ideas?

ZCS 6.0.1 Zimlets that doesn't work anymore

Posted: Mon Oct 12, 2009 9:29 am
by rrao
[quote user="354phingers"]I tried creating a brand new COS, and a new user, logged in as that user, and no social tab.
I tried disabling all the zimlets except the social one, and still nothing, unless I enable debugging.
Any other ideas?[/QUOTE]
you must be hitting some JS error.
In firebug, Tools> Error console > (click on Errors Button) and see if it shows any