Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Error Upgrading from M1

  1. #11
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default ldap not starting

    If ldap doesn't start (on the ldap master) set this config key:
    zmlocalconfig -e ldap_is_master=true

  2. #12
    Join Date
    Nov 2005
    Posts
    9
    Rep Power
    9

    Default Now it works but the messages gone :(

    Checking the error log in zimbra.log I check then the db directory
    and found several sql files with sql scripts.
    One of those just update a "version" number to e "21" ( all magic for me )
    We just apply the sql scipts to the mysql database and now it works.

    The only problem is that the mail index gone away and I see nothing on my mail folder.

    Now, my question is:
    How can I make Zimbra to re-index my mailbox ?
    I found my messages ( raw mail files ) but I cannot see them on the server.

    About the LDAP I run it manually, it is the only way it will work.

    Thanks

  3. #13
    Join Date
    Nov 2005
    Posts
    9
    Rep Power
    9

    Default A new error, now on mysql create tables

    while running the sql scripts we found the following error:
    ERROR 1005 (HY000) at line 58: Can't create table './zimbra/volume.frm' (errno: 121)

    How to proceed ?
    It is something related to InnoDB foreing keys

    Thanks

  4. #14
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Quote Originally Posted by incarose
    while running the sql scripts we found the following error:
    ERROR 1005 (HY000) at line 58: Can't create table './zimbra/volume.frm' (errno: 121)

    How to proceed ?
    It is something related to InnoDB foreing keys

    Thanks
    We don't recomend you try to just hack on the DB. Bad things can happen.

  5. #15
    Join Date
    Nov 2005
    Posts
    3
    Rep Power
    9

    Default Clean Install from M1

    Are there instructions for maintaining data from an M1 system when installing a clean M2 system? In other words, how can I "upgrade" while doing a clean install?

  6. #16
    Join Date
    Oct 2005
    Posts
    34
    Rep Power
    10

    Default Invalid_pdu

    I've just done an upgrade from M1 to M2 and experiencing some of the same problems mentioned in this thread. After a reboot the server wouldn't start, setting ldap to be a master fixed this. I can not see the admin page I just get a blank page. Logging in to zimbra results in INVALID_PDU.

    These lines appear in zimbra.log:

    Code:
    2005-11-16 13:57:08,500 INFO  [http-7071-Processor48] [] StandardWrapper[/service:AdminServlet] - Servlet AdminServlet is currently unavailable
    2005-11-16 13:57:10,800 INFO  [http-7071-Processor50] [] StandardWrapper[/service:AdminServlet] - Servlet AdminServlet is currently unavailable
    2005-11-16 13:57:39,135 INFO  [http-80-Processor98] [] StandardWrapper[/service:SoapServlet] - Servlet SoapServlet is currently unavailable
    2005-11-16 13:57:44,376 INFO  [http-80-Processor98] [] StandardWrapper[/service:SoapServlet] - Servlet SoapServlet is currently unavailable
    2
    I've gone to the login page with debug enabled. Here's the debug:

    HTML Code:
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    <soap:Header>
    <context xmlns="urn:zimbra">
    <nosession/>
    <format type="js"/>
    </context>
    </soap:Header>
    <soap:Body>
    <AuthRequest xmlns="urn:zimbraAccount">
    <account by="name">
    myaccount
    </account>
    <password>
    mypassword
    </password>
    </AuthRequest>
    </soap:Body>
    </soap:Envelope>
    HTML Code:
    <parsererror xmlns="http://www.mozilla.org/newlayout/xml/parsererror.xml">XML Parsing Error: mismatched tag. Expected: </HR>.
    Location: http://zimbra.redfish.local/?debug=1
    Line Number 1, Column 1047:<sourcetext><html><head><title>Apache Tomcat/5.5.7 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 404 - Servlet SoapServlet is not available</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Servlet SoapServlet is not available</u></p><p><b>description</b> <u>The requested resource (Servlet SoapServlet is not available) is not available.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/5.5.7</h3></body></html>
    Code:
    code: "INVALID_PDU",
    detail: [undefined],
    method: "AjxSoapDoc.createFromXml:2",
    msg: "Invalid SOAP PDU"
    If there's any other info you need let me know.

    If a clean install is the only way to get things going, is there a way to bring across the mail from the old install?

    Justin.

  7. #17
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

Posting Permissions

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