Results 1 to 4 of 4

Thread: Upgrade from 7.2.2 to 8.0.2 failed

  1. #1
    Join Date
    Jun 2007
    Location
    Porto Alegre, RS, Brazil
    Posts
    96
    Rep Power
    8

    Default Upgrade from 7.2.2 to 8.0.2 failed

    Hi there

    I just rolled back from a failed attempt to upgrade a Zimbra FOSS from 7.2.2 to 8.0.2, 64 bit RHEL6. My production server was left untouched so it was easy to switch back.

    The complete process was this:

    1. Cold rsync from production server to new server (7.2.2)
    2. install.sh (upgrade 7.2.2 to 7.2.2 just to clear things up)
    3. Services started. System is sending and receiving email normally. Weīre still in version 7.2.2
    4. Services stopped
    5. install.sh to upgrade to 8.0.2

    No erros on screen, only failed to create spam, ham and quarantine accounts and also failed to set MTA auth host.

    Installation finished, no apparent error. Services started ok.

    Web interface access was ok, but i couldnīt logon. Warning flag raised

    I thought it could be related to communication loss with our AD. I tried to change the local admin password with zmprov but received an authentication error for user [zimbra].

    At this point, i didnīt want to have more downtime than my window allowed, so i switched back to my old production server running 7.2.2.

    These are the errors iīve found in zmsetup.log

    Error 1)
    Thu Jan 3 09:54:04 2013 Loading database...
    Thu Jan 3 09:54:04 2013 *** Running as zimbra user: /opt/zimbra/libexec/zmslapadd /opt/zimbra/data/ldap/ldap.80
    50e5715d ldif_read_file: checksum error on "/opt/zimbra/data/ldap/config/cn=config/olcDatabase={2}mdb.ldif"

    Error 2)
    Exception in thread "main" com.zimbra.common.service.ServiceException: system failure: no mailbox server for assigning home server for distribution lists
    ExceptionId:main:1357215568771:089f6909ad605e5c
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:258)
    at com.zimbra.cs.account.ldap.upgrade.BUG_68831$Bug68 831Visitor.<init>(BUG_68831.java:116)
    at com.zimbra.cs.account.ldap.upgrade.BUG_68831.upgra de(BUG_68831.java:81)
    at com.zimbra.cs.account.ldap.upgrade.BUG_68831.upgra deDLs(BUG_68831.java:75)
    at com.zimbra.cs.account.ldap.upgrade.BUG_68831.doUpg rade(BUG_68831.java:45)
    at com.zimbra.cs.account.ldap.upgrade.LdapUpgrade.upg rade(LdapUpgrade.java:163)
    at com.zimbra.cs.account.ldap.upgrade.LdapUpgrade.mai n(LdapUpgrade.java:178)

    Error 3) Here it appears something already went very bad as zimbra cannot find a domain that previously existed. I must add that during another config steps it correctly set the server hostname.
    Thu Jan 3 10:23:08 2013 ERROR: account.NO_SUCH_DOMAIN (no such domain: xxxx.com.br)

    Error 4)
    Thu Jan 3 10:24:49 2013 Adding server.xxxx.com.br to zimbraMailHostPool in default COS...
    Thu Jan 3 10:24:49 2013 Returning cached server config attribute for server.xxxx.com.br: zimbraId=0fc92db7-451f-4c72-b6b7-a529395a2d2b
    Thu Jan 3 10:24:49 2013 Returning cached cos config attribute for default: zimbraMailHostPool=0fc92db7-451f-4c72-b6b7-a529395a2d2b
    Thu Jan 3 10:24:49 2013 Updating cached config attribute for COS default: zimbraMailHostPool=0fc92db7-451f-4c72-b6b7-a529395a2d2b
    Thu Jan 3 10:24:49 2013 *** Running as zimbra user: /opt/zimbra/bin/zmprov -r -m -l mc default zimbraMailHostPool '0fc92db7-451f-4c72-b6b7-a529395a2d2b'
    ERROR: service.INVALID_REQUEST (invalid request: specified zimbraMailHostPool does not correspond to a valid server: 0fc92db7-451f-4c72-b6b7-a529395a2d2b)
    Thu Jan 3 10:24:52 2013 failed.

    Error 5)
    Thu Jan 3 10:25:18 2013 *** Running as zimbra user: /opt/zimbra/bin/zmprov -r -m -l ms server.xxxx.com.br zimbraMtaAuthHost 'server.xxxx.com.br'
    ERROR: service.INVALID_REQUEST (invalid request: specified zimbraMtaAuthHost does not correspond to a valid service hostname: server.xxxx.com.br)
    Thu Jan 3 10:25:22 2013 failed.

    Error 6)
    Thu Jan 3 10:25:44 2013 Creating user spam@xxxx.com.br...
    Thu Jan 3 10:25:47 2013 ERROR: account.NO_SUCH_ACCOUNT (no such account: spam@xxxx.com.br)
    Thu Jan 3 10:25:48 2013 *** Running as zimbra user: /opt/zimbra/bin/zmprov
    ERROR: account.NO_SUCH_DOMAIN (no such domain: xxxx.com.br)
    Thu Jan 3 10:25:52 2013 failed.
    Thu Jan 3 10:25:52 2013 Creating user ham@xxxx.com.br...
    Thu Jan 3 10:25:55 2013 ERROR: account.NO_SUCH_ACCOUNT (no such account: ham@xxxx.com.br)
    Thu Jan 3 10:25:56 2013 *** Running as zimbra user: /opt/zimbra/bin/zmprov
    ERROR: account.NO_SUCH_DOMAIN (no such domain: xxxx.com.br)
    Thu Jan 3 10:25:59 2013 failed.
    Thu Jan 3 10:25:59 2013 Creating user virus-quarantine.gk7kzkx6@xxxx.com.br...
    Thu Jan 3 10:26:03 2013 ERROR: account.NO_SUCH_ACCOUNT (no such account: virus-quarantine.gk7kzkx6@xxxx.com.br)
    Thu Jan 3 10:26:03 2013 *** Running as zimbra user: /opt/zimbra/bin/zmprov
    ERROR: account.NO_SUCH_DOMAIN (no such domain: xxxx.com.br)
    Thu Jan 3 10:26:06 2013 failed.


    Error 7) After install script started Zimbra services
    Thu Jan 3 10:27:49 2013 *** Running as zimbra user: /opt/zimbra/bin/zmzimletctl -l undeploy com_zimbra_linkedin
    com.zimbra.common.soap.SoapFaultException: authentication failed for [zimbra]
    ExceptionId:qtp18075390-82:https://127.0.0.1:7071/service/admin...8cf24d5aff913d
    Code:account.AUTH_FAILED
    at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:88)
    at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:333)
    at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:308)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:255)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:167)
    at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:386)
    at com.zimbra.common.soap.SoapTransport.invokeWithout Session(SoapTransport.java:372)
    at com.zimbra.cs.account.soap.SoapProvisioning.invoke Request(SoapProvisioning.java:442)
    at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:450)
    at com.zimbra.cs.account.soap.SoapProvisioning.soapAd minAuthenticate(SoapProvisioning.java:394)
    at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.ini tZimletSoapUtil(ZimletUtil.java:1387)
    at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.<in it>(ZimletUtil.java:1361)
    at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUti l.java:1815)
    at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.ja va:1907)

    I dumped the ldap database to an ldif using zmslapcat and all the users are listed.

    But, when trying "zmprov -l ga user@xxxx.com.br" i get "ERROR: account.NO_SUCH_ACCOUNT (no such account: user@xxxx.com.br)"

    What happened to the once easy and trouble-free Zimbra upgrade process? Iīd like to add that this 7.2.2 was upgraded last week from 6.0.6 without a single issue.

    Now iīm seeing many people posting problems with Zimbra 8. Iīm certainly postponing this upgrade. While i have had success with fresh install of zimbra 8, upgrading is causing too many problems at the moment.
    Last edited by fviero; 01-03-2013 at 07:43 AM.

  2. #2
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,285
    Rep Power
    10

    Default

    "error 1" is not an error. It is a warning. Your slapadd succeeded w/o issue.
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  3. #3
    Join Date
    Jun 2007
    Location
    Porto Alegre, RS, Brazil
    Posts
    96
    Rep Power
    8

    Default

    Quote Originally Posted by quanah View Post
    "error 1" is not an error. It is a warning. Your slapadd succeeded w/o issue.
    Good to know. Thanks.

    And what about the others in the list?

    First symptom after installation was that i couldnīt logon neither to ZWC nor to Admin Console. Trying to use zmprov produces the errors seen on my first post. Again, if you read the steps i took you can see that i had a fully functional 7.2.2 prior to upgrade to 8.0.2 (besides my fallback machine, the untouched one)...

    EDIT: well, error 1 says "checksum error"...not an error? really?

  4. #4
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,285
    Rep Power
    10

    Default

    Really, it is not an error. The text is misleading. If slapadd had actually failed, that would have been logged.

    The rest of the issues, I can't comment on, other than to say something clearly is wrong with the upgrade. I'd have to look at the actual server to know more.
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

Similar Threads

  1. Upgrade to Zimbra 8 failed - script failed with code 256
    By dm4creavil in forum Administrators
    Replies: 0
    Last Post: 10-02-2012, 07:53 AM
  2. Upgrade issues ... upgrade failed without indication
    By Filly in forum Administrators
    Replies: 1
    Last Post: 09-17-2010, 05:14 PM
  3. Replies: 1
    Last Post: 09-17-2010, 05:14 PM
  4. Replies: 7
    Last Post: 02-15-2010, 08:55 PM
  5. failed upgrade, failed restore, big trouble
    By feralcoder in forum Installation
    Replies: 2
    Last Post: 03-19-2007, 06:38 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
  •