Results 1 to 2 of 2

Thread: Upgrading Zimbra on Multi-Server Installs

  1. #1
    glitch23 is offline Special Member
    Join Date
    Jul 2006
    Location
    New York, NY
    Posts
    122
    Rep Power
    8

    Default Upgrading Zimbra on Multi-Server Installs

    I'm not sure if this belongs in Administrators or Installation, but every time I need to upgrade Zimbra on my multi-server installs it always seems to be a pain. On the servers with the mailbox installed everything is usually pretty smooth, actually extremely smooth and its down for no longer than 30 minutes.

    However on the MTA boxes, the install scripts always hangs at trying to start mysql, which isn't installed since the only packages/services enabled are zimbra-core, zimbra-mta, zimbra-snmp. Everytime I upgrade a MTA only box I have to backup /opt/zimbra/ then uninstall it, remover /opt/zimbra/, remove any zimbra files in /tmp and then install the new version. This way it gives me the "menu" of what to enable/disable and set the ldap master host and password.

    Am I doing something wrong, or will there be a fix for this anytime soon?
    Because we all can't be geniuses, I'll go first.

  2. #2
    glitch23 is offline Special Member
    Join Date
    Jul 2006
    Location
    New York, NY
    Posts
    122
    Rep Power
    8

    Angry I think I found it

    I think I found the problem but I do not know the solution.

    When upgrading to a newer version of ZCS on a server that doesn't has all the services running you will run into a problem when the install script goes to re-enable/configure the "old" settings that you had for your previous install.

    I seems the problem stems from zmlocalconfig grabbing all the settings and saving them to /opt/zimbra/.saveconfig/config.save. The problem is this:

    Code:
    mysql_bind_address = localhost
    mysql_data_directory = ${zimbra_db_directory}/data
    mysql_directory = ${zimbra_home}/mysql
    mysql_innodb_log_buffer_size = 8388608
    mysql_innodb_log_file_size = 104857600
    mysql_memory_percent = 30
    mysql_mycnf = ${zimbra_home}/conf/my.cnf
    mysql_pidfile = ${zimbra_db_directory}/mysql.pid
    mysql_port = 7306
    mysql_read_buffer_size = 1048576
    mysql_root_password = *
    mysql_socket = ${zimbra_db_directory}/mysql.sock
    mysql_sort_buffer_size = 1048576
    mysql_table_cache = 500
    None of this exists on this system akak "localhost" and "${zimbra_home}" refers to /opt/zimbra so none of those directories exist either.

    Anyone who has completed an upgrade on a Zimbra MTA please respond with how you did it.
    Because we all can't be geniuses, I'll go first.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Error loading on Mac OS X 10.4.10 server PPC
    By qprcanada in forum Installation
    Replies: 7
    Last Post: 10-26-2007, 06:25 AM
  2. dspam logrotate errors
    By michaeln in forum Users
    Replies: 7
    Last Post: 02-19-2007, 12:45 PM
  3. 3.1 on FC4 problems
    By cohnhead in forum Installation
    Replies: 8
    Last Post: 05-26-2006, 11:16 AM
  4. port 7071 not listening OS X install
    By leeimber in forum Installation
    Replies: 7
    Last Post: 03-21-2006, 10:47 AM
  5. Seeming variety of problems on suse-9.1
    By Crexis in forum Installation
    Replies: 52
    Last Post: 03-04-2006, 12:19 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
  •