MySQL/Wordpress issue
-
What's do the Apache logs look like?
(most likely in /var/log/apache2/apache.log and error.log)
-
@dafyre said in MySQL/Wordpress issue:
What's do the Apache logs look like?
(most likely in /var/log/apache2/apache.log and error.log)
There isn't an apache.logError Log:
[Sun Jul 16 06:25:01 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 mod_ssl/2.2.22 OpenSSL/1.0.1t configured -- resuming normal operations
[Sun Jul 16 21:18:24 2017] [notice] caught SIGTERM, shutting down
[Sun Jul 16 21:19:16 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 mod_ssl/2.2.22 OpenSSL/1.0.1t configured -- resuming normal operations
[Tue Jul 18 11:32:30 2017] [error] an unknown filter was not added: includes
[Tue Jul 18 11:33:04 2017] [error] an unknown filter was not added: includes
[Tue Jul 18 11:33:17 2017] [error] an unknown filter was not added: includes
[Tue Jul 18 14:34:00 2017] [error] an unknown filter was not added: includes
[Tue Jul 18 14:34:00 2017] [error] an unknown filter was not added: includes
[Tue Jul 18 14:34:23 2017] [error] an unknown filter was not added: includes
[Thu Jul 20 09:27:41 2017] [notice] caught SIGTERM, shutting down
[Thu Jul 20 09:28:00 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 mod_ssl/2.2.22 OpenSSL/1.0.1t configured -- resuming normal operations
[Fri Jul 21 09:09:13 2017] [notice] caught SIGTERM, shutting down
[Fri Jul 21 09:10:28 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 mod_ssl/2.2.22 OpenSSL/1.0.1t configured -- resuming normal operations
[Fri Jul 21 09:11:40 2017] [error] server reached MaxClients setting, consider raising the MaxClients setting
[Fri Jul 21 12:46:22 2017] [notice] caught SIGTERM, shutting down
[Fri Jul 21 12:47:13 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 mod_ssl/2.2.22 OpenSSL/1.0.1t configured -- resuming normal operations
[Fri Jul 21 12:48:16 2017] [error] server reached MaxClients setting, consider raising the MaxClients setting
[Fri Jul 21 13:40:23 2017] [notice] caught SIGTERM, shutting down
[Fri Jul 21 13:49:21 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 mod_ssl/2.2.22 OpenSSL/1.0.1t configured -- resuming normal operations
[Fri Jul 21 13:50:59 2017] [notice] caught SIGTERM, shutting down -
From my earlier post it still looks like you are getting spammed.
This: [Fri Jul 21 09:11:40 2017] [error] server reached MaxClients setting, consider raising the MaxClients setting
says that to me. In your Apache2.conf file you can adjust that using an editor then restart Apache. Since you are on Linode you will find this useful, tuning apache. -
Scroll down about half way in that link and you will see an apache module where and how you can adjust the MaxClient's setting
-
changing the MaxClients and ServerLimit doesn't fix anything.
Although moving my wordpress files does allow both apache and mysql to run
-
@wls-itguy said in MySQL/Wordpress issue:
changing the MaxClients and ServerLimit doesn't fix anything.
Although moving my wordpress files does allow both apache and mysql to run
That 100% confirms that it is WP. Which is what we suspected, but that proves it.
-
@jaredbusch said in MySQL/Wordpress issue:
@wls-itguy said in MySQL/Wordpress issue:
changing the MaxClients and ServerLimit doesn't fix anything.
Although moving my wordpress files does allow both apache and mysql to run
That 100% confirms that it is WP. Which is what we suspected, but that proves it.
Yes. Now how to fix it
Would now be the time to move the site to a dedicated WP host? -
You restarted Apache after you changed the .conf file correct?
-
@jmoore said in MySQL/Wordpress issue:
You restarted Apache after you changed the .conf file correct?
yes. Both Apache & MySQL as well as restarted the server.
-
Do you have WP-CLI installed? Maybe you can force an update that way.
-
Ok so it isn't Apache or Mysql so Jared and Scott are right on this then
-
@scottalanmiller Probably not.
-
-
What's the latest here? If you install WP-CLI, I think that you can get your install and plugins updated which might help.
It's possible that you have a PHP issue. But WP is supposed to support PHP down to 5.2 something, but they recommend 7.
-
Can WordPress be set to safemode for troubleshooting purposes?
-
@black3dynamite said in MySQL/Wordpress issue:
Can WordPress be set to safemode for troubleshooting purposes?
Never tried that. I don't think so.
-
safe mode in wordpress is like disabling all of the plugins and setting theme to the original and then work from there.
-
Maybe you could move the plugins out of the folder temporarily and see if it will run without them present?
-
Was off the grid this weekend. was attempting an dist-upgrade and it fails with "too many errors". We are in the process of moving it to a WP host.
-
@wls-itguy said in MySQL/Wordpress issue:
Was off the grid this weekend. was attempting an dist-upgrade and it fails with "too many errors". We are in the process of moving it to a WP host.
Hostadillo, I hope!
