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

Thread: Upgrade Zimbra OSE 7.2.1 to 8.0.0 MySQL Failed

  1. #11
    vadonka is offline Active Member
    Join Date
    Nov 2011
    Location
    Hungary
    Posts
    30
    Rep Power
    3

    Default

    can you see something like that in the my.cnf?

    Code:
    [mysqld]
    
    basedir        = /opt/zimbra/mysql
    datadir        = /opt/zimbra/db/data
    socket         = /opt/zimbra/db/mysql.sock
    pid-file       = /opt/zimbra/db/mysql.pid
    bind-address   = localhost
    port           = 7306
    user           = zimbra
    tmpdir         = /opt/zimbra/data/tmp
    here is my full my.cnf file:

    Code:
    [mysqld]
    
    basedir        = /opt/zimbra/mysql
    datadir        = /opt/zimbra/db/data
    socket         = /opt/zimbra/db/mysql.sock
    pid-file       = /opt/zimbra/db/mysql.pid
    bind-address   = localhost
    port           = 7306
    user           = zimbra
    tmpdir         = /opt/zimbra/data/tmp
    
    external-locking
    slow_query_log = 1
    slow_query_log_file = /opt/zimbra/log/myslow.log
    
    
    long-query-time  = 1
    log-queries-not-using-indexes
    
    thread_cache_size = 110
    max_connections   = 110
    
    # We do a lot of writes, query cache turns out to be not useful.
    query_cache_type = 0
    
    sort_buffer_size = 1048576
    read_buffer_size = 1048576
    
    # (Num mailbox groups * Num tables in each group) + padding
    table_cache = 1200
    
    innodb_buffer_pool_size        = 3435973840
    innodb_log_file_size           = 524288000
    innodb_log_buffer_size         = 8388608
    innodb_file_per_table
    
    # Value is: 200 + max_connections + 2 * table_cache
    innodb_open_files              = 2710
    
    innodb_max_dirty_pages_pct     = 10
    innodb_flush_method            = O_DIRECT
    innodb_flush_log_at_trx_commit = 0
    max_allowed_packet             = 16777216
    
    [mysqld_safe]
    
    err-log      = /opt/zimbra/log/mysqld.log
    pid-file     = /opt/zimbra/db/mysql.pid

  2. #12
    alisou is offline Intermediate Member
    Join Date
    Oct 2012
    Posts
    16
    Rep Power
    2

    Default

    Hi,
    The problem is resolved with Zimbra OSE 8.0.1. With this version i don't have errors and the upgrade work fine.

  3. #13
    andrewperry is offline Starter Member
    Join Date
    Dec 2011
    Posts
    1
    Rep Power
    3

    Default

    People who run into this issue are likely to have installed a local mysql client or server separate from the Zimbra packages.

    After deinstalling any such mysql packages and removing /etc/mysql so it didn't interfere with Zimbra's own mysql config, at the instruction of Zimbra tech support, the upgrade to 8.0.3 worked smoothly.

    Good to check this out before trying the upgrade, but unfortunately it is likely to be the other way around when the issue is discovered.

    Having an /etc/mysql directory is a definite warning sign!

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

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

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, 06:53 AM
  2. zimbra 6.0.2 to 6.0.3 crash on mysql Upgrade
    By hrch in forum Administrators
    Replies: 1
    Last Post: 12-09-2009, 12:33 AM
  3. DBD::mysql::st execute failed
    By padraig in forum Administrators
    Replies: 3
    Last Post: 07-18-2007, 03:46 AM
  4. 3.0 to 4.5.3 Upgrade failed (mysql error)
    By dealt in forum Installation
    Replies: 35
    Last Post: 03-19-2007, 10:30 PM
  5. failed upgrade, failed restore, big trouble
    By feralcoder in forum Installation
    Replies: 2
    Last Post: 03-19-2007, 05:38 PM

Tags for this Thread

Posting Permissions

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