Mysql shutting down

v3
#1

I recently updated one server to the latest EE and since then I’ve had an issue with mysql shutting down. Looking at the log I see:

140505 17:40:26 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140505 17:40:26 [Note] Plugin ‘FEDERATED’ is disabled.
140505 17:40:26 InnoDB: The InnoDB memory heap is disabled
140505 17:40:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140505 17:40:26 InnoDB: Compressed tables use zlib 1.2.3.4
140505 17:40:26 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(135987200 bytes) failed; errno 12
140505 17:40:26 InnoDB: Completed initialization of buffer pool
140505 17:40:26 InnoDB: Fatal error: cannot allocate memory for the buffer pool
140505 17:40:26 [ERROR] Plugin ‘InnoDB’ init function returned error.
140505 17:40:26 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
140505 17:40:26 [ERROR] Unknown/unsupported storage engine: InnoDB
140505 17:40:26 [ERROR] Aborting

140505 17:40:26 [Note] /usr/sbin/mysqld: Shutdown complete

#2

EasyEngine adjust only wait_timeout and interactive_timeout variables.

140505 17:40:26 InnoDB: Initializing buffer pool, size = 128.0M InnoDB: mmap(135987200 bytes) failed; errno 12

Its seems like your buffer pool size is not enough
Please send me the /etc/mysql/my.cnf file

#3

Increased innodb_buffer_pool_size and restart mysql

#4

It’s changed a bit since I’ve been following suggestions of mysqltuner and a few other forum posts,
It’s a 512mb DO droplet
Here’s a link to the conf http://d.pr/n/Svgq/2381WD5O

And here’s the latest from mysqltuner

#5

I’ve increased mysql ram alooted and memcache and still my MySQL shuts down the same as everyone elses… Looks like I’ll be switching back to centmin mod this week.

#6

@Matthew

We never faced such problem, Its good if you provide me server login details for the debugging
purpose

You can send the login details at [email protected]

#7

I’ve found I’ve had to make a lot of changes to the mysql config in order to prevent it from crashing with EE. I had a 512 droplet on Digital Ocean that was running great with 4 sites on it (all low traffic) then after updating EE a few updates ago it started crashing several times per day. It took a lot of tweaking but I finally got everything stabilized.

#8

@coreyallen

Its good if you share your tweaking part here which helps others users to fix the problem

#9

I’m afraid I didn’t write down all of the steps but I basically just googled how to run wordpress on low end boxes. I have noticed my sites aren’t quite as fast as they were before I made the changes so I’ve probably misconfigured something. Still I’d rather have a site not as fast as opposed to a mysql DB error.
All and all I’m still thrilled with EE and can’t wait for all the amazing stuff you guys have planned in the future.
Thanks again!

#10

Finally stable with innodb_buffer_pool_size = 128M in my.cnf

I’ll let you know if anything changes.

#11

Crashed again. I’ll mail you.

#12

@Matthew

List of issue:

  1. no swap
  2. MySQL Maximum possible memory usage: 358.4M (73% of installed RAM)

As you are using 512 MB RAM without any swap partition, So once your RAM is full kernel start killing programs.

You need to create a 2gb swap space: https://www.digitalocean.com/community/articles/how-to-add-swap-on-ubuntu-12-04

Let me know after creating swap you face any issue

1 Like
#13

Hello @matthewlevy,

We haven’t heard back from you in long time. It looks like your issue is resolved.

I am closing this support ticket for now. Feel free to create a new support ticket if you have any queries further. :slight_smile:

#14