mysqld: Too many arguments (first extra is 'restart'). Please refer to Inno DB: DB: about forcing recovery.
Use --verbose --help to get a list of available options 110203 [ERROR] Aborting 110203 [Warning] Forcing shutdown of 1 plugins 110203 [Note] mysqld: Shutdown complete Inno DB: Error: tried to read 65536 bytes at offset 0 4804096. mysqld(my_print_stacktrace 0x21)[0x8489de1] mysqld(handle_segfault 0x37f)[0x81e226f] [0x110420] [0x110410] /lib/6(gsignal 0x50)[0xb5dd80] /lib/6(abort 0x101)[0xb5f691] mysqld[0x83c7fc8] mysqld(fil_io 0x226)[0x8395b16] mysqld(log_group_read_log_seg 0xc0)[0x83b8d40] mysqld[0x83c0b7e] mysqld(recv_recovery_from_checkpoint_start 0x50d)[0x83c10fd] mysqld(innobase_start_or_create_for_mysql 0x127c)[0x83fc7ec] mysqld[0x835d91b] mysqld(_Z24ha_initialize_handlerton P13st_plugin_int 0x34)[0x82bfcf4] mysqld[0x833e8de] mysqld(_Z11plugin_init Pi PPci 0x863)[0x8340df3] mysqld[0x81e4474] mysqld(main 0x4d6)[0x81e55a6] /lib/6(__libc_start_main 0xdc)[0xb4ae8c] mysqld(exit 0xd9)[0x8132811] 111008 - mysqld got signal 6 ; This could be because you hit a bug.
140227 Inno DB: The Inno DB memory heap is disabled 140227 Inno DB: Mutexes and rw_locks use Inno DB's own implementation 140227 Inno DB: Compressed tables use zlib 1.2.3 140227 Inno DB: Using Linux native AIO 140227 Inno DB: Initializing buffer pool, size = 128.0M 140227 Inno DB: Completed initialization of buffer pool 140227 Inno DB: highest supported file format is Barracuda.
140227 Inno DB: Waiting for the background threads to start 140227 Inno DB: 5.5.35 started; log sequence number 2155325 140227 [ERROR] /usr/sbin/mysqld: unknown variable 'set-variable=100' 140227 [ERROR] Aborting 140227 Inno DB: Starting shutdown...
After a good 20 minutes spent on Google trying various things (hunting down the mysql.plugin file to verify its permissions, removing my file, verifying my file was getting erased, etc), I finally stumbled upon the answer: My SQL was still running under a different hostname.
$ ls -l /var/lib/mysql/ total 41128 -rw-rw---- 1 _mysql _mysql 15566 Aug 14 Gabriels-Mac Book.-rw-rw---- 1 _mysql _mysql 771 Aug 15 SDF1.-rw-rw---- 1 _mysql _mysql 5 Aug 15 SDF1.... -rw-rw---- 1 _mysql _mysql 53778 Aug 16 laptop-134....
If it is not fresh installation, do a rpm -Uvh instead) Remove all contents of /var/lib/mysql/ directory Re-install RPM check if /var/lib/mysql/mysql/is created after installing RPM Then give a service mysql start and watch logs.
Inno DB only wrote those files full of Inno DB: zeros, but did not yet use them in any way.
But be careful: do not Inno DB: remove old data files which contain your precious data!
The suggestion on net was to delete pid file, but the thing was not even there at all. I knew that prob was probably one inodb table which probaly got "to big" log: Inno DB: Unable to lock ./ibdata1, error: 11 .....
Inno DB: Unable to lock ./ibdata1, error: 11 Inno DB: Check that you do not already have another mysqld process Inno DB: using the same Inno DB data or log files.
110203 [ERROR] Plugin 'Inno DB' init function returned error.