MySQL/Wordpress issue
-
@scottalanmiller said in MySQL/Wordpress issue:
Yup, that is WAY more than enough memory
Had way more before we downsized. Went the lowest I could while making sure we had enough space for the site itself.
-
Okay, so at this point we need logs.
-
And, and those two sar reports.
-
@scottalanmiller said in MySQL/Wordpress issue:
And, and those two sar reports.
root@www:~# sar
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstatroot@www:~# sar -r
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstat -
@scottalanmiller said in MySQL/Wordpress issue:
Okay, so at this point we need logs.
From what location? /var/ or /etc/ ?
-
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
Okay, so at this point we need logs.
From what location? /var/ or /etc/ ?
Logs are always in /var
-
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
And, and those two sar reports.
root@www:~# sar
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstatroot@www:~# sar -r
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstatYou need to enable sar collection. It's very important for all investigation.
-
@scottalanmiller said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
Okay, so at this point we need logs.
From what location? /var/ or /etc/ ?
Logs are always in /var
I'm not seeing any logs that are viewable
-
@scottalanmiller said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
And, and those two sar reports.
root@www:~# sar
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstatroot@www:~# sar -r
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstatYou need to enable sar collection. It's very important for all investigation.
enabled now.
-
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?
-
@jmoore said in 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?
root@www:~# mysqladmin -u root -p status
Enter password:
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!Even if I run service mysql restart and then run the status I get the same issue.
-
@wls-itguy said in MySQL/Wordpress issue:
@jmoore said in 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?
root@www:~# mysqladmin -u root -p status
Enter password:
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!Even if I run service mysql restart and then run the status I get the same issue.
Except this time I did get a result:
root@www:~# mysqladmin -u root -p status
Enter password:
Uptime: 16 Threads: 47 Questions: 2886 Slow queries: 0 Opens: 103 Flush tables: 1 Open tables: 95 Queries per second avg: 180.375 -
And now it is down again
-
@scottalanmiller said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
And, and those two sar reports.
root@www:~# sar
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstatroot@www:~# sar -r
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstatYou need to enable sar collection. It's very important for all investigation.
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
And, and those two sar reports.
root@www:~# sar
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstatroot@www:~# sar -r
Cannot open /var/log/sysstat/sa21: No such file or directory
Please check if data collecting is enabled in /etc/default/sysstatYou need to enable sar collection. It's very important for all investigation.
enabled now.
Still cannot run the SAR or SAR -R requests. Even after an apache restart and a reboot of the server
-
@wls-itguy Did you try with sudo?
-
@dustinb3403 said in MySQL/Wordpress issue:
@wls-itguy Did you try with sudo?
I'm logged in as root
But I tried anyway and it didn't change anything
-
Would a re-install of MySQL help?
-
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 -
@wls-itguy said in MySQL/Wordpress issue:
@dustinb3403 said in MySQL/Wordpress issue:
@wls-itguy Did you try with sudo?
I'm logged in as root
But I tried anyway and it didn't change anything
What output are you receiving?
No, don't reinstall MySQL (at least not yet. . . or without backups)
-
@jmoore said in 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 mysqlFails to restart
