MySQL/Wordpress issue
-
Good Morning All,
I have been having this issue with MySQL on our main website where out of the blue MySQL services stop. I get this error on the page:
Warning: mysql_connect(): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) in /var/www/wls.wels.net/public_html/wp-includes/wp-db.php on line 1568
And usually if I restart the services all is good for about a week. Now it doesn't even take 2-3 minutes before the services stop again.
I have run through some things that I found on searches but nothing has fixed the issue so far. I am not a linux/MySQL guru by any means and any kick in a better direction would be greatly appreciated.
Jeff
-
Hey Jeff,
Are the MySQL server and Web server on the same box?
-
Yes. Linode host. I have checked space on the server and there is no issue there.
-
Jeff,
I am not a mysql guru either but to me this sounds like you are running out of memory from hackers/bored kids. I have seen this on my own servers. You can check your logs, usually at /var/log/mysql ( I believe is the path). Do a [tail -100 mysql.log] and see if you have line after line of something that like (Post Get HTTP from weird IP addresses). When they constantly do their scanning on ranges of IP addresses they can do some weird stuff that stresses your database out. I doubt you are being targeted in any way because they are just hitting everything with constant barrage of scans. I would run MySql Tuner from that link which also has a guide on how to do it. That should help. Good Luck
-
In another search I found said to run 'find / -type s | grep mysqld.sock'
And I got the following results.
find:
/proc/8311/task/8311/fd/5': No such file or directory find:
/proc/8311/task/8311/fdinfo/5': No such file or directory
find:/proc/8311/fd/5': No such file or directory find:
/proc/8311/fdinfo/5': No such file or directoryNot sure what that means
-
@wls-itguy
I am not sure what that means either. Have you started the mysql.service back up? If you do a [systemctl status mysql.service] from the terminal does it say its active(in green letters) and running? -
That actually sounds like the service is not running or responding to me but do check that with the command above.
-
running Debian 7
-
Right sorry , I do everything in Fedora/Centos. The syntax will be different then
-
@wls-itguy How much RAM?
-
4GB plan through Linode.
-
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?
-
@aaronstuder said in MySQL/Wordpress issue:
@wls-itguy How much RAM?
@wls-itguy said in MySQL/Wordpress issue:
4GB plan through Linode.
Now that I think about it. We resized (downsized) about 2 months ago and I'd like to think that it was around that time (maybe a little later) that this issue showed up.
-
@jmoore
When I restart MySQL I get this:Checking for tables which need an upgrade, are corrupt or were
not closed cleanly.. -
Using
top
would show you the ram usage.... -
Installing netdata may be of use... I'm still trying to figure out where I might use it.
Others were saying it sends anonymous data back to the developers site... but I don't know if that's true or not. Maybe a flag to disable etc..
-
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?
-
@jmoore It is when I restart the service. and then about 30-90 seconds later it stops again.
@DustinB3403 What do you mean by using top?
-
Running top from the cli would show you the ram usage, high ram users etc.
-
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