MySQL not starting with this my.cnf file

Discussion in 'MySQL' started by tyler_durden, Mar 14, 2011.

  1. #1
    Currently I am running off this small my.cnf file:

    [mysqld]
    innodb_file_per_table=1
    
    max_connections=500
    key_buffer=128M
    myisam_sort_buffer_size=32M
    join_buffer_size=1M
    read_buffer_size=1M
    sort_buffer_size=1M
    table_cache=512
    thread_cache_size=128
    wait_timeout=90
    connect_timeout=30
    max_allowed_packet=16M
    max_heap_table_size=48M
    tmp_table_size=64M
    max_connect_errors=10
    query_cache_limit=1M
    query_cache_size=32M
    query_cache_type=1
    Code (markup):
    A few weeks ago I converted my tables to InnoDb from MyISAM but I have not changed the my.cnf file to use it correctly. Below is the file i am now trying to restart MySQL with and is failing. I'm new to MySQl and db usage in general, so it's something likely simple. Also, if it is not starting properly is there an error log for the details of why?

    [mysqld]
    log-bin
    log
    log-error
    log-slow-queries
    default_storage_engine = InnoDB
    max_connections=500
    key_buffer=16M
    myisam_sort_buffer_size=4M
    join_buffer_size=1M
    read_buffer_size=1M
    sort_buffer_size=1M
    table_cache=512
    thread_cache_size=128
    wait_timeout=90
    connect_timeout=30
    max_allowed_packet=16M
    max_heap_table_size=16M
    tmp_table_size=16M
    max_connect_errors=10
    query_cache_limit=1M
    query_cache_size=16M
    query_cache_type=1
    
    innodb_buffer_pool_size = 1G
    innodb_data_home_dir = /var/lib/mysql
    innodb_data_file_path = ibdata1:10M:autoextend
    innodb_file_per_table = 1
    innodb_log_group_home_dir = /var/lib/mysql
    innodb_log_file_size = 32M
    innodb_log_buffer_size=4M
    innodb_flush_method = O_DIRECT
    innodb_thread_concurrency=8
    Code (markup):

     
    tyler_durden, Mar 14, 2011 IP
  2. jestep

    jestep Prominent Member

    Messages:
    3,659
    Likes Received:
    215
    Best Answers:
    19
    Trophy Points:
    330
    #2
    There could be errors in several locations. First check the mysql log, which is located in the mysql data directory, in your case: /var/lib/mysql/

    You may also generate errors in /var/log/faillog

    Most likely what happened is that you edited certain Innodb settings. This causes a mismatch in what Innodb is looking for in the log and other data files. Here's a guide on how many of the Innodb parameters need to be changed: http://dev.mysql.com/doc/refman/5.0/en/innodb-data-log-reconfiguration.html

    If it's buffer size and other non log related, you can usually edit and restart the server.
     
    jestep, Mar 15, 2011 IP