[SOLVED]Mail:Parent must be a subclass of Composite Fehlercode: -1 Method: DwtControl

Printable View

Show 40 post(s) from this thread on one page

09-07-2011, 12:52 PM
chefkoch009

[SOLVED]Mail:Parent must be a subclass of Composite Fehlercode: -1 Method: DwtControl

Hi @all,

i use ZCS NE 6.0.14 and I tried to install zextras_migration_tool_1.0.0-RC3 on mbs1. We have 2 mbs (mbs1 and mbs2).
The result from CLI:

Code:

Checking whether the Core is already installed ... ZeXtras Migration Tool Core detected. Deploying zimlet ... [] INFO: Deploying on mbs1.verwaltung.regenbogen-ag.de [] INFO: Deploy initiated. Check the server's mailbox.log for the status. [] INFO: Deploying on mbs2.verwaltung.regenbogen-ag.de [] INFO: Deploy initiated. Check the server's mailbox.log for the status. [] INFO: Skipping on mta.verwaltung.regenbogen-ag.de [] INFO: Skipping on zldap.verwaltung.regenbogen-ag.de The ZeXtras Migration Tool Zimlet has been successfully installed. =========================== [root@MBS1 zextras_migration_tool-1.0.0-RC3]#

Everything seems to be fine. zmcontrol looks good, too.
But now on the Zimbra-Admin Console i get following error Msg Box:

Unknown Error:
Mail: Parent must be a subclass of Composite Errorcode: -1 Method DwtControl.

Does anybody have a solution for this problem, or is it a bug?
09-07-2011, 01:59 PM
Cine

Hello chefkoch009, and welcome to the Forums!

We are investigating the problem, I'll post here as soon as the Dev team gives me feedback.

In the meantime you can use the 'zxsuite' Command Line Interface to export your data - see the guide at ZxMig CLI - ZeXtras Suite Wiki

Have a nice day,
Cine
09-07-2011, 03:07 PM
kral

Hi, I'm kral of the ZeXtras Dev Team.

Could you please send us the output of this command:

Code:

zmzimletctl info com_zextras_zxmig

We want to be sure about the version of the installed zimlet.

Cheers,
09-07-2011, 04:08 PM
Cine
Hello everybody!

We found and corrected the bug causing this error.
This is a zimlet-related error, so you can safely deploy the new zimlet as it follows:
- Download the updated package to your server (from the ZeXtras Website with wget)
- Unpack it in your server
- Enter the unpacked directory
- Run `./install zimlet`
Affected ZeXtras versions: 1.0.0-RC3 running on a Zimbra 6.x Server (Both ZeXtras Suite and ZeXtras Migration Tool)
Bugzilla Link: http://bugzilla.zextras.com/show_bug.cgi?id=14
09-07-2011, 08:21 PM
chefkoch009

thanks for your fast response.

I tried both ways. After installation i also did zmcontrol stop /start on each mbs. zimbra started successfully, but now i get this message in the WebUI:

JavaScript-Fehler in method ZaOverviewPanelController.prototype._overviewTreeL istener
message: this._headerList is undefined fileName: https://192.168.131.151:7071/service...55&language=de lineNumber: 21729 stack: ([object Object],[object Object],true,0)@https://192.168.131.151:7071/service/zimlet/res/Zimlets-nodev_all.js.zgz.js?v=1108...

should i remove the "old" zimlet with "./install -u zimlet" before installing the new one?

Code:

[zimbra@MBS1 ~]$ zmzimletctl info com_zextras_zxmig Zimlet com_zextras_zxmig Version: 1.0.0 Description: ZeXtras Migration Tool Priority: 18 Enabled: true Indexing Enabled: true Extension: true Activated in COS: null Config: <zimletConfig name="com_zextras_zxmig" version="1.0.0"><global/></zimletConfig> Scripts: zxutils.js, zxmodule_controller.js, zxmodule.js, zxmodule_listcontroller.js, zxmodule_listview.js, zxmodule_view.js, zxbase.js, modules/module_zxmig.js, modules/module_notifications.js, modules/wizards/zxmig_wizard.js, zxwizard.js, zxbase_bottom.js CSS: com_zextras_zextras.css [zimbra@MBS1 ~]$
09-07-2011, 08:49 PM
chefkoch009

now i uninstalled the zmextras package completly with "install -u all", then i installed the fresh downloaded package with "install all", but without success.

Code:

Deploying zimlet ... [] INFO: Deploying on mbs1.verwaltung.regenbogen-ag.de [] INFO: Deploy initiated. Check the server's mailbox.log for the status. [] INFO: Deploying on mbs2.verwaltung.regenbogen-ag.de [] INFO: Deploy initiated. Check the server's mailbox.log for the status. [] INFO: Skipping on mta.verwaltung.regenbogen-ag.de [] INFO: Skipping on zldap.verwaltung.regenbogen-ag.de The ZeXtras Migration Tool Zimlet has been successfully installed.

And while reading the log, i recognized following:

Code:

