Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Upgrade Zimbra OSE 7.2.1 to 8.0.0 MySQL Failed

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

    Default Upgrade Zimbra OSE 7.2.1 to 8.0.0 MySQL Failed

    Hi,

    I want to upgrade my Zimbra 7.2.1 OSE in Ubuntu 10.04 LTS 64Bits to Zimbra OSE 8.0.0. But i have problem in MySQL.

    The upgrade was blocked in "Starting mysql".

    Code:
    Do you want to verify message store database integrity? [Y] 
    Verifying integrity of message store databases.  This may take a while.
    Starting mysqld.../opt/zimbra/mysql/bin/mysqladmin: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
    Fatal error in defaults handling. Program aborted
    /opt/zimbra/mysql/bin/mysqladmin: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
    Fatal error in defaults handling. Program aborted
    done.
    mysqld is alive
    Database errors found.
    /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --auto-repair --password=XXXXXXXX
    mysql.general_log
     Error    : You can't use locks with log tables.
     mysql.slow_log
     Error    : You can't use locks with log tables.
    mysqld is alive
    Stopping mysqld... done.
    
    ...
    
    Restoring existing configuration file from /opt/zimbra/.saveconfig/localconfig.xml...done
    Operations logged to /tmp/zmsetup.10072012-173944.log
    Upgrading from 7.2.1_GA_2790 to 8.0.0_GA_5434
    Stopping zimbra services...done.
    Starting mysql...

  2. #2
    lytledd is offline Elite Member
    Join Date
    Dec 2009
    Location
    Michigan
    Posts
    448
    Rep Power
    5

    Default

    Do you want to verify message store database integrity? [Y]
    Try again, but this time, say no to the above question.

    Doug
    Ben Franklin quote:

    "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."

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

    Default

    I can do this. But im sur that "Starting mysql..." keep blocking

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

    Default

    Someone can help me ?

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

    Default

    I dont have "/etc/mysql/conf.d/" directory in my server.

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

    Default

    I have resolve my problem :

    Code:
    /opt/zimbra/mysql/bin/mysqladmin: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
    Fatal error in defaults handling. Program aborted
    /opt/zimbra/mysql/bin/mysqladmin: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
    Fatal error in defaults handling. Program aborted
    I have create cront.d folder in /etc/mysql

    Now i have this error in the upgrade
    Code:
    Starting mysql...done.
    ERROR 1133 (42000) at line 2: Can't find any matching row in the user table
    ERROR 1396 (HY000) at line 1: Operation DROP USER failed for ''@'mail'

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

    Default

    /etc/mysql/conf.d/ is the default mysql config location, since zimbra have own mysql server this directory isn't needed.
    please show me your /opt/zimbra/log/mysql_error.log after you see this error.

    zimbra mysql server can be used for free simply calling the 'mysql' client with the zimbra user (no password needed)
    once you can login to the mysql prompt you can see the databases with this command:
    show databases;

    The important database is 'zimbra'
    This is how should look like the tables structure in ZCS 8
    mysql> show tables;
    +-------------------+
    | Tables_in_zimbra |
    +-------------------+
    | config |
    | current_volumes |
    | deleted_account |
    | mailbox |
    | mailbox_metadata |
    | mobile_devices |
    | out_of_office |
    | pending_acl_push |
    | scheduled_task |
    | service_status |
    | table_maintenance |
    | volume |
    +-------------------+

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

    Default

    hi,

    Here what i have in mysql_error.log

    Code:
    121010 10:25:51 mysqld_safe Starting mysqld daemon with databases from /opt/zimbra/db/data
    InnoDB: The InnoDB memory heap is disabled
    InnoDB: Mutexes and rw_locks use GCC atomic builtins
    InnoDB: Compressed tables use zlib 1.2.3.3
    121010 10:25:51  InnoDB: Initializing buffer pool, size = 499.0M
    121010 10:25:51  InnoDB: Completed initialization of buffer pool
    121010 10:25:51  InnoDB: highest supported file format is Barracuda.
    121010 10:25:51 InnoDB Plugin 1.0.17 started; log sequence number 296375368
    121010 10:25:51 [Note] Event Scheduler: Loaded 0 events
    121010 10:25:51 [Note] /opt/zimbra/mysql/libexec/mysqld: ready for connections.
    Version: '5.1.63-log'  socket: '/opt/zimbra/db/mysql.sock'  port: 7306  Source distribution
    121010 10:25:57 [Note] /opt/zimbra/mysql/libexec/mysqld: Normal shutdown
    
    121010 10:25:57 [Note] Event Scheduler: Purging the queue. 0 events
    121010 10:25:57  InnoDB: Starting shutdown...
    121010 10:26:01  InnoDB: Shutdown completed; log sequence number 296375378
    121010 10:26:01 [Note] /opt/zimbra/mysql/libexec/mysqld: Shutdown complete
    
    121010 10:26:01 mysqld_safe mysqld from pid file /opt/zimbra/db/mysql.pid ended
    121010 10:27:58 mysqld_safe Starting mysqld daemon with databases from /opt/zimbra/db/data
    121010 10:27:58 InnoDB: The InnoDB memory heap is disabled
    121010 10:27:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    121010 10:27:58 InnoDB: Compressed tables use zlib 1.2.3.3
    121010 10:27:58 InnoDB: Initializing buffer pool, size = 499.0M
    121010 10:27:59 InnoDB: Completed initialization of buffer pool
    121010 10:27:59 InnoDB: highest supported file format is Barracuda.
    InnoDB: 127 rollback segment(s) active.
    121010 10:27:59  InnoDB: Waiting for the background threads to start
    121010 10:28:00 InnoDB: 1.1.8 started; log sequence number 296375378
    121010 10:28:00 [Note] Server hostname (bind-address): 'localhost'; port: 7306
    121010 10:28:00 [Note]   - 'localhost' resolves to '::1';
    121010 10:28:00 [Note]   - 'localhost' resolves to '127.0.0.1';
    121010 10:28:00 [Note] Server socket created on IP: '127.0.0.1'.
    121010 10:28:00 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
    121010 10:28:00 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
    121010 10:28:00 [Note] Event Scheduler: Loaded 0 events
    121010 10:28:00 [Note] /opt/zimbra/mysql/bin/mysqld: ready for connections.
    Version: '5.5.24-log'  socket: '/opt/zimbra/db/mysql.sock'  port: 7306  Source distribution

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

    Default

    zimbra upgrade mysql from 5.1 to 5.5 along the 7.2.x-> 8.0 upgrade
    your mysql databases not upgraded properly along the zimbra upgrade process
    but my problem is zimbra mysql server is not exactly like the original mysql server, its not need the proxies_priv table for example...

    what is the output of this?
    cat /opt/zimbra/conf/my.cnf
    (i need just the first few row after the [mysqld])

    and what the output of this?
    ps ax | grep mysql

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

    Default

    Quote Originally Posted by vadonka View Post
    zimbra upgrade mysql from 5.1 to 5.5 along the 7.2.x-> 8.0 upgrade
    your mysql databases not upgraded properly along the zimbra upgrade process
    but my problem is zimbra mysql server is not exactly like the original mysql server, its not need the proxies_priv table for example...

    what is the output of this?
    cat /opt/zimbra/conf/my.cnf
    (i need just the first few row after the [mysqld])

    and what the output of this?
    ps ax | grep mysql
    root@mail:~# ps ax | grep mysql
    22003 pts/0 S+ 0:00 grep --color=auto mysql

    my.cnf
    Code:
    [client]
    port            = 3306
    socket          = /var/run/mysqld/mysqld.sock
    
    # Here is entries for some specific programs
    # The following values assume you have at least 32M ram
    
    # This was formally known as [safe_mysqld]. Both versions are currently parsed.
    [mysqld_safe]
    socket          = /var/run/mysqld/mysqld.sock
    nice            = 0
    
    [mysqld]

Page 1 of 2 12 LastLast

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
  •