Results 1 to 5 of 5

Thread: No accounts found after upgrade from 7.2.2 to 8.0.2

Hybrid View

  1. #1
    Join Date
    Jun 2010
    Posts
    17
    Rep Power
    5

    Default No accounts found after upgrade from 7.2.2 to 8.0.2

    I did an upgrade of Zimbra 7.2.2 to Zimbra 8.0.2 on Ubuntu 10.04.3 LTS using the package zcs-8.0.2_GA_5569.UBUNTU10_64.20121210115101.

    There are several email accounts in the existing 7.2.2 version and they are fully functional. The upgrade run with no errors (with the exception that the script reported that the spam/ham accounts already exist, which is not really an error).

    But after the upgrade even the admin for the domain can not log in, the same applies to all other users, and the system reports that the account does not exist. Using "zmprov gaaa" does not display any admins after the upgrade (but did before). The same applies to "zmprov -l gaa", no user entries are returned.

    But using "ldapsearch -x -H $ldap_master_url -D $zimbra_ldap_userdn -w $zimbra_ldap_password" (following the description on Ajcody-LDAP-Topics - Zimbra :: Wiki) shows all user accounts.

    While experimenting in a test environment I created a new admin user on the console, which made things completely weird. Suddenly all users could log on again, but "zmprov -l gaa" still showed nothing. That is I ended up with a corrupted system, where users could log on, but the admin had no control over the accounts.

    I am clueless now where I should begin to search for the problem, why the upgrade obviously failed, but no errors were reported, and every service started successfully. And I have been able to reproduce the problem with our LDAP and mailbox data several times on freshly installed Ubuntu 10.04.3 LTS systems.

    Can anyone help and give advice what to do or where to look for additional information or error logs?

    Detlef Grittner

  2. #2
    Join Date
    Jun 2010
    Posts
    17
    Rep Power
    5

    Default

    Using the following command on a zimbra console

    Code:
    zmprov getAccount detlef.grittner
    gives the following error in mailbox.log:

    Code:
    com.zimbra.cs.account.AccountServiceException: no such account: detlef.grittner
    ExceptionId:qtp390087669-76:https://127.0.0.1:7071/service/admin/soap/GetAccountRequest:1362587540776:008e977093027c11
    Code:account.NO_SUCH_ACCOUNT
     at com.zimbra.cs.account.AccountServiceException.NO_SUCH_ACCOUNT(AccountServiceException.java:200)
        at com.zimbra.cs.service.admin.GetAccount.handle(GetAccount.java:66)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:500)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:363)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:236)
        at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:290)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:206)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:565)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1361)
        at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:57)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1332)
        at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:77)
        at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:218)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1332)
        at com.zimbra.cs.servlet.ZimbraQoSFilter.doFilter(ZimbraQoSFilter.java:105)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1332)
        at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:464)
        at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:327)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1332)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:477)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:965)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
        at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:312)
        at org.eclipse.jetty.server.handler.DebugHandler.handle(DebugHandler.java:77)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
        at org.eclipse.jetty.server.Server.handle(Server.java:349)
        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:452)
        at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:894)
        at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:948)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:857)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77)
        at org.eclipse.jetty.io.nio.SslConnection.handle(SslConnection.java:191)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:606)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:46)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538)
        at java.lang.Thread.run(Thread.java:722)
    Even though the account did exist before the upgrade and still lingers in the ldap.

    Does this help to find the problem?

  3. #3
    Join Date
    Sep 2009
    Posts
    18
    Rep Power
    6

    Default

    Hi,

    How about new accounts? is it working or listed using zmprov -l gaa ?
    Did you try creating new account from the console?

  4. #4
    Join Date
    Jun 2010
    Posts
    17
    Rep Power
    5

    Default

    Quote Originally Posted by bluezebra View Post
    Hi,

    How about new accounts? is it working or listed using zmprov -l gaa ?
    Did you try creating new account from the console?
    Yes, new accounts work. I give more details in the following:

    Let's start with account "test" that already existed before the upgrade:

    zmprov createAccount test@domain.xx blabla

    The astonishing result is:

    ERROR: account.ACCOUNT_EXISTS (email address already exists: test@domain.xx, at DN: uid=test,ou=people,dc=domain,dc=xx)


    This looks like as if the system knows that there is this account, but

    zmprov getAccount test@domain.xx

    results in

    ERROR: account.NO_SUCH_ACCOUNT (no such account: test@domain.xx)



    Now lets make a completely new account "test_1".

    zmprov createAccount test_1@domain.xx blabla
    75e16b5f-5a2c-49ca-8911-94896b23afab


    and the result is:

    zmprov getAccount test_1@domain.xx
    # name test_1@domain.xx
    cn: test_1
    mail: test_1@domain.xx
    objectClass: inetOrgPerson
    objectClass: zimbraAccount
    objectClass: amavisAccount
    < ... more entries ...>


    That works as intended and
    zmprov -l gaa

    shows a single entry

    test_1@domain.xx


    We are using an external LDAP for authentication and after creating user "test_1" there with a default password, the user "test_1" can log in with the zimbra webclient.

    One thing is creepy though: After creating a single new user, the other users can log in as well, but they are not displayed with "zmprov -l gaa". Using "zmprov getAccount" on previously existing accounts like "test" suddenly shows valid entries. In the admin web ui only the user "test_1" is displayed.
    One hint, if this is important: We have two domains for the mail system, one is servername.domain.xx and the other the official MX address domain.xx. And of course both are working in zimbra 7.

  5. #5
    Join Date
    Jun 2010
    Posts
    17
    Rep Power
    5

    Default Solved

    With version zcs-8.0.3_GA_5664.UBUNTU10_64.20130305090205 the update works.

Similar Threads

  1. 8.0.1 upgrade issue -- user accounts gone!
    By undersys in forum Administrators
    Replies: 7
    Last Post: 03-05-2013, 03:07 PM
  2. Cannot pop external accounts after 6.0.8 upgrade
    By strafford in forum Administrators
    Replies: 4
    Last Post: 11-11-2010, 11:45 AM
  3. Not found zmmsgtrace After upgrade to ZCS open-source 6.0.1
    By Fox_sibirsky in forum Administrators
    Replies: 3
    Last Post: 10-06-2009, 04:03 PM
  4. after upgrade zimbra 6.0.0 some zimlet not found.
    By adelmoral in forum Administrators
    Replies: 0
    Last Post: 09-11-2009, 07:45 AM
  5. Upgrade 4.5.6->4.5.10: accounts gone
    By bucketoftruth in forum Installation
    Replies: 2
    Last Post: 12-18-2007, 03:18 PM

Posting Permissions

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