Web interface (only) failure after upgrade to 8.7.11

Ask questions about your setup or get help installing ZCS server (ZD section below).
Post Reply
dgeist
Posts: 24
Joined: Fri Sep 12, 2014 10:47 pm

Web interface (only) failure after upgrade to 8.7.11

Post by dgeist »

After working through various other challenges with having a virtual-host dual stack single host system, I'm stuck getting the web interface back up and running. All other functions appear to be working (SMTP, anti-spam, IMAP, POP, SOAP requests from and external z-push system, etc.). Every time I try to connect to the web interface, I get a "network error" and the mailbox log shows this:

Code: Select all

2017-10-18 11:14:56,792 INFO  [qtp1068934215-786] [] nginxlookup - missing header field Auth-User
2017-10-18 11:14:56,932 WARN  [qtp1068934215-783] [name=dan@<domain>.net;oip=2607:<IP>:201:3000:0:0:0:4e9d;ua=zclient/8.7.11_GA_1854;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: unable to modify attrs: LDAP error:  - unable to modify attributes: ldap host=2607:<IP>:201:3000:0:0:0:4e9d:636: Too many referrals were encountered while attempting to process the operation.
ExceptionId:qtp1068934215-783:1508339696931:858506b605dac54a
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:286)
        at com.zimbra.cs.account.ldap.LdapProvisioning.modifyLdapAttrs(LdapProvisioning.java:648)
        at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrsInternal(LdapProvisioning.java:555)
        at com.zimbra.cs.account.ldap.LdapProvisioning.modifyEphemeralAttrsInLdap(LdapProvisioning.java:448)
        at com.zimbra.cs.ephemeral.LdapEphemeralStore$ZimbraLdapHelper.executeChange(LdapEphemeralStore.java:181)
        at com.zimbra.cs.ephemeral.LdapEphemeralStore.deleteInternal(LdapEphemeralStore.java:96)
        at com.zimbra.cs.ephemeral.LdapEphemeralStore.purgeExpired(LdapEphemeralStore.java:80)
        at com.zimbra.cs.account.Entry.purgeEphemeralAttr(Entry.java:955)
        at com.zimbra.cs.account.ZAttrAccount.purgeCsrfTokenData(ZAttrAccount.java:7684)
        at com.zimbra.cs.servlet.util.CsrfUtil.getTokenDataFromLdap(CsrfUtil.java:360)
        at com.zimbra.cs.servlet.util.CsrfUtil.getExistingCsrfTokenForThisAuthToken(CsrfUtil.java:426)
        at com.zimbra.cs.servlet.util.CsrfUtil.generateCsrfToken(CsrfUtil.java:396)
        at com.zimbra.cs.service.account.Auth.doResponse(Auth.java:461)
        at com.zimbra.cs.service.account.Auth.handle(Auth.java:355)
I had to play with my ldap_master_url and ldap_url to get things working, as well as modifying the proxy templates for nginx to get the dual-stack part working.

Any ideas what's going on here?

Thanks.
Dan
Post Reply