MySQL InnoDB Error

We have recently moved a WordPress/ecommerce website to our Cpanel hosting environment and came across a new error today (site has been on our server for 5 days)

The website goes down unexpectedly and displays this error in the browser:
Error while connecting to MySQL: Couldn't connect to localhost:3306/tcp: IO::Socket::INET: connect: Connection refused

We have tracked it down to InnoDB, but we have no idea why this is happening or how to fix it.


140121 11:25:19 InnoDB: The InnoDB memory heap is disabled
140121 11:25:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140121 11:25:19 InnoDB: Compressed tables use zlib 1.2.3
140121 11:25:19 InnoDB: Using Linux native AIO
140121 11:25:19 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
140121 11:25:19 InnoDB: Completed initialization of buffer pool
140121 11:25:19 InnoDB: Fatal error: cannot allocate memory for the buffer pool
140121 11:25:19 Plugin 'InnoDB' init function returned error.
140121 11:25:19 Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140121 11:25:19 Unknown/unsupported storage engine: InnoDB
140121 11:25:19 Aborting

140121 11:25:19 [Note] /usr/sbin/mysqld: Shutdown complete

140121 11:25:19 mysqld_safe mysqld from pid file /var/lib/mysql/festaparties.topgeartechnologies.com.pid ended
140121 12:55:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140121 12:55:47 [Note] Plugin 'FEDERATED' is disabled.
140121 12:55:47 InnoDB: The InnoDB memory heap is disabled
140121 12:55:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140121 12:55:47 InnoDB: Compressed tables use zlib 1.2.3
140121 12:55:47 InnoDB: Using Linux native AIO
140121 12:55:47 InnoDB: Initializing buffer pool, size = 128.0M
140121 12:55:47 InnoDB: Completed initialization of buffer pool
140121 12:55:47 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140121 12:55:47 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
TopGearTechAsked:
Who is Participating?
 
snoyes_jwConnect With a Mentor Commented:
Error 12 means not enough space. You're too low on memory.

128M isn't too large for a buffer pool, so check what other things might be set too large (like the query cache or something), and maybe talk with your provider about how much memory you are allocated.
0
 
TopGearTechAuthor Commented:
Thanks for your reply.  I'm self-hosting, couldn't I just increase buffer pool?
0
 
TopGearTechAuthor Commented:
Thank You!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.