Results 1 to 6 of 6

Thread: Upgrade 4.5.3 to 4.5.4

  1. #1
    risworo is offline New Member
    Join Date
    Mar 2007
    Posts
    4
    Rep Power
    8

    Default Upgrade 4.5.3 to 4.5.4

    I was trying to update my installation from 4.5.1_GA to 4.5.4_GA_763.FC5. I got to Starting LDAP ... , and it took a long time. After about 15 minutes, I checked /tmp/install.log.xxxx and foud no errors, but when I check /tmp/zmsetup.log.30832 I found this:

    Code:
    Checking 4.5.0_RC1
    Checking 4.5.0_RC2
    Checking 4.5.0_GA
    Checking 4.5.1_GA
    Updating from 4.5.1_GA
    Getting local config tomcat_java_options
    Modified tomcat_java_options=-client -XX:NewRatio=2 -Djava.awt.headless=true
    Setting local config tomcat_java_options to -client -XX:NewRatio=2 -Djava.awt.headless=true
    *** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e tomcat_java_options='-client -XX:NewRatio=2 -Djava.awt.headless=true'
    Checking 4.5.2_GA
    Updating from 4.5.2_GA
    Checking 4.5.3_GA
    Updating from 4.5.3_GA
    Global config attribute retrieved from ldap: zimbraMtaMaxMessageSize=10485760
    Global config attribute retrieved from ldap: zimbraMessageCacheSize=1671168
    *** Running as zimbra user: /opt/zimbra/bin/zmprov -l -- mcf zimbraMessageCacheSize 62813896
    Checking 4.5.4_GA
    Updating from 4.5.4_GA
    Setting local config ldap_log_level to 32768
    *** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e ldap_log_level='32768'
    Stopping ldap
    Upgrade complete
    Checking for port conflicts
    Starting ldap...
    *** Running as zimbra user: /opt/zimbra/openldap/sbin/slapindex -f /opt/zimbra/conf/slapd.conf
    bdb(): Lock table is out of available locks
    => bdb_idl_insert_key: c_put id failed: Cannot allocate memory (12)
    After that I hit CTRL-C and the installation went on. The rest of the zmsetup.log file did not look too worrying. However I also found this:

    Code:
    Session terminated, killing shell... ...killed. <--- I hit CTRL-C
    *** Running as zimbra user: /opt/zimbra/bin/ldap start
    Started slapd: pid 2137
    *** Running as zimbra user: /opt/zimbra/libexec/zmldapapplyldif
    slapd already running: pid 2137
    ldap_add: Already exists (68)
    ldap_add: Already exists (68)
    ldap_add: Already exists (68)
    ldap_add: Already exists (68)
    ldap_add: Already exists (68)
    ldap_add: Already exists (68)
    ldap_add: Already exists (68)
    After that, everything seems to run ok. However looking at /var/log/zimbra.log I found this:
    Code:
    <=bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
    The same goes for zimbraMailStatus. Does this indicate a future problem I should be aware of? If so, how would I correct it?

    I am running Zimbra on an FC6 i686 machine, with 8GB of memory.

    Sorry if this has been posted before. Forum search did not show related issues.
    Thank you for the great product.

    p.s. Then I found this [SOLVED] Messages after upgrade of 4.5.3 for 4.5.4. My stupid mistake. I apologize.
    Last edited by risworo; 04-09-2007 at 04:43 AM. Reason: Found the answer

  2. #2
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    Hi-
    I realize that you found your answer, but I needed to chime in about:
    bdb(): Lock table is out of available locks
    => bdb_idl_insert_key: c_put id failed: Cannot allocate memory (12)
    That actually worries me. What's to stop it from happening again? Just because things look like they're working, doesn't mean that they actually are.

    So, do you have a backup/recovery strategy? Make sure you do.

    john

  3. #3
    tbullock is offline Advanced Member
    Join Date
    Oct 2005
    Location
    Calgary, AB
    Posts
    232
    Rep Power
    9

    Default

    Quote Originally Posted by risworo View Post

    I am running Zimbra on an FC6 i686 machine, with 8GB of memory.
    Is all working OK? I noticed that you installed the ZCS FC5 binary on a FC6 machine. That might be causing you some problems too.
    Cheers,

    Travis

    "Let's look at this from a standpoint of "Status". What exactly, on the Space Craft, IS working?"
    -Flight Control, Apollo 13

  4. #4
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    GREAT catch!!

  5. #5
    risworo is offline New Member
    Join Date
    Mar 2007
    Posts
    4
    Rep Power
    8

    Default

    Quote Originally Posted by jholder View Post
    GREAT catch!!
    So is the FC5 binary on FC6 the problem then? Before 4.5.4 I was running 4.5.1 (sorry for the mistake on the original title, should be 4.5.1 and not 4.5.3) on the same machine. I followed the instructions outlined here http://wiki.zimbra.com/index.php?tit...ora_Core_6_x86. Actually on my installation the symbolic link was already there. So did not do anything, and 4.5.1 was installed without a hitch.

    Only the upgrade to 4.5.4 gave me this error:
    Code:
    *** Running as zimbra user: /opt/zimbra/openldap/sbin/slapindex -f /opt/zimbra/conf/slapd.conf
    bdb(): Lock table is out of available locks
    => bdb_idl_insert_key: c_put id failed: Cannot allocate memory (12)
    For the backup I just tar -cpf the whole /opt/zimbra directory on a spare NFS partition on another server, making sure that the permissions are kept intact.

    Are there any log entries that I should watch for? Besides the following
    Code:
    <=bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
    I did not catch anything else in /var/log/zimbra.log.

    Thanks.

  6. #6
    risworo is offline New Member
    Join Date
    Mar 2007
    Posts
    4
    Rep Power
    8

    Default

    So is there any log entries that I should watch for? When I installed 4.5.1 (the title on the original message was wrong) the first time, I followed the instruction for FC6 platform specific notes. Actually the symbolic link suggested on that wiki entry was already there, so I did not do anything. The installation of 4.5.1 went without a hitch.

    The problem came up when I upgraded to 4.5.4 (see the quoted zmsetup.log above). Right now, the server is running, and I am testing it by transferring about 50+GB of Lotus Domino Mail. So far, no real problem. The server can be accessed through the web interface, pop3 and IMAP. So far one of my testers (100+ persons) complained.

    The backup strategy is fairly simple, it involves shutting down the Zimbra processes (zmcontrol), mounting a shared NFS volumes from another server, tar -cpf to the mounted volume, disconnect the NFS, and restart the Zimbra.

    Thanks.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [SOLVED] Messages after upgrade of 4.5.3 for 4.5.4.
    By aabreu2005 in forum Administrators
    Replies: 8
    Last Post: 09-10-2007, 02:42 PM
  2. Replies: 6
    Last Post: 07-04-2007, 08:36 AM
  3. Upgrade (4.5.4 to 4.5.5)
    By SpEnTBoY in forum Zimbra Success Stories
    Replies: 0
    Last Post: 05-14-2007, 06:43 AM
  4. Upgrade 4.5.4 to 4.5.5 questions
    By dlochart in forum Zimbra Connector for Outlook
    Replies: 11
    Last Post: 05-14-2007, 02:44 AM
  5. upgrade 3.1.4 to 4.5.3
    By ronsterchan in forum Administrators
    Replies: 4
    Last Post: 03-16-2007, 01:24 AM

Posting Permissions

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