MySQL/Wordpress issue
-
@wls-itguy said in MySQL/Wordpress issue:
@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?
The top command. But it isn't a good tool for that. For immediately memory use this instead free -m
-
Sorry I've been away. Had a morning call then hanging with my dad. I'm here now.
-
Can I get the output of **df -h ** as well?
-
@scottalanmiller said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
@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?
The top command. But it isn't a good tool for that. For immediately memory use this instead free -m
Total 3948 used 343
-
@scottalanmiller said in MySQL/Wordpress issue:
Can I get the output of **df -h ** as well?
Filesystem Size Used Avail Use% Mounted on
/dev/root 16G 14G 2.6G 84% /
devtmpfs 2.0G 0 2.0G 0% /dev
tmpfs 395M 196K 395M 1% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 893M 0 893M 0% /run/shm -
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
@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?
The top command. But it isn't a good tool for that. For immediately memory use this instead free -m
Total 3948 used 343
The full output would be best, but that gives us a starting point.
-
@scottalanmiller said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
@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?
The top command. But it isn't a good tool for that. For immediately memory use this instead free -m
Total 3948 used 343
The full output would be best, but that gives us a starting point.
root@www:~# free -m total used free shared buffers cached Mem: 3948 347 3601 0 5 37 -/+ buffers/cache: 304 3644 Swap: 511 19 492 -
Yup, that is WAY more than enough memory
-
@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