2011-09-07 20:36:18,293 INFO [btpool0-9://192.168.131.151:7071/service/admin/soap/zextras] [name=admin@zldap.verwaltung.regenbogen-ag.de;mid=2;ip=10.12.55.6;ua=ZimbraWebClient - FF3.0 (Linux);] extensions - ZeXtras API Manager: Proxying request ZxCore/getLicenseInfo to: mbs1.verwaltung.regenbogen-ag.de, mbs2.verwaltung.regenbogen-ag.de 2011-09-07 20:36:18,294 INFO [ZxLink Handler] [] extensions - ZeXtras API Manager: Exec: ZxCore/getLicenseInfo 2011-09-07 20:36:18,295 WARN [btpool0-9://192.168.131.151:7071/service/admin/soap/zextras] [name=admin@zldap.verwaltung.regenbogen-ag.de;mid=2;ip=10.12.55.6;ua=ZimbraWebClient - FF3.0 (Linux);] extensions - ZeXtras API Manager: Exception: Unable to connect to server: mbs2.verwaltung.regenbogen-ag.de at com.zextras.lib.ZEClientHelper.openStream(Unknown Source) at com.zextras.lib.ZEPublicAPIManager.proxyRequest(Unknown Source) at com.zextras.lib.ZEPublicAPIManager.execPAPIRequest(Unknown Source) at com.zextras.lib.ZESOAPBackend.handle(Unknown Source) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181) at javax.servlet.http.HttpServlet.service(HttpServlet.java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) 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:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.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(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.handler.DebugHandler.handle(DebugHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) ... 39 more 2011-09-07 20:36:18,538 INFO [btpool0-9://192.168.131.151:7071/service/admin/soap/zextras] [name=admin@zldap.verwaltung.regenbogen-ag.de;mid=2;ip=10.12.55.6;ua=ZimbraWebClient - FF3.0 (Linux);] soap - zextras 2011-09-07 20:36:18,538 INFO [btpool0-9://192.168.131.151:7071/service/admin/soap/zextras] [name=admin@zldap.verwaltung.regenbogen-ag.de;mid=2;ip=10.12.55.6;ua=ZimbraWebClient - FF3.0 (Linux);] extensions - ZeXtras API Manager: Exec: ZxCore/doReport 2011-09-07 20:36:18,984 INFO [btpool0-9://192.168.131.151:7071/service/admin/soap/zextras] [name=admin@zldap.verwaltung.regenbogen-ag.de;mid=2;ip=10.12.55.6;ua=ZimbraWebClient - FF3.0 (Linux);] soap - zextras 2011-09-07 20:36:18,984 INFO [btpool0-9://192.168.131.151:7071/service/admin/soap/zextras] [name=admin@zldap.verwaltung.regenbogen-ag.de;mid=2;ip=10.12.55.6;ua=ZimbraWebClient - FF3.0 (Linux);] extensions - ZeXtras API Manager: Exec: ZxCore/getAllNotifications 2011-09-07 20:36:18,984 INFO [btpool0-9://192.168.131.151:7071/service/admin/soap/zextras] [name=admin@zldap.verwaltung.regenbogen-ag.de;mid=2;ip=10.12.55.6;ua=ZimbraWebClient - FF3.0 (Linux);] extensions - ZeXtras API Manager: Proxying request ZxCore/getAllNotifications to: mbs1.verwaltung.regenbogen-ag.de 2011-09-07 20:36:18,985 INFO [ZxLink Handler] [] extensions - ZeXtras API Manager: Exec: ZxCore/getAllNotifications 2011-09-07 20:36:30,950 INFO [btpool0-9://mbs1.verwaltung.regenbogen-ag.de/service/extension/nginx-lookup] [] nginx - looking up domain by virtualhost name

That looks like that zmig can't connect to 2nd mbs. But the ZCS NE works.
09-07-2011, 10:40 PM
d0s0n

Hi chefkoch009,
thanks for the logs, maybe a I find your problem:

Code:

[...]ZeXtras API Manager: Proxying request ZxCore/getLicenseInfo to: mbs1.verwaltung.regenbogen-ag.de, mbs2.verwaltung.regenbogen-ag.de [...]ZeXtras API Manager: Exception: Unable to connect to server: mbs2.verwaltung.regenbogen-ag.de [...]Caused by: java.net.ConnectException: Connection refused

This seems to be a multi-store enviroment, with ZeXtras not fully installed on every mailboxd node (or unlikely a networking comunication problem on 8735/TCP between mailboxd servers).

Good night.

D0s-0n
09-08-2011, 08:12 AM
chefkoch009

hi d0s0n,

you are right, i have a multi store enviroment.
For now i also installed the yesterday downloaded package via "install all" on the 2nd store. for testing i disabled the firewalls between the mailbox stores and restartet them.
But i wasn't able to find the port 8735 open on mbs1,mbs2 (checked with nmap).
For now i get the following WebUI ErrorMsg:

JavaScript-Fehler in method ZaOverviewPanelController.prototype._overviewTreeL istener fileName: https://192.168.131.151:7071/service...v=110802115255 lineNumber: 21729

For the moment i check my logs. If i find any interesting, i'll append this to this thread.
09-08-2011, 10:40 AM
d0s0n

uhmmm, strange behaviour...
...however thanks for your collaboration.

Can you try these commands to check some installation details:

Code:

# netstat -nltp | grep 8735

The output should be like this:

Code:

tcp6 0 0 :::8735 :::* LISTEN 18398/java

As zimbra user, from host mbs1.verwaltung.regenbogen-ag.de:

Code:

zxmig --host mbs2.verwaltung.regenbogen-ag.de core doCheckUpdate

The output should be like this:

Code:

mbs2.verwaltung.regenbogen-ag.de: availableVersion none lastUpdate 2011-09-08 10:35:28 CEST currentVersion 1.0.0 updateError

For investigate the zimlet problem, you can try to access to the Administration console in debug mode, to have more detailed errore message with correct .js filename and line, adding "?dev=1" parameter to the access url, like this:
https://mbs1.verwaltung.regenbogen-a...raAdmin/?dev=1

Have a nice day.

D0s0n
09-08-2011, 11:41 AM
chefkoch009

everything you predicted is true....i got all the same response.

The WebUI Error MSG for now is:

JavaScript-Fehler in method ZaOverviewPanelController.prototype._overviewTreeL istener fileName: https://mbs1.verwaltung.regenbogen-a...v=110802115255 lineNumber: 79

Show 40 post(s) from this thread on one page