Issue Starting MySQL Daemon

mccabec123 · 08-17-2012, 05:13 AM

I have just come across the most random error I've seen my MySQL daemon spew out yet, everything was working fine, then all of a sudden it randomly crashed and it now outputting this when I start it up, not sure if it's because my 'my.cnf' file is minimal

Here's my 'my.cnf':

Code:

[mysqld]
    # Settings user and group are ignored when systemd is used.
    # If you need to run mysqld under different user or group,
    # customize your systemd unit file for mysqld according to the
    # instructions in http://fedoraproject.org/wiki/Systemd
    datadir=/var/lib/mysql/
    socket=/var/lib/mysql/mysql.sock
    # Disabling symbolic-links is recommended to prevent assorted security risks
    symbolic-links=0
    
    [mysqld_safe]
    log-error=/var/log/mysqld.log
    pid-file=/var/run/mysqld/mysqld.pid

Here's the errors:

Code:

120817  3:47:26 [Note] Plugin 'FEDERATED' is disabled.
    120817  3:47:26 InnoDB: The InnoDB memory heap is disabled
    120817  3:47:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    120817  3:47:26 InnoDB: Compressed tables use zlib 1.2.5
    120817  3:47:26 InnoDB: Using Linux native AIO
    120817  3:47:26 InnoDB: Initializing buffer pool, size = 128.0M
    120817  3:47:26 InnoDB: Completed initialization of buffer pool
    InnoDB: Error: auto-extending data file ./ibdata1 is of a different size
    InnoDB: 384 pages (rounded down to MB) than specified in the .cnf file:
    InnoDB: initial 640 pages, max 0 (relevant if non-zero) pages!
    120817  3:47:26 InnoDB: Could not open or create data files.
    120817  3:47:26 InnoDB: If you tried to add new data files, and it failed here,
    120817  3:47:26 InnoDB: you should now edit innodb_data_file_path in my.cnf back
    120817  3:47:26 InnoDB: to what it was, and remove the new ibdata files InnoDB created
    120817  3:47:26 InnoDB: in this failed attempt. InnoDB only wrote those files full of
    120817  3:47:26 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
    120817  3:47:26 InnoDB: remove old data files which contain your precious data!
    120817  3:47:26 [ERROR] Plugin 'InnoDB' init function returned error.
    120817  3:47:26 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    120817  3:47:26 [ERROR] mysqld: unknown variable 'max_used_connections=0'
    120817  3:47:26 [ERROR] Aborting
    
    120817  3:47:26 [Note] mysqld: Shutdown complete

Any help would be greatly appreciated, thanks guys!

dinkus223 · 08-17-2012, 06:14 AM

With a minimum config file and sudden crash, I suspect that it is something simple, without reviewing your config file. A little googling brought up https://forums.mysql.com/read.php?22...055#msg-241055. [URL="http://onaxer.com/blog/blog/tag/error-plugin-innodb-init-function-returned-error/"]. For confirmation, http://onaxer.com/blog/blog/tag/erro...eturned-error/ has a more detailed, if you will, explanation. Also make sure that only one config file is referenced: /etc/my.cnf /etc/mysql/my.cnf /usr/etc/my.cnf ~/.my.cnf.