Results 1 to 2 of 2

Thread: Access other LDAP/Stores from admin console error

  1. #1
    Join Date
    Aug 2012
    Rep Power

    Default Access other LDAP/Stores from admin console error


    In a fresh installation over CentOS 6.5 64bits of Zimbra NE 8.0.7, I get this error when I try to access a server configuration from the admin console.
    In this last try, I have 1 LDAP Master/Store + 1 LDAP Replica/Store + 1 LDAP Replica/Store/MTA/Proxy

    Proxy is disabled and not configured for easing the diagnose. Secure interprocess communication is set to "no".

    Error detected (this part is translated from spanish) JavaScript in method ZaOverviewPanelController.prototype._overviewTreeL istener

    The log info I was able to find relevant to this is located in /opt/zimbra/log/mailbox.log and reads several entries like the following regaring to all kind of soap calls (in this case is flushcacheRequest but there are others like this for gethsmstatusrequest, etc).

    2014-04-26 20:03:24,341 WARN [qtp58648533-603:] [] soap -
    com.zimbra.common.service.ServiceException: system failure: Request not allowed on port 443
    at com.zimbra.common.service.ServiceException.FAILURE (
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.eclipse.jetty.servlet.ServletHolder.handle(Ser
    at org.eclipse.jetty.servlet.ServletHandler$CachedCha in.doFilter(
    at com.zimbra.cs.servlet.RequestStringFilter.doFilter (
    at org.eclipse.jetty.servlet.ServletHandler$CachedCha in.doFilter(
    at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set
    at org.eclipse.jetty.servlet.ServletHandler$CachedCha in.doFilter(
    at org.eclipse.jetty.servlets.UserAgentFilter.doFilte r(
    at org.eclipse.jetty.servlets.GzipFilter.doFilter(Gzi
    at org.eclipse.jetty.servlet.ServletHandler$CachedCha in.doFilter(
    at com.zimbra.cs.servlet.ETagHeaderFilter.doFilter(ET
    at org.eclipse.jetty.servlet.ServletHandler$CachedCha in.doFilter(
    at com.zimbra.cs.servlet.ZimbraQoSFilter.doFilter(Zim
    at org.eclipse.jetty.servlet.ServletHandler$CachedCha in.doFilter(
    at org.eclipse.jetty.servlets.DoSFilter.doFilterChain (
    at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSF
    at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSF
    at org.eclipse.jetty.servlet.ServletHandler$CachedCha in.doFilter(
    at org.eclipse.jetty.servlet.ServletHandler.doHandle(
    at org.eclipse.jetty.server.handler.ScopedHandler.han dle(
    at Handle(
    at Handle(
    There's more...

    My 443 port status as for netstat is this in all the servers:
    tcp 0 0* LISTEN 0 254881 4160/java

    I tried working this issue with three browsers (chrome, firefox and iexplore). With IE I've got some more info in the pop-up message.

    Se ha detectado un error de JavaScript in method ZaOverviewPanelController.prototype._overviewTreeL istener

    description: Unable to set property 'currentTab' of undefined or null reference number: -2146823281 stack: TypeError: Unable to set property 'currentTab' of undefined or null reference at setInstanceValue ( at setInstanceValue ( at xformTabTreeListener ( at _overviewTreeListener ( at run ( at handleEvent ( at notifyListeners ( at notifyListeners ( at _notifyListeners ( at _itemClicked (

    At this point...I have absolutly no clue where the problem is...I have this very same problem with "mmr" instead of "replica" and with proxy enabled for http and mail instead of the proxy being disabled like in this post.

    SELinux is disabled for all the hosts, iptables is disabled aswell and IPv6 is disabled from the very OS.

    I already updated the authkeys in case that was the problem and ran zmfixperms -e too...

    I also tried leveling up the log info but nothing new showed up.

    I'm puzzled by this. Anyone please? Reading other posts, some solutions pointed towards the url for the log host...I've got this setting ok.

    Please help me with this...any idea is going to be more than welcome.

    PS: If I add a server without LDAP/store roles, it doesn't throws this error.

  2. #2
    Join Date
    Aug 2012
    Rep Power


    Well, it's not solved but it's deffenetly something happens in CentOS 6.5 but NOT in RHEL 6.5.

    So....if you faced this problem because like me, you work in CentOS labs but your production is over RHEL, now at least you know that this particular error won't come up in RHEL.


Similar Threads

  1. Replies: 10
    Last Post: 01-07-2013, 12:23 AM
  2. Replies: 1
    Last Post: 11-27-2012, 07:22 AM
  3. Cannot access to the admin console
    By forstera in forum Administrators
    Replies: 8
    Last Post: 01-14-2010, 06:55 AM
  4. Can't access admin console
    By mmorse in forum Administrators
    Replies: 3
    Last Post: 06-28-2007, 10:42 AM
  5. Can't Access to Admin Console
    By GameSky in forum Installation
    Replies: 32
    Last Post: 05-26-2007, 12:25 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts