Results 1 to 7 of 7

Thread: Installation fails, possible mysql problem

  1. #1
    webminster is offline Junior Member
    Join Date
    Sep 2005
    Posts
    5
    Rep Power
    9

    Default Installation fails, possible mysql problem

    Installing on Fedora Core 3... Get to the install step "Starting Servers..." and install hangs. I note in the mysql log the following:

    InnoDB: Setting log file ./ib_logfile0 size to 14 MB
    InnoDB: Database physically writes the file full: wait...
    InnoDB: Error: ib_logfiles are too small for innodb_thread_concurrency 200.
    InnoDB: The combined size of ib_logfiles should be bigger than
    InnoDB: 200 kB * innodb_thread_concurrency.
    InnoDB: To get mysqld to start up, set innodb_thread_concurrency in my.cnf
    InnoDB: to a lower value, for example, to 8. After an ERROR-FREE shutdown
    InnoDB: of mysqld you can adjust the size of ib_logfiles, as explained in
    InnoDB: http://dev.mysql.com/doc/mysql/en/Ad..._removing.html
    InnoDB: Cannot continue operation. Calling exit(1).
    050908 20:59:52 mysqld ended

    Any way to get past this? Thanks.
    -Alan

  2. #2
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    18

    Default

    Hi,

    Can you run df -k and check your available disk space?

    thanks

    -kevin

  3. #3
    webminster is offline Junior Member
    Join Date
    Sep 2005
    Posts
    5
    Rep Power
    9

    Default

    [asparks@phoenix ~]$ df
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/hda2 20161204 15959068 3177996 84% /
    /dev/hda1 101086 22552 73315 24% /boot
    none 94832 0 94832 0% /dev/shm
    /dev/shm 153600 28 153572 1% /opt/zimbra/amavisd/tmp

    Thanks.

  4. #4
    marcmac is offline Expert Member
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    13

    Default This actually looks like a memory shortage

    Quote Originally Posted by webminster
    Installing on Fedora Core 3... Get to the install step "Starting Servers..." and install hangs. I note in the mysql log the following:

    InnoDB: Setting log file ./ib_logfile0 size to 14 MB
    InnoDB: Database physically writes the file full: wait...
    InnoDB: Error: ib_logfiles are too small for innodb_thread_concurrency 200.
    InnoDB: The combined size of ib_logfiles should be bigger than
    InnoDB: 200 kB * innodb_thread_concurrency.
    InnoDB: To get mysqld to start up, set innodb_thread_concurrency in my.cnf
    InnoDB: to a lower value, for example, to 8. After an ERROR-FREE shutdown
    InnoDB: of mysqld you can adjust the size of ib_logfiles, as explained in
    InnoDB: http://dev.mysql.com/doc/mysql/en/Ad..._removing.html
    InnoDB: Cannot continue operation. Calling exit(1).
    050908 20:59:52 mysqld ended

    Any way to get past this? Thanks.
    -Alan
    It looks like you don't have enough memory - by default, we assign 40% of available system memory to mysql. The log files are sized at 20% of that value - so, if you've got limited RAM, the log file sizes are too low for the concurrency value.

    To fix this, edit /opt/zimbra/conf/my.cnf and lower innodb_thread_concurrency from 200. THe error message shows that your logfiles are 14M, so concurrency*200kB should be less than that - so a value of 50 should work.

    Additionally, you'll want to lower max_connections in my.cnf to a smaller value - 50 should work for that, too.

    This is being tracked in bug 3911
    Last edited by marcmac; 09-09-2005 at 11:43 AM. Reason: Added bug reference

  5. #5
    webminster is offline Junior Member
    Join Date
    Sep 2005
    Posts
    5
    Rep Power
    9

    Default

    How do I do this during running install.sh? How do I pre-change the configuration so it'll start the DB properly during the "initializing db" phase? The installation is corrupt since the database won't come up for initialization...
    -Alan

  6. #6
    marcmac is offline Expert Member
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    13

    Default Fix for this problem

    What you need to do is modify the innodb_thread_concurrency and max_connections prior to mysql installation.

    You'll need to modify the install.sh script.

    Before the line that runs "zmmyinit" (line 989, I think) you'll want to add these two lines (inside the conditional block):

    runAsZimbra "zmlocalconfig -e mysql_innodb_thread_concurrency=50"
    runAsZimbra "zmlocalconfig -e mysql_max_connections=50"

    This will set the parameters prior to database creation.

    Quote Originally Posted by webminster
    How do I do this during running install.sh? How do I pre-change the configuration so it'll start the DB properly during the "initializing db" phase? The installation is corrupt since the database won't come up for initialization...
    -Alan

  7. #7
    webminster is offline Junior Member
    Join Date
    Sep 2005
    Posts
    5
    Rep Power
    9

    Default

    Thanks! Good call, that worked nicely.
    -Alan

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Use existing MySQL installation
    By daimer77 in forum Installation
    Replies: 6
    Last Post: 05-07-2009, 08:48 AM
  2. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 12:42 AM
  3. Installation fails on zimbra-store
    By wyleyrabbit in forum Installation
    Replies: 8
    Last Post: 01-15-2006, 08:19 AM
  4. Installation problem
    By sywong70 in forum Installation
    Replies: 5
    Last Post: 11-07-2005, 09:01 PM
  5. Installation fault - getDirectContext fails
    By gregjohnson1024 in forum Administrators
    Replies: 3
    Last Post: 11-07-2005, 04:28 PM

Posting Permissions

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