MySQL/Wordpress issue
-
@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
topwould 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 -
Goign to lunch, be back in a bit.
-
@wls-itguy said in MySQL/Wordpress issue:
4GB plan through Linode.
1GB should be plenty.
What's the output of sar and sar -r?
-
@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.
