By danvega
My wordpress blog has been working for over a year and all of a sudden it stopped working. This morning I posted the following question on Stack Overflow
http://stackoverflow.com/questions/35799917/wordpress-site-down-mysql-crashing
I first decided to bump my memory from 512 to 1GB on the droplet. With no responses I started doing some digging. I found this solution which looked exactly like my problem so I tried setting up a swap file
http://www.webtrafficexchange.com/comment/reply/156
Still not having any luck here and this is the latest from my logs. Anyone have any clue is to what is happening to me?
160304 14:05:29 [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. 160304 14:05:29 [Note] Plugin ‘FEDERATED’ is disabled. 160304 14:05:29 InnoDB: The InnoDB memory heap is disabled 160304 14:05:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins 160304 14:05:29 InnoDB: Compressed tables use zlib 1.2.8 160304 14:05:29 InnoDB: Using Linux native AIO 160304 14:05:29 InnoDB: Initializing buffer pool, size = 64.0M InnoDB: mmap(68681728 bytes) failed; errno 12 160304 14:05:29 InnoDB: Completed initialization of buffer pool 160304 14:05:29 InnoDB: Fatal error: cannot allocate memory for the buffer pool 160304 14:05:29 [ERROR] Plugin ‘InnoDB’ init function returned error. 160304 14:05:29 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed. 160304 14:05:29 [ERROR] Unknown/unsupported storage engine: InnoDB 160304 14:05:29 [ERROR] Aborting
160304 14:05:30 [Note] /usr/sbin/mysqld: Shutdown complete
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Here is a detailed guide on how to fix crashed innodb tables
https://iserversupport.com/recover-crashed-innodb-tables-on-mysql-database-server/
One possibility is that you are being attacked via the XML-RPC interface. It’s unfortunately a fairly common reason that MySQL will exhaust all available memory. To check if this is the case, look for mentions in the webserver’s logs: grep xmlrpc /var/log/apache2/access.log
If that is the case, take a look at this article for a few options on how to mitigate the attack:
same problem I’ve done everything but not solved. but Finally, I solved the problem try this https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-16-04
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.