ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    MySQL/Wordpress issue

    IT Discussion
    mysql wordpress
    9
    119
    9.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller @JaredBusch
      last edited by

      @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, mv your 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.

      JaredBuschJ 1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch @scottalanmiller
        last edited by

        @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, mv your 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.

        WLS-ITGuyW 1 Reply Last reply Reply Quote 0
        • dafyreD
          dafyre
          last edited by

          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.)

          WLS-ITGuyW 1 Reply Last reply Reply Quote 0
          • WLS-ITGuyW
            WLS-ITGuy @JaredBusch
            last edited by

            @jaredbusch said in MySQL/Wordpress issue:

            @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, mv your 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.

            How about disabling plugins?

            1 Reply Last reply Reply Quote 0
            • WLS-ITGuyW
              WLS-ITGuy @dafyre
              last edited by

              @dafyre said in MySQL/Wordpress 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.)

              Yes. A few times

              1 Reply Last reply Reply Quote 0
              • dafyreD
                dafyre
                last edited by

                What's do the Apache logs look like?

                (most likely in /var/log/apache2/apache.log and error.log)

                WLS-ITGuyW 1 Reply Last reply Reply Quote 0
                • WLS-ITGuyW
                  WLS-ITGuy @dafyre
                  last edited by

                  @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.log

                  Error 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

                  1 Reply Last reply Reply Quote 0
                  • jmooreJ
                    jmoore
                    last edited by

                    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.

                    1 Reply Last reply Reply Quote 0
                    • jmooreJ
                      jmoore
                      last edited by

                      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

                      1 Reply Last reply Reply Quote 0
                      • WLS-ITGuyW
                        WLS-ITGuy
                        last edited by

                        changing the MaxClients and ServerLimit doesn't fix anything.

                        Although moving my wordpress files does allow both apache and mysql to run

                        JaredBuschJ 1 Reply Last reply Reply Quote 0
                        • JaredBuschJ
                          JaredBusch @WLS-ITGuy
                          last edited by

                          @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.

                          WLS-ITGuyW 1 Reply Last reply Reply Quote 0
                          • WLS-ITGuyW
                            WLS-ITGuy @JaredBusch
                            last edited by

                            @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?

                            1 Reply Last reply Reply Quote 0
                            • jmooreJ
                              jmoore
                              last edited by

                              You restarted Apache after you changed the .conf file correct?

                              WLS-ITGuyW 1 Reply Last reply Reply Quote 0
                              • WLS-ITGuyW
                                WLS-ITGuy @jmoore
                                last edited by

                                @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.

                                1 Reply Last reply Reply Quote 0
                                • scottalanmillerS
                                  scottalanmiller
                                  last edited by

                                  Do you have WP-CLI installed? Maybe you can force an update that way.

                                  WLS-ITGuyW 1 Reply Last reply Reply Quote 0
                                  • jmooreJ
                                    jmoore
                                    last edited by

                                    Ok so it isn't Apache or Mysql so Jared and Scott are right on this then

                                    1 Reply Last reply Reply Quote 0
                                    • WLS-ITGuyW
                                      WLS-ITGuy @scottalanmiller
                                      last edited by

                                      @scottalanmiller Probably not.

                                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller @WLS-ITGuy
                                        last edited by

                                        @wls-itguy said in MySQL/Wordpress issue:

                                        @scottalanmiller Probably not.

                                        Probably worth installing.

                                        1 Reply Last reply Reply Quote 0
                                        • scottalanmillerS
                                          scottalanmiller
                                          last edited by

                                          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.

                                          1 Reply Last reply Reply Quote 0
                                          • black3dynamiteB
                                            black3dynamite
                                            last edited by

                                            Can WordPress be set to safemode for troubleshooting purposes?

                                            scottalanmillerS 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 6
                                            • 6 / 6
                                            • First post
                                              Last post