Unable to log into Zimbra Admin

[craftedpacket]

I have had zimbra installed for about 3 days now. I have started moving some mail accounts over to it but I am now unable to login to the admin page. I have tried firefox and IE and get the same message. The login stops at "loading...." and then in the bottom left of browser you can see an error. Opening the error shows this:

'this._msgDialog' is null or not an object
Admin_all.js.zgz
code:0
line:2722 Char:1
URI:https://theaddress:7071/zimbraAdmin/...v=101115230502

This is the second time it has happend today. When it first happend I did a zmcontrol restart and it seemed to have resolved the issue but it is doing it again.

Any ideas?

[phoenix]

Have you modified any of the Zimbra files on this server? What is 'theaddress' in your url above, is it an IP address or a valid FQDN of your server?

[craftedpacket]

I have made the following changes to stop CPU spikes as the zimbra is installed on vmware.

zmlocalconfig -e zmmtaconfig_interval=6000
zmprov mcf zimbraLogRawLifetime 7d
zmprov mcf zimbraLogSummaryLifetime 30d
/opt/zimbra/libexec/zmlogprocess

su - zimbra
crontab -e
*/60 * * * * /opt/zimbra/libexec/zmstatuslog


I have tried to log in as https://domainname and https://IPaddress both internet routeable and local on the box.


This is release
6.0.9_GA_2686.UBUNTU10_64 Network Edition

[kfairich]

Originally Posted by craftedpacket

I have made the following changes to stop CPU spikes as the zimbra is installed on vmware.

zmlocalconfig -e zmmtaconfig_interval=6000
zmprov mcf zimbraLogRawLifetime 7d
zmprov mcf zimbraLogSummaryLifetime 30d
/opt/zimbra/libexec/zmlogprocess

su - zimbra
crontab -e
*/60 * * * * /opt/zimbra/libexec/zmstatuslog


I have tried to log in as https://domainname and https://IPaddress both internet routeable and local on the box.


This is release
6.0.9_GA_2686.UBUNTU10_64 Network Edition

Hi, all good!

I'm having the same problem. Managed to solve? Can you give me the procedure?

Message: 'this._msgDialog' is null or not an object
Line: 2722
Char: 1
Code: 0
URI: https: / / xxx.xxx.xxx.xxx: 7071/zimbraAdmin/js/Admin_all.js.zgz? v = 100820045352

Thanks!

[klodoma]

I confirm the error in IE and in Firefox

'this._msgDialog' is null or not an object

I could catch the following request:

https://srvtest.interpid.eu:7071/ser...ap/AuthRequest

The Post:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><userAgent xmlns="" name="ZimbraWebClient - FF3.0 (Win)"/><session xmlns=""/><format xmlns="" type="js"/></context></soap:Header><soap:Body><AuthRequest xmlns="urn:zimbraAdmin"><name xmlns="">admin@interpid.eu</name><password xmlns="">sorrow</password><virtualHost xmlns="">srvtest.interpid.eu</virtualHost></AuthRequest></soap:Body></soap:Envelope>

The Response:

{"Header":{"context":{"_jsns":"urn:zimbra"}},"Body":{"Fault":{"Code":{"Value":"soap:Receiver"},"Reason":{"Text":"system failure: ZimbraLdapContext"},"Detail":{"Error":{"Code":"service.FAILURE","Trace":"com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext\nExceptionId:btpool0-14://srvtest.interpid.eu:7071/service/admin/soap/AuthRequest:1296425694469:069505b89520a5a6\nCode:service.FAILURE\n\tat com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)\n\tat com.zimbra.cs.account.ldap.ZimbraLdapContext.\u003Cinit\u003E(ZimbraLdapContext.java:416)\n\tat com.zimbra.cs.account.ldap.ZimbraLdapContext.\u003Cinit\u003E(ZimbraLdapContext.java:373)\n\tat com.zimbra.cs.account.ldap.LdapProvisioning.getAccountByQuery(LdapProvisioning.java:608)\n\tat com.zimbra.cs.account.ldap.LdapProvisioning.getAccountByNameInternal(LdapProvisioning.java:776)\n\tat com.zimbra.cs.account.ldap.LdapProvisioning.getAccountByName(LdapProvisioning.java:757)\n\tat com.zimbra.cs.account.ldap.LdapProvisioning.get(LdapProvisioning.java:668)\n\tat com.zimbra.cs.account.ldap.LdapProvisioning.get(LdapProvisioning.java:653)\n\tat com.zimbra.cs.service.admin.Auth.handle(Auth.java:131)\n\tat com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420)\n\tat com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274)\n\tat com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)\n\tat com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)\n\tat com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:727)\n\tat com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:820)\n\tat org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)\n\tat org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)\n\tat com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)\n\tat org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)\n\tat org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)\n\tat org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)\n\tat org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)\n\tat org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)\n\tat org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)\n\tat org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)\n\tat org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)\n\tat org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)\n\tat org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)\n\tat org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)\n\tat org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)\n\tat org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)\n\tat org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)\n\tat org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)\n\tat org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)\n\tat org.mortbay.jetty.Server.handle(Server.java:326)\n\tat org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543)\n\tat org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939)\n\tat org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)\n\tat org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)\n\tat org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)\n\tat org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:413)\n\tat org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)\nCaused by: javax.naming.CommunicationException: Bad file descriptor [Root exception is java.net.SocketException: Bad file descriptor]\n\tat com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3213)\n\tat javax.naming.ldap.InitialLdapContext.extendedOperation(InitialLdapContext.java:164)\n\tat com.zimbra.cs.account.ldap.ZimbraLdapContext.\u003Cinit\u003E(ZimbraLdapContext.java:406)\n\t... 42 more\nCaused by: java.net.SocketException: Bad file descriptor\n\tat java.net.SocketOutputStream.socketWrite0(Native Method)\n\tat java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)\n\tat java.net.SocketOutputStream.write(SocketOutputStream.java:136)\n\tat java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)\n\tat java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)\n\tat com.sun.jndi.ldap.Connection.writeRequest(Connection.java:396)\n\tat com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient.java:1172)\n\tat com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3160)\n\t... 44 more\n","_jsns":"urn:zimbra"}}}},"_jsns":"urn:zimbraSoap"}

It seem that a java error occured.

Any tips how to fix this?

Zimbra 6 running on Ubuntu 10.04

Regards, Andrei.