MySQL/Wordpress issue
-
@wls-itguy said in MySQL/Wordpress issue:
@scottalanmiller said in MySQL/Wordpress issue:
Okay, let's get this one...
cat /var/log/mysql/error.logroot@www:~# cat /var/log/mysql/error.log
cat: /var/log/mysql/error.log: No such file or directoryThis server is FUBAR'd
It's old, too. Debian 9 is current, and those releases are very far apart.
-
Are you just running a single WordPress site here?
-
@scottalanmiller said in MySQL/Wordpress issue:
Are you just running a single WordPress site here?
Yes. Single site.
-
That is indeed strange. When you did a ps aux was there more than 1 mysql process or just 1?
-
@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.)
-
@jmoore said in MySQL/Wordpress issue:
That is indeed strange. When you did a ps aux was there more than 1 mysql process or just 1?
Just the one but I also had to run the restart service command before it would display any info.
-
Did you run [service mysql start] from terminal?
-
@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.
-
@jmoore said in MySQL/Wordpress issue:
Did you run [service mysql start] from terminal?
everything has been from CLI terminal
-
To be more clear, did you use the start or restart command?
-
@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.
-
@jmoore restart
-
In most cases it should not matter but in a few I think it does. run the same command but use [start]. So:
[service mysql start] -
@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.
-
@jmoore said in MySQL/Wordpress issue:
In most cases it should not matter but in a few I think it does. run the same command but use [start]. So:
[service mysql start]That brought the page up and then it crashed midway through the load.
-
Wow, tough problem. Let me think about it some more. Have you taken any backups recently in case you have to reinstall?
-
I have daily snapshots and full backups.
-
Have you changed any permissions or config files recently?
-
@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.
