Re: Innodb Crash recovery

[Andrew Stanfield]

+1 I have had almost the exact same problem. Here is my code below. Many of the forums I've reviewed talk about mysql running out of memory (causing it to crash), not sure if that is the problem here or not. I am running 3 databases on an Amazon micro instance so running out of memory is possible, though I'm the only person using the server at the moment. Thoughts?

130529 18:41:01 mysqld_safe Number of processes running now: 0
130529 18:41:01 mysqld_safe mysqld restarted
130529 18:41:01 [Note] Plugin 'FEDERATED' is disabled.
130529 18:41:01 InnoDB: The InnoDB memory heap is disabled
130529 18:41:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130529 18:41:01 InnoDB: Compressed tables use zlib 1.2.5
130529 18:41:01 InnoDB: Using Linux native AIO
130529 18:41:01 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
130529 18:41:01 InnoDB: Completed initialization of buffer pool
130529 18:41:01 InnoDB: Fatal error: cannot allocate memory for the buffer pool
130529 18:41:01 [ERROR] Plugin 'InnoDB' init function returned error.
130529 18:41:01 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130529 18:41:01 [ERROR] Unknown/unsupported storage engine: InnoDB
130529 18:41:01 [ERROR] Aborting

130529 18:41:01 [Note] /usr/libexec/mysqld: Shutdown complete

130529 18:41:01 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended