Announcement

Collapse
No announcement yet.

MySQL hammering my server after update to 5.6.3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Would it be helpful to upgrade from PHP 7.3 to 7.4 and to a more recent version of MariaDB?

    Comment


    • #17
      Originally posted by imager View Post
      I should have the MySQL log shortly. Where should I send this?
      You can provide access to this in a support ticket referencing this topic.

      Originally posted by imager View Post
      Would it be helpful to upgrade from PHP 7.3 to 7.4 and to a more recent version of MariaDB?
      I don't see anything in the reported issue where an upgrade of PHP or MariaDB will resolve the issue. Even switching to MySQL 8 may not resolve the issue. Since it is involving temporary files, the issue is most likely related to overall server configuration. I need to know what vBulletin is trying to do with these temporary file sorts and why it is using them first. Upgrades will probably not change this configuration.

      Speaking of information can you run this query and provide the results: describe node

      Finally, edit all search modules on your site and make sure they have a valid date range. Even if it is 365 (or more) days. Default should be 30 days but older installs might have empty values.
      Translations provided by Google.

      Wayne Luke
      The Rabid Badger - a vBulletin Cloud demonstration site.
      vBulletin 5 API

      Comment


      • #18
        And I just noticed that your PHP memory size is 32 MB. Please increase this to 128 MB.
        Translations provided by Google.

        Wayne Luke
        The Rabid Badger - a vBulletin Cloud demonstration site.
        vBulletin 5 API

        Comment


        • #19
          PHP is now set to 128MB.

          I'm not sure what you mean by run query describe node

          Comment


          • #20
            I have updated my support ticket mentioning you requested the mysql-slow.log file and I have sent it to contact AT vbulletin dot com via WeTranfer

            Also I don't know if this is useful?

            [[email protected] /]# mysqladmin proc | grep egroup_vb
            | 34 | egroup_vb | localhost | egroup_vb | Query | 2655 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 416 | egroup_vb | localhost | egroup_vb | Query | 2205 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 434 | egroup_vb | localhost | egroup_vb | Sleep | 2186 | | | 0.000 |
            | 438 | egroup_vb | localhost | egroup_vb | Sleep | 2182 | | | 0.000 |
            | 441 | egroup_vb | localhost | egroup_vb | Sleep | 2180 | | | 0.000 |
            | 442 | egroup_vb | localhost | egroup_vb | Sleep | 2179 | | | 0.000 |
            | 443 | egroup_vb | localhost | egroup_vb | Sleep | 2178 | | | 0.000 |
            | 446 | egroup_vb | localhost | egroup_vb | Sleep | 2177 | | | 0.000 |
            | 451 | egroup_vb | localhost | egroup_vb | Sleep | 2168 | | | 0.000 |
            | 452 | egroup_vb | localhost | egroup_vb | Sleep | 2166 | | | 0.000 |
            | 570 | egroup_vb | localhost | egroup_vb | Query | 2006 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 648 | egroup_vb | localhost | egroup_vb | Query | 1918 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 1058 | egroup_vb | localhost | egroup_vb | Query | 1339 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 1138 | egroup_vb | localhost | egroup_vb | Query | 1240 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 1499 | egroup_vb | localhost | egroup_vb | Query | 828 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 1628 | egroup_vb | localhost | egroup_vb | Query | 634 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 1720 | egroup_vb | localhost | egroup_vb | Query | 497 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 1845 | egroup_vb | localhost | egroup_vb | Query | 339 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 1858 | egroup_vb | localhost | egroup_vb | Query | 300 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 1911 | egroup_vb | localhost | egroup_vb | Query | 208 | Sending data | SELECT DISTINCT node.starter AS nodeid
            | 2007 | egroup_vb | localhost | egroup_vb | Query | 73 | Sending data | SELECT DISTINCT node.starter AS nodeid

            Comment


            • #21
              The support ticket is [SID-2327129]
              Last edited by Wayne Luke; Wed 16 Sep '20, 1:06pm.

              Comment


              • #22
                Wayne Luke "Finally, edit all search modules on your site and make sure they have a valid date range. Even if it is 365 (or more) days. Default should be 30 days but older installs might have empty values."

                I don't really know what you mean by this?

                Comment


                • #23
                  Pages are made of modules. In places where it uses search modules (i.e. Latest Activity) on various pages. Edit those modules using Site Builder and make sure the form field named "Date Range" has a value.
                  Translations provided by Google.

                  Wayne Luke
                  The Rabid Badger - a vBulletin Cloud demonstration site.
                  vBulletin 5 API

                  Comment


                  • #24
                    Is it the search JSON like this? {"date":{"from":"0"},"sort":

                    EDIT - I have worked it out; there were a few modules with '0' and have changed them to 30.
                    Last edited by imager; Wed 16 Sep '20, 10:12pm.

                    Comment


                    • #25
                      Originally posted by imager View Post
                      Is it the search JSON like this? {"date":{"from":"0"},"sort":

                      EDIT - I have worked it out; there were a few modules with '0' and have changed them to 30.
                      It's been half an hour since I edited the date ranges and reset the MySQL server and so far, touch wood, the server load has remained in what we regards as the normal range!

                      Comment


                      • #26
                        Changing the date range appears to have solved the problem. I don't actually know why the date range was zero in some of these modules but I am just so glad that it's all working again. Thank you for all the offers of help!

                        Comment

                        Related Topics

                        Collapse

                        Working...
                        X