# mysql crashed cannot restart

**URL:** <https://forums.percona.com/t/mysql-crashed-cannot-restart/4969>\
**Category:** Other MySQL® Questions\
**Created:** [July 14, 2016, 9:20am UTC](https://forums.percona.com/t/mysql-crashed-cannot-restart/4969 "2016-07-14T09:20:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pixelpadre](https://avatars.discourse-cdn.com/v4/letter/p/76d3ee/32.png) [@pixelpadre](https://forums.percona.com/u/pixelpadre)\
**Post date:** [July 14, 2016, 9:20am UTC](https://forums.percona.com/t/mysql-crashed-cannot-restart/4969/1 "2016-07-14T09:20:02Z")

</div>

This is the second time this has happened to me on two different VPS. Logs says insufficient memory but I have 2GB and 250MB swap for small websites. And its crashing on off peak hours.

this is my journalctl data at the time of the crash.

[url][http://paste.ubuntu.com/19369123/[/url]](http://paste.ubuntu.com/19369123/%5B/url%5D)

I cant get mysql to restart. my db files appears intact. Problem is restarting sql. I have tried to rename those 3 ibdata files and then rebooting sql. that worked once before but not this time.☹

Please help.

---

<div class="post-metadata">

**Author:** ![ChadScheiter](https://avatars.discourse-cdn.com/v4/letter/c/e19b73/32.png) [@ChadScheiter](https://forums.percona.com/u/ChadScheiter)\
**Post date:** [August 2, 2016, 4:37pm UTC](https://forums.percona.com/t/mysql-crashed-cannot-restart/4969/2 "2016-08-02T16:37:03Z")

</div>

The crash was obviously due to too much memory allocated. It appears you have quite a few different items running so 2GB might not be sufficient memory. You should not remove the ibdata files without setting ‘innodb\_fast\_shutdown=0’ [url][MySQL :: MySQL 5.7 Reference Manual :: 14.15 InnoDB Startup Options and System Variables](http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_fast_shutdown%5B/url%5D) as they contain data that has not been written to the table specific data files yet. Posting the error messages from the mysql startup process would help determine why the mysql daemon is not starting. You should also be able to install the mysqltuner package which will do some very rough calculations on the maximum amount of memory that could be used given your configuration, although those numbers will be higher than actual usage as not every connection will max out the total amount of memory that it can.

Chad