365pricefinder
Regular Member
- Mar 1, 2016
- 224
- 33
Wordpress Database Connection Error
- Thread starter VeeGeeN
- Start date
roadhamster
Regular Member
- Mar 12, 2012
- 362
- 261
Check the logfiles and find out where and why it goes wrong.
It maybe time to tweak your MySql, increase number of simultaneous connections, increase memory usage, increase buffers, change (if you haven't already) to InnoDB, replace Mysql with MariaDB or Percona server (assuming your running linux on VPS). You can install Apache mod_cache plugin to get the pressure off of your database, but as said, first thing is to check the logs!
It maybe time to tweak your MySql, increase number of simultaneous connections, increase memory usage, increase buffers, change (if you haven't already) to InnoDB, replace Mysql with MariaDB or Percona server (assuming your running linux on VPS). You can install Apache mod_cache plugin to get the pressure off of your database, but as said, first thing is to check the logs!
seomastervang
BANNED
- Jul 9, 2016
- 144
- 4
still u tried to help and thats good thing
MaFiaStyle
Regular Member
- May 23, 2016
- 353
- 173
OP, the issue is most likely caused by Jetpack. Are you using the share function? And trying to add more social accounts when you encounter this error?
superindian
BANNED
- Jun 28, 2016
- 79
- 5
does share button hamper database?
aafable
Registered Member
- Sep 25, 2015
- 70
- 8
Well, you don't have to be mean about it. I was just trying to help. If I can't figure it out, I check everything. That's just me though. A simple, "I don't think that's it," would've been sufficient enough.
- Apr 23, 2012
- 2,842
- 5,850
I wouldn't call that being mean. I was simply stating that you commented without reading the while post.
MaFiaStyle
Regular Member
- May 23, 2016
- 353
- 173
Yes potentially because Jetpack consumes a lot of system resources. Apart from that Publicze has 15 social account limitation, once you hit that limit you cannot add more accounts and you will see the db error.
MaFiaStyle
Regular Member
- May 23, 2016
- 353
- 173
Good advice. By default some hosting provider limit the memory to 64MB.Try asking your hosting provider to increase to 128 and see if it helps.
superindian
BANNED
- Jun 28, 2016
- 79
- 5
one thing
try database cache
try database cache
Drewdude1991
Newbie
- Jun 11, 2015
- 38
- 3
Now contact your hosting company and tell us what type of problems are you facing.
This. I have some sites running on a vps as well, you should really optimize the configuration of the mysql database, maybe switch to Mariadb as well. And I solved the problem by adding swap, no shit. I had the exact same problem until I added swap, even if it's a bit slower, your database won't crash until you fix the problem.
And some posts before said that it might be because of the caching which I don't think it is. I think your caching isn't even working. Because whenever I had the mysql crash, all I was not able to do is get into the wp-admin page. The cached sites were still served and why wouldn't they, that's what the caching is for. But in the wp-admin panel you always need your database so I think there might be an error as well
Edit: look at a cached source code of your page. Normally the caching plug-ins add some text like "cached by $plug-in name". If that's not true for you, you got at least one error
UniBul
Registered Member
- Apr 18, 2015
- 77
- 16
OP, I had exactly the same problem for close to two years and tried all kinds of things, including changing several hosting companies. None of them was able to help me fix the issue, but eventually I stumbled on the solution.
Someone else already suggested it -- do yourself a favor and get the Wordfence plug-in and start restricting incoming traffic from bots, crawlers and everyone else. As you are using CloudFlare, as I do, you will have to whitelist all CloudFlare IP addresses (just Google them) and adjust the "How does Wordfence get IPs" option to "Use CloudFlare "CF-Connecting-IP" HTTP header" (the last option). Make sure you do those adjustments, otherwise you'll be having troubles. Oh, and remove the CloudFlare plug-in -- you don't need it.
Since I installed Wordfence I've had no such issues.
Someone else already suggested it -- do yourself a favor and get the Wordfence plug-in and start restricting incoming traffic from bots, crawlers and everyone else. As you are using CloudFlare, as I do, you will have to whitelist all CloudFlare IP addresses (just Google them) and adjust the "How does Wordfence get IPs" option to "Use CloudFlare "CF-Connecting-IP" HTTP header" (the last option). Make sure you do those adjustments, otherwise you'll be having troubles. Oh, and remove the CloudFlare plug-in -- you don't need it.
Since I installed Wordfence I've had no such issues.
