MySQL/Wordpress issue
-
@jmoore said in MySQL/Wordpress issue:
Have you changed any permissions or config files recently?
I had some issues with wordpress updating and had done some permission changes to wordpress files
-
@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.
-
@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:
Are you just running a single WordPress site here?
Yes. Single site.
Given that the site is now down... is there a good reason that you are running a WP site on your own instead of through a server (asks the guy who runs a service for that.)
It has been 2+ years since it has been set up this way. Wasn't broken, why fix it.
Someone had to set it up that way to start with
and...
http://www.smbitjournal.com/2017/07/if-it-aint-broke-dont-fix-it/
-
@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.
-
@wls-itguy said in MySQL/Wordpress issue:
@dustinb3403 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:
@scottalanmiller said in MySQL/Wordpress issue:
Are you just running a single WordPress site here?
Yes. Single site.
Given that the site is now down... is there a good reason that you are running a WP site on your own instead of through a server (asks the guy who runs a service for that.)
It has been 2+ years since it has been set up this way. Wasn't broken, why fix it.
Wrong. . . . .
You patch and update to ensure things remain functional.
Not what I was asked. It has been patched to the version I have. Just not upgraded to Debian 9.
Updating is not AS important as patching, but is important. Older systems become continuously harder and harder to maintain over time and eventually start having their own risks of things breaking - partially because other things change around them and they don't adapt to them. Partially just because the gap between them and current gets larger and larger and knowledge of supporting them or the ability to update gets harder.
-
@wls-itguy said in MySQL/Wordpress issue:
@jmoore said in MySQL/Wordpress issue:
Have you changed any permissions or config files recently?
I had some issues with wordpress updating and had done some permission changes to wordpress files
Try shutting down Apache. THEN bring up MySQL. Let's see if MySQL dies when nothing is touching it.
-
If MySQL dies when Apache is offline, then we can rule out issues with Apache or WordPress as being the problem. I'm assuming this is a pure MySQL issue, but want to be sure.
-
@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:
@scottalanmiller said in MySQL/Wordpress issue:
Are you just running a single WordPress site here?
Yes. Single site.
Given that the site is now down... is there a good reason that you are running a WP site on your own instead of through a server (asks the guy who runs a service for that.)
It has been 2+ years since it has been set up this way. Wasn't broken, why fix it.
Someone had to set it up that way to start with
and...
http://www.smbitjournal.com/2017/07/if-it-aint-broke-dont-fix-it/
What I meant by my statement was that it has been working. We didn't see a need to move it off a host to a wordpress specific site. I update it regularly but wasn't ready to upgrade to a new version of Debian at this time.
-
@scottalanmiller said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
@jmoore said in MySQL/Wordpress issue:
Have you changed any permissions or config files recently?
I had some issues with wordpress updating and had done some permission changes to wordpress files
Try shutting down Apache. THEN bring up MySQL. Let's see if MySQL dies when nothing is touching it.
@scottalanmiller said in MySQL/Wordpress issue:
If MySQL dies when Apache is offline, then we can rule out issues with Apache or WordPress as being the problem. I'm assuming this is a pure MySQL issue, but want to be sure.
So far it is still running:
root@www:~# mysqladmin -u root -p status
Enter password:
Uptime: 147 Threads: 1 Questions: 198 Slow queries: 0 Opens: 97 Flush tables: 1 Open tables: 90 Queries per second avg: 1.346 -
now what do you get from [service mysql status] ?
-
@jmoore said in MySQL/Wordpress issue:
now what do you get from [service mysql status] ?
root@www:~# service mysql status
[info] /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.55, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved.Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.Server version 5.5.55-0+deb7u1
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 5 min 46 secThreads: 1 Questions: 202 Slow queries: 0 Opens: 97 Flush tables: 1 Open tables: 90 Queries per second avg: 0.583.
-
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.
-
As soon as I start Apache2 MySQL stops working.
-
@wls-itguy Well thats a bummer. What does your apache error log say when that happens?
-
Okay, there is a really good chance that we have a WordPress issue here. I think that rolling back to before the last update might be the logical place to start.
-
@scottalanmiller said in MySQL/Wordpress issue:
Okay, there is a really good chance that we have a WordPress issue here. I think that rolling back to before the last update might be the logical place to start.
Any bets on a compromised plugin causing issues?
-
@scottalanmiller said in MySQL/Wordpress issue:
Okay, there is a really good chance that we have a WordPress issue here. I think that rolling back to before the last update might be the logical place to start.
If you want to isolate to WP (thought I cannot see how it is anything else), I would shut down apache,
mvyour WP directory elsewhere and start apache back up. -
@jaredbusch said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
Okay, there is a really good chance that we have a WordPress issue here. I think that rolling back to before the last update might be the logical place to start.
If you want to isolate to WP (thought I cannot see how it is anything else), I would shut down apache,
mvyour WP directory elsewhere and start apache back up.True, but in theory it is the only thing running on Apache. So likely it was isolated in the last test, unless the other info wasn't correct.
-
@scottalanmiller said in MySQL/Wordpress issue:
@jaredbusch said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
Okay, there is a really good chance that we have a WordPress issue here. I think that rolling back to before the last update might be the logical place to start.
If you want to isolate to WP (thought I cannot see how it is anything else), I would shut down apache,
mvyour WP directory elsewhere and start apache back up.True, but in theory it is the only thing running on Apache. So likely it was isolated in the last test, unless the other info wasn't correct.
Correct, but because of possible compromise issues, or just something he does not know about because he did not set it up, there is always a chance.
I do agree it will probably not come back showing anything but WP to be the issue.
-
I would check the Apache logs before rolling back as well.
Has the server been completely restarted? (I've followed the thread and haven't seen any mention of that.)
