Question

Site shows "Error establishing a database connection"

My WordPress site had been fine all along, but roughly 36 hours ago, I noticed that it doesn’t load the site but shows Error establishing a database connection instead.

I certainly have not made any changes to the WordPress site itself, or my droplet settings recently.

What might have caused this? Thanks for any advise!

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

@arunsathiya

If the error was at random, I would recommend checking the MySQL error log to see if there was a crash. The command below will output the last 50 lines from the MySQL error log.

tail -50 /var/log/mysql/error.log

If you see lines with Out of memory or Killed process, MySQL is unable to allocate the RAM it needs to continue to run and the OOM killer is killing off the process.

There are a few ways to resolve this

  • Reboot the Droplet (short-term solution to get you back online)
  • Resize your Droplet
  • Optimize the MySQL configuration (MySQL Tuner is a great tool to get you started)
  • Enable Caching for your WordPress using a plugin (W3 Total Cache works very well)

Caching can help reduce resource usage by caching commonly requested data which, in turn, reduces the number of database calls that need to be made. It can be highly effective when combined with MySQL Tuner and general optimization.

Resizing is really the final recommendation when you’ve reached the point where you’ve enabled caching, optimized your configuration the best you can, and you still can’t get the resource usage under control (i.e. you just need more RAM).

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Maybe there was a locked table and you reached your MySQL max connections limit or the droplet ran out of memory and MySQL got killed. Were you able to check if MySQL was running and could you check your connections?

This comment has been deleted