From my earlier post it still looks like you are getting spammed.
This: [Fri Jul 21 09:11:40 2017] [error] server reached MaxClients setting, consider raising the MaxClients setting
says that to me. In your Apache2.conf file you can adjust that using an editor then restart Apache. Since you are on Linode you will find this useful, tuning apache.
Posts made by jmoore
-
RE: MySQL/Wordpress issue
-
RE: MySQL/Wordpress issue
@wls-itguy Well thats a bummer. What does your apache error log say when that happens?
-
RE: MySQL/Wordpress issue
Well I think things are looking up. That was a good idea from Scott to shut down Apache and then work with mysql. I think you can go ahead and start Apache back up and let those run for a while to see what happens.
-
RE: Weekend Plans
Going to go hit some golf balls in a while. Pretty day, just hot
-
RE: MySQL/Wordpress issue
@wls-itguy said in MySQL/Wordpress issue:
I had some issues with wordpress updating and had done some permission changes to wordpress files
Well wordpress and the database communicate with each other so that could possibly be it but I'm not sure. Usually when Wordpress doesn't update it is because permissions are too stringent and you therefore loosen them. I doubt loosening permissions would break mysql. Thats why I am doubtful if that is all you did.
-
RE: MySQL/Wordpress issue
@wls-itguy said in MySQL/Wordpress issue:
I have daily snapshots and full backups.
Well it can be hard to diagnose things at times so in the interest of your time you might consider uninstalling mysql, reinstalling mysql, then importing your database back into mysql. Just consider it for now. Let others chime in for a bit in case someone else gets something to work for you.
-
RE: MySQL/Wordpress issue
Have you changed any permissions or config files recently?
-
RE: MySQL/Wordpress issue
Wow, tough problem. Let me think about it some more. Have you taken any backups recently in case you have to reinstall?
-
RE: MySQL/Wordpress issue
In most cases it should not matter but in a few I think it does. run the same command but use [start]. So:
[service mysql start] -
RE: MySQL/Wordpress issue
To be more clear, did you use the start or restart command?
-
RE: MySQL/Wordpress issue
That is indeed strange. When you did a ps aux was there more than 1 mysql process or just 1?
-
RE: The Motivations of Sales
So after reading all of this, do smb's or enterprises have any 1 single person or a team in the IT department that are trained to just deal with sales people? It seems if you had someone go through some type of training you would have to worry less about emotional responses to buying and therefore only buy what you need. Does anyone do this at all?
-
RE: MySQL/Wordpress issue
Ok to me it just sounds like mysql is in a funk. It also appears it is still running. I think you should try to kill the process and then start it back up. Do this from terminal:
ps aux
then look for process ID of mysql
from terminal : kill -9 ID
then from terminal again: service start mysql -
RE: MySQL/Wordpress issue
Back from lunch. I see Scott is here and he is infinitely more qualified lol. I am betting it is the data base. Did you ever do a status on mysql to see if it was responding?
-
RE: MySQL/Wordpress issue
To check all your memory at once just do this command from the terminal. [free -m ]
That will show you the current state of your memory.
Top command is just that. Type [top] in the terminal. Watch it for a while then hit ctrl-z to end the top session -
RE: MySQL/Wordpress issue
Ok yeah that still sounds like mysql just stopped responding and is just sitting there doing nothing. You first error indicates that it is not running.
Try this: [service mysql status] from the termina. Is mysql running and active?
-
RE: MySQL/Wordpress issue
Hmm I'm surprised your having issues with that much ram. I mean it certainly could be something else then. You have to check your logs to be sure. Main ones to check are your Apache log and Mysql log. I suspect its Mysql that is messing up though. I would run that Mysql tuner as it can't hurt and will only help.
Did you check to see if mysql is running and responding yet?